https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83201
--- Comment #22 from Martin Liška <marxin at gcc dot gnu.org> --- (In reply to john henning from comment #21) > Comments from SPEC CPU Documentation Guy: > > As described at > https://www.spec.org/cpu2017/Docs/faq.html#Miscompare.07 > https://www.spec.org/cpu2017/Docs/benchmarks/505.mcf_r.html#Portability > SPEC's recommendation is to use > -fno-strict-aliasing > > The patch attached to this bug is not approved by SPEC. > > SPEC generally does not change benchmarks after release (no moving targets); > more detail is at the above links. > > John Henning > SPEC CPU Subcommittee Secretary Note that the same function is used by other benchmarks as well: 502.gcc_r, 511.povray_r, 527.cam4_r That means the same miscompilation can happen for them as well :/
