On Thu, Mar 6, 2014 at 6:05 AM, David Brown <da...@westcontrol.com> wrote: > Will the __intN stuff ever make it into mainline? The msp430 port may > be the only chip that needs __int20, but there are other chips that > could benefit from different integer sizes - perhaps __int24 on the > 8-bit AVR, or __int40 on some devices with DSP-style accumulators.
I'd hope that it's done in a way that allows that, though I haven't looked at what DJ did. Speaking as somebody who did all this in gcc almost two years ago, part of what's needed was already there, but it had some bugs (which I reported, and one of which Nick later rediscovered in the RH port). There are a lot of other issues for full msp430 20-bit support too (mostly to do with address/non-address value differences), many of which were solved in mspgcc. Hopefully the new clean-room implementation, done by folks who know more about gcc, will address the flaws in mspgcc's approach and be acceptable upstream. Peter ------------------------------------------------------------------------------ Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce. With Perforce, you get hassle-free workflows. Merge that actually works. Faster operations. Version large binaries. Built-in WAN optimization and the freedom to use Git, Perforce or both. Make the move to Perforce. http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk _______________________________________________ Mspgcc-users mailing list Mspgcc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mspgcc-users
