This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Massive SPEC failures on trunk
- From: "Andrew Pinski" <pinskia at gmail dot com>
- To: "H. J. Lu" <hjl at lucon dot org>
- Cc: "Diego Novillo" <dnovillo at redhat dot com>, "Grigory Zagorodnev" <grigory_zagorodnev at linux dot intel dot com>, gcc at gcc dot gnu dot org, "Ian Lance Taylor" <iant at google dot com>
- Date: Sat, 3 Mar 2007 14:00:30 -0800
- Subject: Re: Massive SPEC failures on trunk
- References: <45E9235F.4000507@linux.intel.com> <45E99BE4.5060709@redhat.com> <20070303215422.GA19570@lucon.org>
On 3/3/07, H. J. Lu <hjl@lucon.org> wrote:
> [1] 176.gcc and 253.perlbmk usually miscompare for me. Not sure why.
176.gcc=default=default=default:
CPORTABILITY = -Dalloca=_alloca
EXTRA_LDFLAGS =
srcalt=64bitgcc40
For one, the 176.gcc in SPEC 2k has an aliasing violation in it so
that failing is known. You might want to try adding
-fno-strict-aliasing.
I have been asking someone who has the power to submit an alt to SPEC
for that failure for 3 years now and now it is too late really.
Thanks,
Andrew Pinski