There are three multilibs that are built: 430 - the "default" so it doesn't have a subdir - is for all non-430X processors.
430x - for 430X series processors, but still using 16-bit pointers. 430x/large - for 430X series processors using 20-bit pointers. For each of those, newlib is built using a "common subset" so it works for any (I hope) processor in that category. GCC (msp430-elf-gcc, not mspgcc) has two options it looks at: -mmcu=<whatever> - if <whatever> has "430x" or "430X" in it, you get the 430x family. Default is the 430 family. -mlarge - enables 20-bit pointers. IIRC there's also -mcpu= which specifies the family (430/430x) directly, for when the MCU name doesn't match the pattern. Also, keep in mind that newlib is not targetted specifically to the 430's needs. It's a generic runtime library so tends to be more "one size fits all" than "one variant per chip" like mspgcc's library. ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
