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 tree-optimization/97104] [11 Regression] aarch64, SVE: ICE in vect_get_loop_mask since r11-3070-g783dc66f9cc
Date: Thu, 05 Nov 2020 09:49:45 +0000	[thread overview]
Message-ID: <bug-97104-4-it57yUezdW@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97104-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Alex Coplan <acoplan at gcc dot gnu.org> ---
For the related testcase:

int a, c, d, e;
long b;
void f() {
  short g = a;
  for (; c; c++) {
    b &= a == 0 ? 1 : g / a;
    d |= e;
  }
}

with the same options on AArch64, we ICE with a similar (but not identical)
backtrace:

during GIMPLE pass: vect
test.c: In function 'f':
test.c:3:6: internal compiler error: in vect_get_loop_mask, at
tree-vect-loop.c:8868
    3 | void f() {
      |      ^
0x10a45cc vect_get_loop_mask(gimple_stmt_iterator*, auto_vec<rgroup_controls,
0ul>*, unsigned int, tree_node*, unsigned int)
        /home/alecop01/toolchain/src/gcc/gcc/tree-vect-loop.c:8867
0x1085843 vectorizable_condition
        /home/alecop01/toolchain/src/gcc/gcc/tree-vect-stmts.c:10195
0x109b040 vect_transform_stmt(vec_info*, _stmt_vec_info*,
gimple_stmt_iterator*, _slp_tree*, _slp_instance*)
        /home/alecop01/toolchain/src/gcc/gcc/tree-vect-stmts.c:10831
0x10a1eb3 vect_transform_loop_stmt
        /home/alecop01/toolchain/src/gcc/gcc/tree-vect-loop.c:9053
0x10bee28 vect_transform_loop(_loop_vec_info*, gimple*)
        /home/alecop01/toolchain/src/gcc/gcc/tree-vect-loop.c:9475
0x10eb324 try_vectorize_loop_1
        /home/alecop01/toolchain/src/gcc/gcc/tree-vectorizer.c:1091
0x10eba51 try_vectorize_loop
        /home/alecop01/toolchain/src/gcc/gcc/tree-vectorizer.c:1148
0x10ebe2b vectorize_loops()
        /home/alecop01/toolchain/src/gcc/gcc/tree-vectorizer.c:1229
0xf7843d execute
        /home/alecop01/toolchain/src/gcc/gcc/tree-ssa-loop.c:414
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.

  parent reply	other threads:[~2020-11-05  9:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-18 11:19 [Bug tree-optimization/97104] New: " acoplan at gcc dot gnu.org
2020-09-18 11:20 ` [Bug tree-optimization/97104] " acoplan at gcc dot gnu.org
2020-09-18 12:04 ` rguenth at gcc dot gnu.org
2020-10-16 12:09 ` rguenth at gcc dot gnu.org
2020-11-05  9:49 ` acoplan at gcc dot gnu.org [this message]
2020-12-10 17:00 ` akrl at gcc dot gnu.org
2021-01-14 16:13 ` acoplan at gcc dot gnu.org
2021-03-09 14:24 ` rguenth at gcc dot gnu.org
2021-03-09 14:25 ` acoplan at gcc dot gnu.org
2021-03-09 14:57 ` 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-97104-4-it57yUezdW@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).