public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/96974] New: [10/11 Regression] ICE in vect_get_vector_types_for_stmt compiling for SVE
Date: Tue, 08 Sep 2020 11:20:45 +0000 [thread overview]
Message-ID: <bug-96974-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96974
Bug ID: 96974
Summary: [10/11 Regression] ICE in
vect_get_vector_types_for_stmt compiling for SVE
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: ktkachov at gcc dot gnu.org
Target Milestone: ---
Target: aarch64*-*-*
The reduced testcase:
float a;
int
b ()
{ return __builtin_lrintf(a); }
struct c {
float d;
c() {
for (int e = 0; e < 9; e++)
coeffs[e] = d ? b() : 0;
}
int coeffs[10];
} f;
ICEs with g++ -Ofast -march=armv8.2-a+sve
during GIMPLE pass: slp
foo.cc: In function '(static initializers for foo.cc)':
foo.cc:14:4: internal compiler error: in vect_get_vector_types_for_stmt, at
tree-vect-stmts.c:12055
14 | } f;
| ^
0x126e44d vect_get_vector_types_for_stmt(vec_info*, _stmt_vec_info*,
tree_node**, tree_node**, unsigned int)
$SRC/gcc/tree-vect-stmts.c:12054
0x12a7b9a vect_build_slp_tree_1
$SRC/gcc/tree-vect-slp.c:801
0x12a7b9a vect_build_slp_tree_2
$SRC/gcc/tree-vect-slp.c:1284
0x12a642b vect_build_slp_tree
$SRC/gcc/tree-vect-slp.c:1195
0x12a8a30 vect_build_slp_tree_2
$SRC/gcc/tree-vect-slp.c:1413
0x12a642b vect_build_slp_tree
$SRC/gcc/tree-vect-slp.c:1195
0x12a8a30 vect_build_slp_tree_2
$SRC/gcc/tree-vect-slp.c:1413
0x12a642b vect_build_slp_tree
$SRC/gcc/tree-vect-slp.c:1195
0x12ab23e vect_analyze_slp_instance
$SRC/gcc/tree-vect-slp.c:2210
0x12aea06 vect_analyze_slp(vec_info*, unsigned int)
$SRC/gcc/tree-vect-slp.c:2418
0x12b0fc3 vect_slp_analyze_bb_1
$SRC/gcc/tree-vect-slp.c:3388
0x12b0fc3 vect_slp_region
$SRC/gcc/tree-vect-slp.c:3498
0x12b0fc3 vect_slp_bb(basic_block_def*)
$SRC/gcc/tree-vect-slp.c:3628
0x12b4a70 execute
$SRC/gcc/tree-vectorizer.c:1429
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:[~2020-09-08 11:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 11:20 ktkachov at gcc dot gnu.org [this message]
2020-09-08 11:21 ` [Bug tree-optimization/96974] " ktkachov at gcc dot gnu.org
2020-09-08 13:03 ` rguenth at gcc dot gnu.org
2020-10-15 15:36 ` stammark at gcc dot gnu.org
2021-01-05 10:09 ` ktkachov at gcc dot gnu.org
2021-01-18 10:29 ` stammark at gcc dot gnu.org
2021-01-18 10:38 ` rsandifo at gcc dot gnu.org
2021-01-18 13:32 ` stammark at gcc dot gnu.org
2021-01-18 13:48 ` rsandifo at gcc dot gnu.org
2021-01-18 13:52 ` stammark at gcc dot gnu.org
2021-01-28 11:47 ` stammark at gcc dot gnu.org
2021-01-28 11:47 ` stammark at gcc dot gnu.org
2021-01-28 11:59 ` rsandifo at gcc dot gnu.org
2021-01-28 13:12 ` rguenth at gcc dot gnu.org
2021-03-25 15:30 ` cvs-commit at gcc dot gnu.org
2021-03-25 15:32 ` cvs-commit at gcc dot gnu.org
2021-03-31 9:42 ` ktkachov at gcc dot gnu.org
2021-03-31 9:54 ` rguenth at gcc dot gnu.org
2021-03-31 13:57 ` cvs-commit at gcc dot gnu.org
2021-03-31 13:59 ` 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-96974-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).