Anticipating a couple questions: If you need more information on setting up a developer environment, see https://sourceforge.net/apps/mediawiki/mspgcc/index.php?title=Devel:git.
We're not jumping to base off the upstream trunk leading to 4.7.x for two reasons. First, because 4.7.0 won't be out until the end of the year and I'd like to see 20-bit support out in a 4.6.x-based release before then. Cherry-picking patches into a release branch is a pain, and the 4.7.x development series has changes that would make the msp430 back end incompatible with 4.6.x. Second, because one of the upstream changes in preparation for 4.7.x breaks the nesC compiler used for TinyOS, which comprises the bulk of my application-level test suite. And as a present for those reading this far, who were ignorant as I was: Try using -Wl,--sort-common when building an application. This decreases the amount of wasted RAM used to satisfy alignment constraints on uninitialized global variables. (No, I can't make that the default behavior.) Peter On Wed, Aug 3, 2011 at 5:36 AM, Peter Bigot <pabi...@users.sourceforge.net> wrote: > Anybody wishing to track development versions of mspgcc should now pull from > the repositories. Development is now based on the branch-point where 4.6.x > forked from trunk. This resulted in new branches to be used to track > development: follow "master" on all repositories (this is new for binutils > and gcc; the uniarch/* hierarchy is no longer active). The repository.txt > file in the maint branch on each repository has been updated with the new > development practices. > > Development and bug resolution will proceed on these branches. If you > report a bug and need it fixed in the 4.5.3 long-term support version, please > indicate that in your report. > > Since this is all new stuff with no road time, patches have not been added > to the mspgcc repository and there is no mspgcc release corresponding to > this. Note that this development is based on a gcc branch point, not an > upstream release. Do not distribute packages from these development > branches. A 4.6.1-based mspgcc will be released as a bundle when things > seem stable. > > NOTE: These updates include changes to binutils that clean up various linker > problems. If you used to have problems with Contiki or other systems that > use archives, rather than building monolithic executables as with TinyOS, > please see if your problems have been resolved. If not, or if there are new > ones, please open a ticket at on the tracker at > https://sourceforge.net/tracker/?func=browse&group_id=42303&atid=432701 > > Peter > > Binutils updates: > de15d45 SF 3143071 error in addend of relocation entry in output > b23dce1 SF 3384754 relocatable links discard CRT section information > cee33c6 SF 3384766 string constants misplaced in text section > 74b7db4 SF 3379341: non-empty ARCH environment variable results unusable ld > > GCC updates: > e4f5384 SF 3384766 string constants misplaced in text section > 3f602e2 SF 3370978: ICE on shift with 32-bit count > ------------------------------------------------------------------------------ BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA The must-attend event for mobile developers. Connect with experts. Get tools for creating Super Apps. See the latest technologies. Sessions, hands-on labs, demos & much more. Register early & save! http://p.sf.net/sfu/rim-blackberry-1 _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
