[Bug lto/87283] [9 Regression] internal compiler error: in remove, at alloc-pool.h:433

hjl.tools at gmail dot com gcc-bugzilla@gcc.gnu.org
Tue Sep 11 17:25:00 GMT 2018


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87283

--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
Created attachment 44679
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44679&action=edit
A testcase

./lto1 -quiet -dumpdir ./ -dumpbase gromacs.ltrans2 -mtune=generic
-march=x86-64 -mtune=generic -march=x86-64 -auxbase-strip
gromacs.ltrans2.ltrans.o -O2 -O2 -version -fno-openmp -fno-openacc -fno-pie
-ffast-math -fwhole-program -fuse-linker-plugin -fltrans /tmp/gromacs.ltrans2.o
-o gromacs.ltrans2.s

GNU GIMPLE (GCC) version 9.0.0 20180911 (experimental) (x86_64-pc-linux-gnu)
        compiled by GNU C version 8.2.1 20180726 (Red Hat 8.2.1-1), GMP version
6.1.2, MPFR version 3.1.6-p2, MPC version 1.0.2, isl version isl-0.16.1-GMP

GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
GNU GIMPLE (GCC) version 9.0.0 20180911 (experimental) (x86_64-pc-linux-gnu)
        compiled by GNU C version 8.2.1 20180726 (Red Hat 8.2.1-1), GMP version
6.1.2, MPFR version 3.1.6-p2, MPC version 1.0.2, isl version isl-0.16.1-GMP

GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
during GIMPLE pass: recip
sim_util.c: In function ‘do_force.constprop’:
sim_util.c:189:6: internal compiler error: in remove, at alloc-pool.h:433
0x9858fb base_pool_allocator<memory_block_pool>::remove(void*)
        /export/gnu/import/git/sources/gcc/gcc/alloc-pool.h:433
0x120cc1e object_allocator<occurrence>::remove(occurrence*)
        /export/gnu/import/git/sources/gcc/gcc/alloc-pool.h:521
0x1201b97 free_bb
        /export/gnu/import/git/sources/gcc/gcc/tree-ssa-math-opts.c:523
0x1202ae9 execute_cse_reciprocals_1
        /export/gnu/import/git/sources/gcc/gcc/tree-ssa-math-opts.c:840
0x1202e1d execute
        /export/gnu/import/git/sources/gcc/gcc/tree-ssa-math-opts.c:923
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.


More information about the Gcc-bugs mailing list