public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/107944] [11/12/13 Regression] ICE in cgraph_node::get_untransformed_body since r13-48-g27ee75dbe81bb7
Date: Thu, 02 Feb 2023 11:28:57 +0000 [thread overview]
Message-ID: <bug-107944-4-LKgFNGvCl7@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107944-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107944
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Martin Jambor
<jamborm@gcc.gnu.org>:
https://gcc.gnu.org/g:e36385be53d51539e1c295a80085115b24fede32
commit r11-10496-ge36385be53d51539e1c295a80085115b24fede32
Author: Martin Jambor <mjambor@suse.cz>
Date: Thu Feb 2 12:22:22 2023 +0100
ipa: Release body more carefully when removing nodes (PR 107944)
The code removing function bodies when the last call graph clone of a
node is removed is too aggressive when there are nodes up the
clone_of chain which still need them. Fixed by expanding the check.
gcc/ChangeLog:
2023-01-18 Martin Jambor <mjambor@suse.cz>
PR ipa/107944
* cgraph.c (cgraph_node::remove): Check whether nodes up the
lcone_of chain also do not need the body.
(cherry picked from commit db959e250077ae6b4fc08f53fb322719582c5de6)
next prev parent reply other threads:[~2023-02-02 11:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-01 9:12 [Bug ipa/107944] New: " marxin at gcc dot gnu.org
2022-12-01 9:12 ` [Bug ipa/107944] " marxin at gcc dot gnu.org
2022-12-01 9:52 ` [Bug ipa/107944] [12/13 Regression] " rguenth at gcc dot gnu.org
2022-12-21 10:59 ` [Bug ipa/107944] [11/12/13 " rguenth at gcc dot gnu.org
2022-12-28 9:21 ` marxin at gcc dot gnu.org
2023-01-18 14:44 ` cvs-commit at gcc dot gnu.org
2023-02-01 17:58 ` cvs-commit at gcc dot gnu.org
2023-02-02 11:28 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-02 11:30 ` 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-107944-4-LKgFNGvCl7@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).