Re: TI compiler
Yamandu Ploskonka <[email protected]> Fri, 3 Mar 2017 16:24:14 -0600
| Newsgroups | gmane.comp.hardware.texas-instruments.msp430.gcc.user |
|---|---|
| Message-ID | <CANot=bcOWJAHoDbu-x2EhR=GWGTZhWC9Un44g0=-MhQuZr_Qaw@mail.gmail.com> |
--===============7916147926333510373== Content-Type: multipart/alternative; boundary=001a114416287215300549db01ba --001a114416287215300549db01ba Content-Type: text/plain; charset=UTF-8 long story short, one of my first mspgcc worked because of a bug, when later either the bug was fixed in mspgcc or fedora (don't recall which one exactly), things broke all over, code unusable, docs I had share were wrong. But by then I was already married to the MSP430 chips, so I stayed for the ride, and am generally happy with my choice, though that ESP that uses arduino code and has full wifi at a cost of around one US dollar per has more than once made me look again. :-) (but it eats battery power, so again, MSP430 is better, at least for me) On Fri, Mar 3, 2017 at 12:30 PM, DJ Delorie <[email protected]> wrote: > > This has come up before, and here's what's going on... the new > msp430-elf-gcc includes all the code required by the standard, partly > because... well, standards... and partly so that the testsuite can test > everything. The old msp-gcc made lots of assumptions about how the > compiler would actually be used, and "pre-optimized" the runtime for it. > > So you end up with things like "argv handling" when there's no command > line, or "exit closes files" when you never exit. A big change is using > a float-enabled printf when you don't need it. > > I put some notes here, way back when, but they're old, and IIRC it's > been improved even more since then: > > http://people.redhat.com/~dj/msp430/size-optimizations.html > > Also, you can use "msp430-elf-gcc -mintr ..." to minimize the runtime > support. > > Also, if you're REALLY constrained to size, you might consider getting > the crt0.S source file from newlib and modifying it yourself to really > strip out the parts you don't need. Most embedded code really only > needs to set up the stack and watchdog, then jump to main(). > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Mspgcc-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mspgcc-users > --001a114416287215300549db01ba-- --===============7916147926333510373== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot --===============7916147926333510373== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users --===============7916147926333510373==--