https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99328
Alex Coplan <acoplan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
CC| |acoplan at gcc dot gnu.org
Status|UNCONFIRMED |NEW
Last reconfirmed| |2021-04-12
--- Comment #1 from Alex Coplan <acoplan at gcc dot gnu.org> ---
Confirmed. Here's a testcase that ICEs with some different options:
$ cat test.cc
int a, d;
long b;
char c;
long *e;
char *f;
void g() {
for (short h = 0; h < 24; h += 4)
while (d)
while (b)
while (1)
for (bool i; i < 1; i += c)
for (; f[h]; a = e[h])
;
}
$ aarch64-linux-gnu-gcc -c test.cc -O2 -fsanitize=undefined -mtune=octeontx2t93
-fselective-scheduling2 -fsel-sched-pipelining
during RTL pass: sched2
test.cc: In function ‘void g()’:
test.cc:14:1: internal compiler error: in verify_target_availability, at
sel-sched.c:1557
14 | }
| ^
0x1063ed9 verify_target_availability
/home/alecop01/toolchain/src/gcc/gcc/sel-sched.c:1553
0x1063ed9 find_best_reg_for_expr
/home/alecop01/toolchain/src/gcc/gcc/sel-sched.c:1667
0x1063ed9 fill_vec_av_set
/home/alecop01/toolchain/src/gcc/gcc/sel-sched.c:3784
0x1066c06 fill_ready_list
/home/alecop01/toolchain/src/gcc/gcc/sel-sched.c:4014
0x1066c06 find_best_expr
/home/alecop01/toolchain/src/gcc/gcc/sel-sched.c:4374
0x1066c06 fill_insns
/home/alecop01/toolchain/src/gcc/gcc/sel-sched.c:5535
0x1066c06 schedule_on_fences
/home/alecop01/toolchain/src/gcc/gcc/sel-sched.c:7353
0x1066c06 sel_sched_region_2
/home/alecop01/toolchain/src/gcc/gcc/sel-sched.c:7491
0x1069b3c sel_sched_region_1
/home/alecop01/toolchain/src/gcc/gcc/sel-sched.c:7533
0x106a463 sel_sched_region(int)
/home/alecop01/toolchain/src/gcc/gcc/sel-sched.c:7634
0x106ba03 run_selective_scheduling()
/home/alecop01/toolchain/src/gcc/gcc/sel-sched.c:7720
0x1046150 rest_of_handle_sched2
/home/alecop01/toolchain/src/gcc/gcc/sched-rgn.c:3738
0x1046150 execute
/home/alecop01/toolchain/src/gcc/gcc/sched-rgn.c:3882
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.