As I approach the end of the cleanup necessary before releasing the new gcc 4.5.2-base unified architecture mspgcc for test, I'd like anybody who uses or would defend preservation of the following features to reply with details explaining that they do work and are useful. I want to get all the breakage done up front.
- The msp430-specific profiling infrastructure, including compiler options -mpgs, -mpgl, -mpgr. As far as I can tell, these options are never referenced in gcc, and are not recognized in binutils. There is a profiling infrastructure for msp430 in the GNU assembler which I don't intend to remove at the moment, although the example code in the comment was rejected with syntax errors when I tried it. (If you use that, please let me know.) - -mrtl (apparently unused) and -mdeb dump options - Support for the IAR assembler (-mIAR). I don't have this assembler, so can't verify that it works; the only affect the flag seems to have is that it defines _IAR_ASSEMBLER_ during preprocessing. - The -maccumulate-outgoing-args option. There are likely to be other changes, including removal of all the syntactic sugar that hides use of GCC attributes in function modifiers like interrupt, critical, noinit, reentrant, etc. I'll add some sort of legacy header file for people who explicitly want to use them, but having these symbols defined in iomacros.h is just wrong. Sing out if you have an opinion on any of this. Peter
------------------------------------------------------------------------------ Free Software Download: Index, Search & Analyze Logs and other IT data in Real-Time with Splunk. Collect, index and harness all the fast moving IT data generated by your applications, servers and devices whether physical, virtual or in the cloud. Deliver compliance at lower cost and gain new business insights. http://p.sf.net/sfu/splunk-dev2dev
_______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
