public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/107925] New: ICE in update_specialized_profile at gcc/ipa-cp.cc:5082 for 531.deepsjeng_r benchmark
Date: Tue, 29 Nov 2022 20:46:18 +0000 [thread overview]
Message-ID: <bug-107925-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107925
Bug ID: 107925
Summary: ICE in update_specialized_profile at
gcc/ipa-cp.cc:5082 for 531.deepsjeng_r benchmark
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: jamborm at gcc dot gnu.org, marxin at gcc dot gnu.org,
tnfchris at gcc dot gnu.org
Target Milestone: ---
Created attachment 53985
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=53985&action=edit
test-case
Noticed by Tamar and their testers using fancy parameters:
$ g++ -march=native -Ofast -flto=auto --param ipa-cp-eval-threshold=1 *.ii
-fprofile-use
during IPA pass: cp
lto1: internal compiler error: in operator>=, at profile-count.h:999
0x814bcc profile_count::operator>=(profile_count const&) const
/home/marxin/Programming/gcc/gcc/profile-count.h:999
0x814bcc profile_count::operator>=(profile_count const&) const
/home/marxin/Programming/gcc/gcc/profile-count.h:991
0x814bcc update_specialized_profile
/home/marxin/Programming/gcc/gcc/ipa-cp.cc:5082
0x1be1689 perhaps_add_new_callers<tree_node*>
/home/marxin/Programming/gcc/gcc/ipa-cp.cc:5932
0x1be1689 decide_about_value<tree_node*>
/home/marxin/Programming/gcc/gcc/ipa-cp.cc:6038
0x1be40cc decide_whether_version_node
/home/marxin/Programming/gcc/gcc/ipa-cp.cc:6190
0x1be5c02 ipcp_decision_stage
/home/marxin/Programming/gcc/gcc/ipa-cp.cc:6388
0x1be5c02 ipcp_driver
/home/marxin/Programming/gcc/gcc/ipa-cp.cc:6576
0x1be5c02 execute
/home/marxin/Programming/gcc/gcc/ipa-cp.cc:6651
The issue is likely not new in GCC 13, but as it uses profile, I hasn'y
bisected that.
next reply other threads:[~2022-11-29 20:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 20:46 marxin at gcc dot gnu.org [this message]
2022-11-29 20:46 ` [Bug ipa/107925] " marxin at gcc dot gnu.org
2022-11-29 20:46 ` marxin at gcc dot gnu.org
2022-11-29 20:47 ` marxin at gcc dot gnu.org
2022-11-29 20:58 ` pinskia at gcc dot gnu.org
2023-01-27 10:15 ` tnfchris at gcc dot gnu.org
2023-02-17 17:20 ` jamborm at gcc dot gnu.org
2023-02-22 9:55 ` jamborm at gcc dot gnu.org
2023-03-14 17:57 ` cvs-commit at gcc dot gnu.org
2023-03-14 17:57 ` cvs-commit at gcc dot gnu.org
2023-03-14 17:58 ` jamborm at gcc dot gnu.org
2023-03-22 16:05 ` cvs-commit at gcc dot gnu.org
2023-03-22 16:06 ` jamborm 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-107925-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).