On 5/23/11, Luis Rossi <luisf.ro...@gmail.com> wrote: > Hmm i really need to learn how to buid these things hehe. Anyway.. why > mspgcc keep changing of name? Is there any reason? They are tottaly > different projects?
Of course there's a reason :). There aren't different projects, really, in the sense of Emacs and XEmacs disagreeing and going in different directions. GCC got the MSP430 back end at or before GCC v.3. GCC kept evolving and did a major version jump to GCC v.4, but the MSP back end got some bugs in the process---like, the more aggressive optimization stragegies in v.4 triggered MSP code generation bugs, etc. So, many people preferred to stay with GCC v.3, but GCCv4 really is the only way forward, so people kept developing it as MSPGCC4. Now the original runtime interface in both versions was based on a flawed model where lot of the MSP chip model-specific info (e.g. differences in periphereal addresses, memory map, etc) was encoded in the compiler. This became unsustainable as the model count balooned to over 300, so MSP developers started shifting the chip dependent parts to per-chip header files, provided by TI; this is what is called 'uniarch'. It is of course based on the current version of GCC, i.e. v.4. ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
