public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "acoplan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/99328] ICE: in verify_target_availability, at sel-sched.c:1557 with -fselective-scheduling2 on aarch64
Date: Mon, 12 Apr 2021 09:00:48 +0000	[thread overview]
Message-ID: <bug-99328-4-vHAB9QET1S@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99328-4@http.gcc.gnu.org/bugzilla/>

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.

  reply	other threads:[~2021-04-12  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-01 17:15 [Bug rtl-optimization/99328] New: " qinzhao at gcc dot gnu.org
2021-04-12  9:00 ` acoplan at gcc dot gnu.org [this message]
2021-04-12  9:56 ` [Bug rtl-optimization/99328] " acoplan at gcc dot gnu.org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-99328-4-vHAB9QET1S@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).