tag | 10ae92531ae6ae481405baf73fd7ff58e01b76c5 | |
---|---|---|
tagger | Tom Stellard <tstellar@redhat.com> | Fri Mar 17 16:31:52 2023 -0700 |
object | 0bf641816abea1f785603193e1ed0d939bae8516 |
Tag 16.0.0
commit | 0bf641816abea1f785603193e1ed0d939bae8516 | [log] [tgz] |
---|---|---|
author | Alexandros Lamprineas <alexandros.lamprineas@arm.com> | Tue Jan 10 20:19:03 2023 +0000 |
committer | Alexandros Lamprineas <alexandros.lamprineas@arm.com> | Wed Jan 11 16:29:27 2023 +0000 |
tree | 1bbf27b0675260e10c54e3e593a8fe56cb2fd7d9 | |
parent | de2e530ed27db6a14cf8d420fc721d2e605b31e2 [diff] |
[SPEC2017] Use -fno-strict-aliasing when compiling 502.gcc_r, 505.mcf_r As suggested on SPEC's documentation page (Known Portability Issues) [1][2] the spec_qsort.c routine does not strictly obey the ANSI aliasing rules. In the absence of -fno-strict-aliasing the test suite fails when Function Specialization is enabled with both LTO and PGO (see https://reviews.llvm.org/D140210). [1] https://www.spec.org/cpu2017/Docs/benchmarks/502.gcc_r.html [2] https://www.spec.org/cpu2017/Docs/benchmarks/505.mcf_r.html Differential Revision: https://reviews.llvm.org/D141474