public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "admin at levyhsu dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/111858] New: [14 Regression] ICE: in vectorizable_simd_clone_call, at tree-vect-stmts.cc:4263
Date: Wed, 18 Oct 2023 06:48:17 +0000 [thread overview]
Message-ID: <bug-111858-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111858
Bug ID: 111858
Summary: [14 Regression] ICE: in vectorizable_simd_clone_call,
at tree-vect-stmts.cc:4263
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: admin at levyhsu dot com
Target Milestone: ---
This bug appears to be caused by a commit r14-4628-g63eaccd114393f
(63eaccd114393f4692976bb78b30148e6d77a89e)
When compiling spec2017 527.cam4_r with
-march=native -Ofast -funroll-loops -flto
on Sapphire Rapids or
-march=sapphirerapids on other host:
radsw.fppized.f90: In function 'raddedmx.isra':
radsw.fppized.f90:2017:19: internal compiler error: in
vectorizable_simd_clone_call, at tree-vect-stmts.cc:4263
2017 | subroutine raddedmx(coszrs ,ndayc ,abh2o , &
| ^
0x8d3fad vectorizable_simd_clone_call
../../gcc/tree-vect-stmts.cc:4263
0x1e4693e vect_analyze_stmt(vec_info*, _stmt_vec_info*, bool*, _slp_tree*,
_slp_instance*, vec<stmt_info_for_cost, va_heap, vl_ptr>*)
../../gcc/tree-vect-stmts.cc:12672
0x116255c vect_analyze_loop_operations
../../gcc/tree-vect-loop.cc:2087
0x116255c vect_analyze_loop_2
../../gcc/tree-vect-loop.cc:2903
0x1162ecf vect_analyze_loop_1
../../gcc/tree-vect-loop.cc:3339
0x11635d3 vect_analyze_loop(loop*, vec_info_shared*)
../../gcc/tree-vect-loop.cc:3493
0x11a1981 try_vectorize_loop_1
../../gcc/tree-vectorizer.cc:1064
0x11a1981 try_vectorize_loop
../../gcc/tree-vectorizer.cc:1180
0x11a21e4 execute
../../gcc/tree-vectorizer.cc:1296
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.
lto-wrapper: fatal error: gfortran returned 1 exit status
compilation terminated.
Which matches the changes in vectorizable_simd_clone_call.
next reply other threads:[~2023-10-18 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 6:48 admin at levyhsu dot com [this message]
2023-10-18 7:37 ` [Bug tree-optimization/111858] " rguenth at gcc dot gnu.org
2023-10-18 7:37 ` rguenth at gcc dot gnu.org
2023-10-18 10:22 ` admin at levyhsu dot com
2023-10-18 10:22 ` admin at levyhsu dot com
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-111858-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).