On Sun, Jul 7, 2013 at 7:12 PM, Brendan Conoboy <b...@redhat.com> wrote:
>
> 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's footprint compare with msp430-libc?
Last time I used newlib (on ARM) it seemed to want to do dynamic memory
allocation for a simple printf() (!). I can't imagine using it on a device
with 256 bytes RAM... or was I just using newlib wrong?
Regards,
Mark
markrages@gmail
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Mspgcc-users mailing list
Mspgcc-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mspgcc-users
