public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at kam dot mff.cuni.cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/103277] [12 Regression] ICE in branch_prob with -O1 -fbranch-probabilities -fno-ipa-pure-const since r12-5236-g5aa91072e24c1e16
Date: Thu, 18 Nov 2021 08:47:53 +0000 [thread overview]
Message-ID: <bug-103277-4-t2avQTVuLC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103277-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103277
--- Comment #4 from hubicka at kam dot mff.cuni.cz ---
> Btw. started with r12-5236-g5aa91072e24c1e16.
Yep, I know - it is modref based DSE that lets us to enable that call as
dead. So the bug is technically mine if Richi decides to pass it to me
:)
We need to keep track if cleanup_cfg is needed by testing whether
removed call had multpile exit edges, right?
next prev parent reply other threads:[~2021-11-18 8:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-16 16:42 [Bug ipa/103277] New: [12 Regression] ICE in branch_prob, at profile.c:1208 asolokha at gmx dot com
2021-11-17 5:35 ` [Bug ipa/103277] " pinskia at gcc dot gnu.org
2021-11-17 5:44 ` [Bug ipa/103277] [12 Regression] ICE in branch_prob with -O1 -fbranch-probabilities -fno-ipa-pure-const pinskia at gcc dot gnu.org
2021-11-18 8:00 ` rguenth at gcc dot gnu.org
2021-11-18 8:36 ` [Bug ipa/103277] [12 Regression] ICE in branch_prob with -O1 -fbranch-probabilities -fno-ipa-pure-const since r12-5236-g5aa91072e24c1e16 marxin at gcc dot gnu.org
2021-11-18 8:47 ` hubicka at kam dot mff.cuni.cz [this message]
2021-11-18 9:02 ` cvs-commit at gcc dot gnu.org
2021-11-18 9:02 ` 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-103277-4-t2avQTVuLC@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).