Massive SPEC failures on trunk
H. J. Lu
hjl@lucon.org
Sat Mar 3 22:09:00 GMT 2007
On Sat, Mar 03, 2007 at 02:00:30PM -0800, Andrew Pinski wrote:
> 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.
While we are on SPEC CPU, has anyone tried gcc on SPEC CPU 2006? I
need a patch to fix 465.tonto and a patch to fix 400.perlbench
which is Linux/ia64 specific. Has anyone else reported those problems
to SPEC?
H.J.
More information about the Gcc
mailing list