public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/108601] New: [13 Regression] vector peeling ICEs with PGO + LTO + IPA inlining in gcc_r in SPEC2017
Date: Mon, 30 Jan 2023 15:43:06 +0000 [thread overview]
Message-ID: <bug-108601-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108601
Bug ID: 108601
Summary: [13 Regression] vector peeling ICEs with PGO + LTO +
IPA inlining in gcc_r in SPEC2017
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: tnfchris at gcc dot gnu.org
Target Milestone: ---
PGO seems fine, LTO seems fine, but PGO + LTO + increase inlining makes it
crash.
Full options:
-fprofile-generate -mcpu=native -Ofast -fomit-frame-pointer -flto=auto --param
ipa-cp-eval-threshold=1 --param ipa-cp-unit-growth=80
GCC 12 seems fine.
I'm still trying to reduce (it's a combination of my worst nightmares :( ), but
in the mean time here's the crash
during GIMPLE pass: vect
opts.c: In function 'common_handle_option':
opts.c:1456:1: internal compiler error: in vect_peel_nonlinear_iv_init, at
tree-vect-loop.cc:8664
1456 | common_handle_option (size_t scode, const char *arg, int value,
| ^
0xdcff4b vect_peel_nonlinear_iv_init(gimple**, tree_node*, tree_node*,
tree_node*, vect_induction_op_type)
/opt/buildAgent/work/5c94c4ced6ebfcd0/gcc/tree-vect-loop.cc:8664
0xdee503 vect_update_ivs_after_vectorizer
/opt/buildAgent/work/5c94c4ced6ebfcd0/gcc/tree-vect-loop-manip.cc:1594
0xdee503 vect_do_peeling(_loop_vec_info*, tree_node*, tree_node*, tree_node**,
tree_node**, tree_node**, int, bool, bool, tree_node**)
/opt/buildAgent/work/5c94c4ced6ebfcd0/gcc/tree-vect-loop-manip.cc:2999
0xde49d7 vect_transform_loop(_loop_vec_info*, gimple*)
/opt/buildAgent/work/5c94c4ced6ebfcd0/gcc/tree-vect-loop.cc:10837
0xe17447 vect_transform_loops
/opt/buildAgent/work/5c94c4ced6ebfcd0/gcc/tree-vectorizer.cc:1007
0xe17a8b try_vectorize_loop_1
/opt/buildAgent/work/5c94c4ced6ebfcd0/gcc/tree-vectorizer.cc:1153
0xe17a8b try_vectorize_loop
/opt/buildAgent/work/5c94c4ced6ebfcd0/gcc/tree-vectorizer.cc:1183
0xe17f6b execute
/opt/buildAgent/work/5c94c4ced6ebfcd0/gcc/tree-vectorizer.cc:1299
next reply other threads:[~2023-01-30 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 15:43 tnfchris at gcc dot gnu.org [this message]
2023-01-30 16:05 ` [Bug tree-optimization/108601] " pinskia at gcc dot gnu.org
2023-01-31 7:25 ` rguenth at gcc dot gnu.org
2023-01-31 7:29 ` rguenth at gcc dot gnu.org
2023-01-31 7:49 ` crazylht at gmail dot com
2023-01-31 8:28 ` crazylht at gmail dot com
2023-01-31 9:05 ` tnfchris at gcc dot gnu.org
2023-01-31 20:24 ` [Bug tree-optimization/108601] [13 Regression] vector peeling ICEs with VLA in gcc_r in SPEC2017 since g:c13223b790bbc5e4a3f5605e057eac59b61b2c85 tnfchris at gcc dot gnu.org
2023-01-31 21:08 ` tnfchris at gcc dot gnu.org
2023-02-01 5:32 ` crazylht at gmail dot com
2023-02-01 7:29 ` crazylht at gmail dot com
2023-02-01 7:32 ` rguenther at suse dot de
2023-02-01 7:46 ` crazylht at gmail dot com
2023-02-01 8:41 ` rguenth at gcc dot gnu.org
2023-02-01 9:07 ` crazylht at gmail dot com
2023-02-02 9:02 ` cvs-commit at gcc dot gnu.org
2023-02-03 8:05 ` 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-108601-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).