On 2013-07-08, Brendan Conoboy <[email protected]> wrote:
> On 07/04/2013 07:10 PM, Peter Bigot wrote:
>> I have no information about Red Hat's toolchain other than what's been
>> announced here, but:
>>
>> Red Hat's MSP430 toolchain is entirely unrelated to mspgcc. I am unaware
>> of any information having been provided related to support for libc or
>> specific MCUs in this new work. While msp430mcu and msp430-libc might work
>> with some fiddling, it's not clear they're needed, I very much doubt
>> they're the intended solution, and they certainly don't incorporate any
>> changes to accommodate Red Hat's implementation.
>
> There is now msp430 support in newlib:
>
> http://www.cygwin.com/ml/newlib/2013/msg00362.html
>
> Since we did a clean re-implementation of the MSP port we can't comment
> on the pre-existing mspgcc library solutions: We really don't know. Our
> plan is to support and enhance standard upstream infrastructure. For
> libc this means newlib.
How does newlib compare with the old msp430 libc when it comes to
size? In the past, when I've tried newlib for embedded work it was
_huge_.
--
Grant Edwards grant.b.edwards Yow! Th' MIND is the Pizza
at Palace of th' SOUL
gmail.com
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Mspgcc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
