https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92288
Bug ID: 92288
Summary: [10 Regression] 502.gcc_r ICE with -O3 -march=skylake
-fno-checking since r277621
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Blocks: 26163
Target Milestone: ---
Before the revision there was a checking assert (that I disabled with
-fno-checking).
Can reproduce with test size:
runcpu --config=spec2017 --size=test --iterations=1 --no-reportable -I
--action=run --tune=peak 502.gcc_r -D
Contents of t1.opts-O3_-finline-limit_50000.err
****************************************
t1.c:2:5: warning: conflicting types for built-in function 'printf'
t1.c: In function 'main':
t1.c:9:1: benchmark internal error: in ?, at df-scan.c:1573
The 502.gcc_r benchmark binary 'cpugcc_r' has encountered an internal error.
It is possible that there is an error in the benchmark 502.gcc_r
source code, but it is more likely that your compiler
has mis-optimized or otherwise generated bad code for
the benchmark. You might try reducing the optimization
level; see your compiler documentation.
If you think the error is in the benchmark source code, see
www.spec.org/cpu2017/Docs/techsupport.html
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
[Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
