On Thu, Jun 5, 2014 at 4:48 PM, DJ Delorie <d...@redhat.com> wrote: > > The reason msp430 is different is because CIO *can* be used on real > hardware, to communicate through a hardware debugger or emulator pod. > > Perhaps moving the cio-enabled nosys to a libcio.a? Then we'd need a > -mcio option to gcc to enable it, but could default to doing the > generic nosys thing...
I like that approach; it makes clear that the system interface is still CIO even when not using -msim, and it gives application developers the appropriate level of control when CIO is not desired. Making selection of -mcio a positive decision (not default) also helps reveal when an application unintentionally introduces dependencies such as calls to sbrk (malloc) for newlib internal data structures that most mspgcc developers would be surprised to find happening (they did not occur with the same functions in msp430-libc). What needs to be done to get this into place? Do you need an enhancement request in gcc and/or newlib bugzilla? Peer ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/NeoTech _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
