public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107055] New: [13 Regression] ICE in vect_peel_nonlinear_iv_init, at tree-vect-loop.cc:8415
Date: Tue, 27 Sep 2022 16:22:26 +0000 [thread overview]
Message-ID: <bug-107055-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107055
Bug ID: 107055
Summary: [13 Regression] ICE in vect_peel_nonlinear_iv_init, at
tree-vect-loop.cc:8415
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: gscfq@t-online.de
Target Milestone: ---
Started between 20220904 and 20220911 at -O1,
with file gcc.dg/torture/pr24257.c :
$ gcc-13-20220925 -c pr24257.c -O1 -fno-tree-dce -fno-vect-cost-model
-ftree-vectorize -fprofile-arcs
during GIMPLE pass: vect
pr24257.c: In function 'oof':
pr24257.c:20:6: internal compiler error: in vect_peel_nonlinear_iv_init, at
tree-vect-loop.cc:8415
20 | void oof(A *s, int n)
| ^~~
0x11a15b3 vect_peel_nonlinear_iv_init(gimple**, tree_node*, tree_node*,
tree_node*, vect_induction_op_type)
../../gcc/tree-vect-loop.cc:8415
0x11c6909 vect_update_ivs_after_vectorizer
../../gcc/tree-vect-loop-manip.cc:1582
0x11c6909 vect_do_peeling(_loop_vec_info*, tree_node*, tree_node*, tree_node**,
tree_node**, tree_node**, int, bool, bool, tree_node**)
../../gcc/tree-vect-loop-manip.cc:2987
0x11b8efc vect_transform_loop(_loop_vec_info*, gimple*)
../../gcc/tree-vect-loop.cc:10554
0x11fa09b vect_transform_loops
../../gcc/tree-vectorizer.cc:1008
0x11fa7d4 try_vectorize_loop_1
../../gcc/tree-vectorizer.cc:1153
0x11fa7d4 try_vectorize_loop
../../gcc/tree-vectorizer.cc:1185
0x11fae34 execute
../../gcc/tree-vectorizer.cc:1299
next reply other threads:[~2022-09-27 16:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 16:22 gscfq@t-online.de [this message]
2022-09-27 16:37 ` [Bug tree-optimization/107055] " pinskia at gcc dot gnu.org
2022-09-28 5:14 ` crazylht at gmail dot com
2022-09-28 7:01 ` crazylht at gmail dot com
2022-09-28 8:41 ` crazylht at gmail dot com
2022-09-28 8:42 ` crazylht at gmail dot com
2022-09-29 7:23 ` cvs-commit at gcc dot gnu.org
2022-09-29 7:24 ` crazylht at gmail dot com
2022-09-29 7:59 ` 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-107055-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).