public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/102152] New: [12 Regression] ICE: tree check: expected ssa_name, have integer_cst in cprop_operand, at tree-ssa-dom.c:1715
Date: Wed, 01 Sep 2021 04:18:46 +0000 [thread overview]
Message-ID: <bug-102152-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102152
Bug ID: 102152
Summary: [12 Regression] ICE: tree check: expected ssa_name,
have integer_cst in cprop_operand, at
tree-ssa-dom.c:1715
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
Target: aarch64-linux-gnu
gcc-12.0.0-alpha20210829 snapshot (g:c3c669ac811429033c0151f910b38fc009e21ca8)
ICEs when compiling the following testcase w/ -march=armv8-a+sve -O1
-ftree-loop-vectorize -fno-tree-fre:
signed char i;
void
foo (void)
{
for (i = 0; i < 6; i += 5)
;
}
% aarch64-linux-gnu-gcc-12.0.0 -march=armv8-a+sve -O1 -ftree-loop-vectorize
-fno-tree-fre -c gye5eeyb.c
during GIMPLE pass: dom
gye5eeyb.c: In function 'foo':
gye5eeyb.c:4:1: internal compiler error: tree check: expected ssa_name, have
integer_cst in cprop_operand, at tree-ssa-dom.c:1715
4 | foo (void)
| ^~~
0x7e6522 tree_check_failed(tree_node const*, char const*, int, char const*,
...)
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-12.0.0_alpha20210829/work/gcc-12-20210829/gcc/tree.c:8688
0x7a5747 tree_check(tree_node*, char const*, int, char const*, tree_code)
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-12.0.0_alpha20210829/work/gcc-12-20210829/gcc/tree.h:3391
0x7a5747 cprop_operand
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-12.0.0_alpha20210829/work/gcc-12-20210829/gcc/tree-ssa-dom.c:1715
0x7a5747 cprop_into_stmt
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-12.0.0_alpha20210829/work/gcc-12-20210829/gcc/tree-ssa-dom.c:1792
0x7a5747 dom_opt_dom_walker::optimize_stmt(basic_block_def*,
gimple_stmt_iterator*, bool*)
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-12.0.0_alpha20210829/work/gcc-12-20210829/gcc/tree-ssa-dom.c:2002
0x105aef8 dom_opt_dom_walker::before_dom_children(basic_block_def*)
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-12.0.0_alpha20210829/work/gcc-12-20210829/gcc/tree-ssa-dom.c:1430
0x1a17487 dom_walker::walk(basic_block_def*)
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-12.0.0_alpha20210829/work/gcc-12-20210829/gcc/domwalk.c:309
0x10584ec execute
/var/tmp/portage/cross-aarch64-linux-gnu/gcc-12.0.0_alpha20210829/work/gcc-12-20210829/gcc/tree-ssa-dom.c:764
next reply other threads:[~2021-09-01 4:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 4:18 asolokha at gmx dot com [this message]
2021-09-01 4:30 ` [Bug tree-optimization/102152] " pinskia at gcc dot gnu.org
2021-09-01 4:35 ` pinskia at gcc dot gnu.org
2021-09-01 10:10 ` rguenth at gcc dot gnu.org
2021-09-01 20:31 ` law at gcc dot gnu.org
2021-09-01 23:15 ` cvs-commit at gcc dot gnu.org
2021-09-01 23:21 ` law at gcc dot gnu.org
2021-09-02 19:56 ` pinskia 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-102152-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).