On Mon, Sep 22, 2014 at 11:40 AM, DJ Delorie <d...@redhat.com> wrote: > >> It's not really feasible to extract those changes and apply them to a >> non-bundled source directory since the base version isn't exactly GCC >> 4.9.1. If you or TI could provide information on whether those >> patches are likely to get refactored and merged upstream, and any >> timeline information that's available, I think most folks here would >> be interested. > > You need my __intN patch set, currently being reviewed upstream. Some > parts have been approved and applied, but you still need the main > conversion (3/5, pending libg++ review) and the msp430-specific part > (5/5, just waiting on part 3/5). This patch set is based on the > TI-specific patch in their 4.9 sources. > > https://gcc.gnu.org/ml/gcc-patches/2014-08/threads.html#01398
Thanks. As it's in-progress, I'll just wait until it appears in the tree. I mostly don't use 20-bit on msp430-elf: it takes up too much space compared to mspgcc since (AFAIK) there's no compact/medium modes so lots of things like size_t take 32 bits of memory when they could take 16 for most applications. If I need more memory for a project I use ARM processors where I don't have to deal with split address spaces. FWIW: There are one or two unverified bug reports from me in gcc's bugzilla that I'd hit doing 20-bit support in mspgcc that can probably be closed now that part 2/5 (PRECISION != BITSIZE) is in. Peter ------------------------------------------------------------------------------ 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
