Hi Peter > Ping.
[DJ is on vacation, so I am standing in for him...] >>> 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? Yes - if you want Red Hat to do this. But of course you can do the work yourself if you prefer. > Absent any coordinated action on this, I'm going to send patches to > newlib to remove the special-case override of libnosys in msp430 > libgloss, and to gcc to eliminate the automatic addition of -lnosys > when -msim is absent in gcc. Both of which are perfectly reasonable, and I see no reason why they should not be accepted. Cheers Nick ------------------------------------------------------------------------------ Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311&iu=/4140/ostg.clktrk _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
