Re: msp430-elf size optimizations - some notes and a patch

> OK, if it is /that/ much space then it's a completely different
>  matter.  I thought we were just talking about clearing the bss and
>  setting the initialised data, which should just be a couple of
>  short simple loops.

Worst case startup is around 400 bytes, but once you start optimizing,
you might as well handle all the cases as best you can.

> Perhaps more relevantly, what about C++ support?  msp430 developers
> will need some basic C++ support, including global constructors -
> but can usually do without global destructors, support for unhandled
> exceptions (or any exceptions or RTTI), etc., which can otherwise
> take up a lot of code space.

Basic C++ should be there, I think including exceptions.

> And I expect Ada support is on your things-to-do list as well, in
> case you get bored!

Sorry, Ada isn't on my to-do list ;-)

> On some systems (not gcc on the msp430), I have had to resort to
> making empty stub functions for exit() and a few other library
> functions in order to avoid massive library imports.

Me too.

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk