Hi Ian,
I would like to ask the maintainers for backends which
I did not mention to bootstrap their targets if possible, and/or to
build them with a newly built mainline compiler, to see if there are new
warnings about C++ compatibility.
For the record I have tested the fr30, iq2000, m32r, mco
On Mon, 20 Apr 2009, Andrew Pinski wrote:
> On Mon, Apr 20, 2009 at 2:30 PM, Ian Lance Taylor wrote:
> > I have not fixed every gcc backend to compile without producing any of
> > the new warnings. I have fixed some: arm, i386, ia64, mips, pa, rs6000,
> > s390, sparc, spu. This covers all the p
On Mon, Apr 20, 2009 at 2:30 PM, Ian Lance Taylor wrote:
> I have not fixed every gcc backend to compile without producing any of
> the new warnings. I have fixed some: arm, i386, ia64, mips, pa, rs6000,
> s390, sparc, spu. This covers all the primary and secondary platforms,
> plus spu which I
Last week I committed a patch to check for enum comparisons which are
invalid in C++. Today I committed a patch to check for enum conversions
during function calls which are invalid in C++. These new warnings are
enabled by -Wc++-compat.
I have not fixed every gcc backend to compile without prod
