This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Massive SPEC failures on trunk

From: Grigory Zagorodnev <grigory_zagorodnev at linux dot intel dot com>
To: Andrew Pinski <pinskia at gmail dot com>
Cc: "H. J. Lu" <hjl at lucon dot org>, Diego Novillo <dnovillo at redhat dot com>, gcc at gcc dot gnu dot org, Ian Lance Taylor <iant at google dot com>
Date: Sun, 04 Mar 2007 22:36:09 +0300
Subject: Re: Massive SPEC failures on trunk
References: <45E9235F.4000507@linux.intel.com> <45E99BE4.5060709@redhat.com> <20070303215422.GA19570@lucon.org> <de8d50360703031400h16a9f4besc99bb994232cd989@mail.gmail.com>

Andrew Pinski wrote:

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.

In this case we would need to add -fno-strict-aliasing to CFLAGS for the whole 'int' test set, since we follow 'baseline' rules. That would result overall performance degradation. Thus we prefer alternative sources in this particular case.

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.

We have made some changes for 176.gcc in spec cpu2000 v1.3 (see http://www.spec.org/cpu2000/issues/). We can either assist in submitting issues via Intel's representative in SPEC committee later on.

- Grigory

References:
- Massive SPEC failures on trunk
  - From: Grigory Zagorodnev
- Re: Massive SPEC failures on trunk
  - From: Diego Novillo
- Re: Massive SPEC failures on trunk
  - From: H. J. Lu
- Re: Massive SPEC failures on trunk
  - From: Andrew Pinski

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]