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

Peter Bigot <[email protected]>
Newsgroups gmane.comp.hardware.texas-instruments.msp430.gcc.user
Message-ID <CAPOJ94MijWm5pcubEEXpaqQ1tgOoRWau9SE1HoeAH7DX8MpU9g@mail.gmail.com>
On Thu, Mar 6, 2014 at 12:47 PM, DJ Delorie <[email protected]> wrote:
> If you have enough flash/ram, yes.  We fully test C++ in our
> simulators, so if gcc/newlib support it in general, it should work for
> msp430 also.

Great.  I'll try that out once it looks like all the TI patches are
applied to the 4.9 development branch.

>> (Exclusive of features that require host support like threads,
>> though it'd be good if <chrono> could be used with various MSP430
>> clocks providing the underlying timers.)
>
> Well, if you want *peripheral* support in the runtime libraries,
> that's a different story ;-)

No, I (very much) don't want gcc or newlib to do the peripheral
interface.  I am hopeful, though, that I can use the standard
templates by providing my own underlying implementation for (for
example) std::system_clock and std::high_resolution_clock.  Haven't
looked into the details yet, though.

Peter

------------------------------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.