public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/97551] [11 Regression] ICE: verify_cgraph_node failed with "-O2 -fno-toplevel-reorder -fno-tree-dce -fno-tree-forwprop -fno-tree-fre -fipa-cp-clone"
Date: Sun, 14 May 2023 21:55:38 +0000 [thread overview]
Message-ID: <bug-97551-4-fp60dcNhm4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97551-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97551
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|ICE: verify_cgraph_node |[11 Regression] ICE:
|failed with "-O2 |verify_cgraph_node failed
|-fno-toplevel-reorder |with "-O2
|-fno-tree-dce |-fno-toplevel-reorder
|-fno-tree-forwprop |-fno-tree-dce
|-fno-tree-fre |-fno-tree-forwprop
|-fipa-cp-clone" |-fno-tree-fre
| |-fipa-cp-clone"
Resolution|--- |FIXED
Status|NEW |RESOLVED
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=97576
Target Milestone|--- |11.0
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Been fixed for a few years now even in GCC 11.
So closing as such.
I suspect it was fixed by the same patch as PR 97576.
prev parent reply other threads:[~2023-05-14 21:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 15:43 [Bug c/97551] New: " suochenyao at 163 dot com
2020-10-26 9:54 ` [Bug ipa/97551] " marxin at gcc dot gnu.org
2021-04-27 11:39 ` jakub at gcc dot gnu.org
2021-07-28 7:04 ` rguenth at gcc dot gnu.org
2023-05-14 21:55 ` pinskia at gcc dot gnu.org [this message]
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-97551-4-fp60dcNhm4@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).