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: SPEC 2017 profiling question (502.gcc_r and 505.mcf_r fail)

From: Thomas Koenig <tkoenig at netcologne dot de>
To: wschmidt at linux dot ibm dot com, Steve Ellcey <sellcey at marvell dot com>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Fri, 4 Oct 2019 23:14:51 +0200
Subject: Re: SPEC 2017 profiling question (502.gcc_r and 505.mcf_r fail)
References: <bf85fd7f07cbd2034e04cb997452ea3f93f76d32.camel@marvell.com> <d709fbc7-49a6-513f-034b-9fb2544b8dc9@linux.ibm.com>

Am 04.10.19 um 22:58 schrieb Bill Schmidt:

Have you tried -fno-strict-aliasing? There is a known issue withspec_qsort() that affects both of these benchmarks. Seehttps://gcc.gnu.org/bugzilla/show_bug.cgi?id=83201.


Reading that bug report (another refusal to correct a glaring
standards violation) convinces me just a tiny little bit more that
SPEC is a cancer.

References:
- SPEC 2017 profiling question (502.gcc_r and 505.mcf_r fail)
  - From: Steve Ellcey
- Re: SPEC 2017 profiling question (502.gcc_r and 505.mcf_r fail)
  - From: Bill Schmidt

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