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 lto/105012] New: [12 Regression] wrf from SPECCPU2017 ICEs during LTO linking
Date: Tue, 22 Mar 2022 08:54:05 +0000 [thread overview]
Message-ID: <bug-105012-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105012
Bug ID: 105012
Summary: [12 Regression] wrf from SPECCPU2017 ICEs during LTO
linking
Product: gcc
Version: 12.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: tnfchris at gcc dot gnu.org
CC: marxin at gcc dot gnu.org
Target Milestone: ---
Target: aarch64-*
wrf when linking with -mcpu=native -Ofast -fomit-frame-pointer -flto=auto
--param ipa-cp-eval-threshold=1 --param ipa-cp-unit-growth=80 (have not reduced
flags yet) fails during final link with:
during GIMPLE pass: ifcvt
module_cam_mp_ndrop.fppized.f90: In function 'dropmixnuc':
module_cam_mp_ndrop.fppized.f90:33:27: internal compiler error: Segmentation
fault
33 | subroutine dropmixnuc(lchnk, ncol, ncldwtr,tendnd, temp,omega, &
| ^
0xb9bee3 crash_signal
/data/tamar/ci/work/5c94c4ced6ebfcd0/gcc/toplev.cc:322
0xc93978 first_imm_use_stmt
/data/tamar/ci/work/5c94c4ced6ebfcd0/gcc/ssa-iterators.h:932
0xc93978 dse_classify_store(ao_ref*, gimple*, bool, simple_bitmap_def*, bool*,
tree_node*)
/data/tamar/ci/work/5c94c4ced6ebfcd0/gcc/tree-ssa-dse.cc:954
0xbf9263 ifcvt_local_dce
/data/tamar/ci/work/5c94c4ced6ebfcd0/gcc/tree-if-conv.cc:3154
0xbfe1b7 tree_if_conversion(loop*, vec<gimple*, va_heap, vl_ptr>*)
/data/tamar/ci/work/5c94c4ced6ebfcd0/gcc/tree-if-conv.cc:3383
0xc000af execute
/data/tamar/ci/work/5c94c4ced6ebfcd0/gcc/tree-if-conv.cc:3461
0xc000af execute
/data/tamar/ci/work/5c94c4ced6ebfcd0/gcc/tree-if-conv.cc:3449
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.
make[1]: *** [/opt/buildAgent/temp/buildTmp/ccGjHi3g.ltrans8.ltrans.o] Error 1
This has started somewhere between g:79e210f0c8e1fad875333e93b5ae2fe9b4879b7a
and g:9fc8f278ebebc57537dc0cb9d33e36d932be0bc3
Sorry for the lack of a small reproducer, still need to learn how to reduce LTO
cases properly..
Note that this range does contain a fix for the threader failure for wrf in
PR102943 but not sure if related.
next reply other threads:[~2022-03-22 8:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 8:54 tnfchris at gcc dot gnu.org [this message]
2022-03-22 9:36 ` [Bug lto/105012] " marxin at gcc dot gnu.org
2022-03-22 10:21 ` rguenth at gcc dot gnu.org
2022-03-22 10:23 ` rguenth at gcc dot gnu.org
2022-03-22 10:37 ` marxin at gcc dot gnu.org
2022-03-22 10:52 ` rguenth at gcc dot gnu.org
2022-03-22 10:53 ` [Bug lto/105012] [12 Regression] wrf from SPECCPU2017 ICEs during LTO linking since r12-7692-g8db155ddf8cec9 marxin at gcc dot gnu.org
2022-03-22 10:58 ` marxin at gcc dot gnu.org
2022-03-22 11:06 ` [Bug fortran/105012] " rguenth at gcc dot gnu.org
2022-03-22 11:09 ` marxin at gcc dot gnu.org
2022-03-22 11:11 ` rguenth at gcc dot gnu.org
2022-03-22 11:18 ` rguenth at gcc dot gnu.org
2022-03-22 11:20 ` rguenth at gcc dot gnu.org
2022-03-22 11:31 ` rguenth at gcc dot gnu.org
2022-03-22 13:05 ` cvs-commit at gcc dot gnu.org
2022-03-22 13:07 ` rguenth at gcc dot gnu.org
2022-05-06 8:33 ` [Bug fortran/105012] [12/13 " jakub at gcc dot gnu.org
2022-08-24 19:36 ` anlauf at gcc dot gnu.org
2022-08-24 20:34 ` anlauf at gcc dot gnu.org
2022-08-25 6:13 ` rguenth at gcc dot gnu.org
2022-08-25 6:18 ` rguenth at gcc dot gnu.org
2022-08-25 19:50 ` mikael at gcc dot gnu.org
2022-08-25 19:55 ` anlauf at gcc dot gnu.org
2022-08-25 19:57 ` anlauf at gcc dot gnu.org
2022-08-25 20:06 ` mikael at gcc dot gnu.org
2022-08-25 20:30 ` anlauf at gcc dot gnu.org
2022-08-25 20:40 ` mikael at gcc dot gnu.org
2022-08-25 20:47 ` anlauf at gcc dot gnu.org
2022-08-25 21:19 ` mikael at gcc dot gnu.org
2022-08-25 21:31 ` anlauf at gcc dot gnu.org
2022-08-28 10:27 ` mikael at gcc dot gnu.org
2022-09-02 19:04 ` mikael at gcc dot gnu.org
2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org
2022-09-25 12:48 ` cvs-commit at gcc dot gnu.org
2022-10-10 20:04 ` cvs-commit at gcc dot gnu.org
2022-10-10 20:53 ` cvs-commit at gcc dot gnu.org
2022-10-12 12:34 ` cvs-commit at gcc dot gnu.org
2022-10-12 12:42 ` mikael 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-105012-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).