public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97579] New: [11 Regression] ICE in gimple_expand_vec_cond_expr, at gimple-isel.cc:201 since r11-4123-g128f43cf679e5156
Date: Mon, 26 Oct 2020 11:44:21 +0000 [thread overview]
Message-ID: <bug-97579-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97579
Bug ID: 97579
Summary: [11 Regression] ICE in gimple_expand_vec_cond_expr, at
gimple-isel.cc:201 since r11-4123-g128f43cf679e5156
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Keywords: ice-on-valid-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
Target Milestone: ---
The issue was probably latent:
$ cat meteor.c
int bad_odd_rows_0_0, rows_bad_row1, rows_bad_group_okay, calc_rows_row2;
int
rows_bad() {
int i, in_zeroes;
char block;
i = 0;
for (; i < 5; i++)
if (rows_bad_row1 & i)
in_zeroes = 0;
else {
if (!in_zeroes)
in_zeroes = 1;
if (block & 1)
rows_bad_group_okay = 1;
}
if (in_zeroes)
return rows_bad_group_okay;
}
void
calc_rows() {
for (; calc_rows_row2; calc_rows_row2++) {
rows_bad();
bad_odd_rows_0_0 = rows_bad();
}
}
$ gcc meteor.c --param=max-unswitch-insns=1024 -O3 -mavx512vl -c
during GIMPLE pass: isel
meteor.c: In function ‘calc_rows’:
meteor.c:22:1: internal compiler error: in gimple_expand_vec_cond_expr, at
gimple-isel.cc:201
22 | calc_rows() {
| ^~~~~~~~~
0x72d8f5 gimple_expand_vec_cond_expr
/home/marxin/Programming/gcc/gcc/gimple-isel.cc:201
0xff19d0 gimple_expand_vec_exprs
/home/marxin/Programming/gcc/gcc/gimple-isel.cc:247
0xff19d0 execute
/home/marxin/Programming/gcc/gcc/gimple-isel.cc:300
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.
The problematic statement is:
(gdb) p debug_gimple_stmt(stmt)
mask__581.198_1001 = VEC_COND_EXPR <mask__258.180_254, { 0, 0, 0, 0, 0, 0, 0,
0, 0, 0, 0, 0, 0, 0, 0, 0 }, mask__649.184_117>;
(gdb) p mode
$3 = E_HImode
(gdb) p cmp_op_mode
$4 = E_V16SImode
next reply other threads:[~2020-10-26 11:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 11:44 marxin at gcc dot gnu.org [this message]
2020-10-26 11:44 ` [Bug tree-optimization/97579] " marxin at gcc dot gnu.org
2020-10-26 12:32 ` rguenth at gcc dot gnu.org
2020-10-27 16:09 ` marxin at gcc dot gnu.org
2020-10-28 7:27 ` rguenther at suse dot de
2020-10-29 13:21 ` marxin at gcc dot gnu.org
2020-11-03 15:23 ` cvs-commit at gcc dot gnu.org
2020-11-18 14:27 ` jakub at gcc dot gnu.org
2020-11-18 14:30 ` jakub at gcc dot gnu.org
2020-11-19 7:21 ` rguenth at gcc dot gnu.org
2020-11-25 11:32 ` rguenth at gcc dot gnu.org
2020-11-25 14:01 ` cvs-commit at gcc dot gnu.org
2020-11-25 14:02 ` rguenth at gcc dot gnu.org
2020-11-30 7:35 ` rguenth 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-97579-4@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).