public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "patrick at rivosinc dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/114196] New: [13/14 Regression] Fixed length vector ICE: in vect_peel_nonlinear_iv_init, at tree-vect-loop.cc:9454
Date: Fri, 01 Mar 2024 21:35:00 +0000 [thread overview]
Message-ID: <bug-114196-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114196
Bug ID: 114196
Summary: [13/14 Regression] Fixed length vector ICE: in
vect_peel_nonlinear_iv_init, at tree-vect-loop.cc:9454
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: patrick at rivosinc dot com
Target Milestone: ---
Created attachment 57589
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57589&action=edit
-freport-bug output
Testcase:
unsigned a;
int b;
long *c;
int main() {
for (short d = 1; d < (short)5443215699099219 - 15932; d += 94 - 90) {
b = ({
__typeof__(0) e = c[d];
e;
})
?: -c[d];
a *= 3;
}
}
Backtrace:
> /scratch/tc-testing/tc-feb-20/build-rv64gcv/bin/riscv64-unknown-linux-gnu-gcc -march=rv64gcv_zvl256b -O3 --param=riscv-autovec-preference=fixed-vlmax red.c -o red.out
during GIMPLE pass: vect
./red.c: In function 'main':
./red.c:4:5: internal compiler error: in vect_peel_nonlinear_iv_init, at
tree-vect-loop.cc:9454
4 | int main() {
| ^~~~
0xb04d35 vect_peel_nonlinear_iv_init(gimple**, tree_node*, tree_node*,
tree_node*, vect_induction_op_type)
../../../gcc/gcc/tree-vect-loop.cc:9454
0x15e6c54 vect_update_ivs_after_vectorizer
../../../gcc/gcc/tree-vect-loop-manip.cc:2368
0x15f3ca7 vect_do_peeling(_loop_vec_info*, tree_node*, tree_node*, tree_node**,
tree_node**, tree_node**, int, bool, bool, tree_node**)
../../../gcc/gcc/tree-vect-loop-manip.cc:3501
0x15e198e vect_transform_loop(_loop_vec_info*, gimple*)
../../../gcc/gcc/tree-vect-loop.cc:11934
0x1627a01 vect_transform_loops
../../../gcc/gcc/tree-vectorizer.cc:1006
0x1628173 try_vectorize_loop_1
../../../gcc/gcc/tree-vectorizer.cc:1152
0x1628173 try_vectorize_loop
../../../gcc/gcc/tree-vectorizer.cc:1182
0x16287fc execute
../../../gcc/gcc/tree-vectorizer.cc:1298
Please submit a full bug report, with preprocessed source (by using
-freport-bug).
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
Godbolt: https://godbolt.org/z/eeEan1hvv
Tested/found using r14-9084-g61ab046a327 (not bisected)
Found via fuzzer.
next reply other threads:[~2024-03-01 21:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 21:35 patrick at rivosinc dot com [this message]
2024-03-02 2:02 ` [Bug middle-end/114196] " pinskia at gcc dot gnu.org
2024-03-06 16:09 ` rdapp at gcc dot gnu.org
2024-03-07 20:03 ` cvs-commit at gcc dot gnu.org
2024-03-08 17:43 ` patrick at rivosinc dot com
2024-03-08 17:44 ` patrick at rivosinc dot com
2024-03-09 7:34 ` [Bug middle-end/114196] [13 " law at gcc dot gnu.org
2024-05-08 12:25 ` rguenth at gcc dot gnu.org
2024-05-13 6:23 ` rdapp at gcc dot gnu.org
2024-05-21 9:19 ` jakub 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-114196-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).