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/98726] New: aarch64: tree check: expected integer_cst, have poly_int_cst in to_wide, at tree.h:5984
Date: Mon, 18 Jan 2021 11:44:04 +0000 [thread overview]
Message-ID: <bug-98726-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98726
Bug ID: 98726
Summary: aarch64: tree check: expected integer_cst, have
poly_int_cst in to_wide, at tree.h:5984
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: acoplan at gcc dot gnu.org
Target Milestone: ---
The following fails:
$ cat test.c
int a, c;
char b;
int d() {
a = 0;
for (; a <= 21; a = (short)a + 1)
b &= c;
}
$ aarch64-elf-gcc -c test.c -O3 -march=armv8.2-a+sve
during GIMPLE pass: forwprop
test.c: In function 'd':
test.c:3:5: internal compiler error: tree check: expected integer_cst, have
poly_int_cst in to_wide, at tree.h:5984
3 | int d() {
| ^
0x1161f66 tree_check_failed(tree_node const*, char const*, int, char const*,
...)
/home/alecop01/toolchain/src/gcc/gcc/tree.c:9812
0x7393c1 tree_check(tree_node const*, char const*, int, char const*, tree_code)
/home/alecop01/toolchain/src/gcc/gcc/tree.h:3594
0x7393c1 wi::to_wide(tree_node const*)
/home/alecop01/toolchain/src/gcc/gcc/tree.h:5984
0x1177e1d vector_cst_int_elt(tree_node const*, unsigned int)
/home/alecop01/toolchain/src/gcc/gcc/tree.c:11104
0x11935a3 vector_cst_elt(tree_node const*, unsigned int)
/home/alecop01/toolchain/src/gcc/gcc/tree.c:11131
0xa35b48 const_binop(tree_code, tree_node*, tree_node*, tree_node*)
/home/alecop01/toolchain/src/gcc/gcc/fold-const.c:1644
0x1484144 gimple_resimplify2
/home/alecop01/toolchain/src/gcc/gcc/gimple-match-head.c:276
0x14b3ca2 gimple_simplify(gimple*, gimple_match_op*, gimple**, tree_node*
(*)(tree_node*), tree_node* (*)(tree_node*))
/home/alecop01/toolchain/src/gcc/gcc/gimple-match-head.c:957
0xa9c5d1 fold_stmt_1
/home/alecop01/toolchain/src/gcc/gcc/gimple-fold.c:6016
0xa9ef9b fold_stmt(gimple_stmt_iterator*, tree_node* (*)(tree_node*))
/home/alecop01/toolchain/src/gcc/gcc/gimple-fold.c:6254
0xf73a2a execute
/home/alecop01/toolchain/src/gcc/gcc/tree-ssa-forwprop.c:3108
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.
next reply other threads:[~2021-01-18 11:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 11:44 acoplan at gcc dot gnu.org [this message]
2021-01-18 11:44 ` [Bug tree-optimization/98726] SVE: " acoplan at gcc dot gnu.org
2021-01-18 12:25 ` [Bug tree-optimization/98726] [10/11 Regression] " ktkachov at gcc dot gnu.org
2021-01-26 12:29 ` rguenth at gcc dot gnu.org
2021-01-26 12:30 ` rguenth at gcc dot gnu.org
2021-01-26 12:42 ` rguenth at gcc dot gnu.org
2021-01-26 13:27 ` cvs-commit at gcc dot gnu.org
2021-01-26 13:30 ` rguenth at gcc dot gnu.org
2021-02-19 12:26 ` avieira at gcc dot gnu.org
2021-02-19 12:27 ` avieira at gcc dot gnu.org
2021-03-17 15:41 ` rsandifo at gcc dot gnu.org
2021-03-30 11:04 ` rsandifo at gcc dot gnu.org
2021-03-31 18:34 ` cvs-commit at gcc dot gnu.org
2021-03-31 20:38 ` rsandifo at gcc dot gnu.org
2021-04-23 9:10 ` cvs-commit at gcc dot gnu.org
2021-04-23 9:10 ` cvs-commit 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-98726-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).