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/100413] [11/12/13 Regression] ICE: failed to reclaim unneeded function with custom flags since r11-4267-g0e590b68fa374365 Date: Fri, 29 Apr 2022 15:39:48 +0000 [thread overview] Message-ID: <bug-100413-4-ztRIv7KcBG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100413-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100413 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Martin Jambor <jamborm@gcc.gnu.org>: https://gcc.gnu.org/g:27ee75dbe81bb781214c66a9e6a759c08b7deb60 commit r13-48-g27ee75dbe81bb781214c66a9e6a759c08b7deb60 Author: Martin Jambor <mjambor@suse.cz> Date: Fri Apr 29 17:38:15 2022 +0200 ipa: Release body of clone_of when removing its last clone (PR 100413) In the PR, the verifier complains that we did not manage to remove the body of a node and it is right. The node is kept for materialization of two clones but after one is materialized, the other one is removed as unneeded (as a part of delete_unreachable_blocks_update_callgraph). The problem is that the node removal does not check for this situation and can leave the clone_of node there with a body attached to it even though there is no use for it any more. This patch does checks for it and handles the situation in a simlar way that cgraph_node::materialize_clone does it, except that it also has to be careful that the removed node itself does not have any clones, which would still need the clone_of's body. Failing to do that results in a bootstrap failure. gcc/ChangeLog: 2022-04-27 Martin Jambor <mjambor@suse.cz> PR ipa/100413 * cgraph.cc (cgraph_node::remove): Release body of the node this is clone_of if appropriate. gcc/testsuite/ChangeLog: 2022-04-27 Martin Jambor <mjambor@suse.cz> PR ipa/100413 * g++.dg/ipa/pr100413.C: New test.
next prev parent reply other threads:[~2022-04-29 15:39 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-04 10:57 [Bug ipa/100413] New: [11/12 Regression] ICE: failed to reclaim unneeded function with custom flags zsojka at seznam dot cz 2021-05-04 12:49 ` [Bug ipa/100413] " rguenth at gcc dot gnu.org 2021-05-10 12:25 ` marxin at gcc dot gnu.org 2021-07-28 7:06 ` rguenth at gcc dot gnu.org 2021-08-13 14:14 ` [Bug ipa/100413] [11/12 Regression] ICE: failed to reclaim unneeded function with custom flags since r11-4267-g0e590b68fa374365 marxin at gcc dot gnu.org 2022-01-17 14:57 ` rguenth at gcc dot gnu.org 2022-04-21 7:49 ` rguenth at gcc dot gnu.org 2022-04-27 14:57 ` jamborm at gcc dot gnu.org 2022-04-28 9:19 ` jamborm at gcc dot gnu.org 2022-04-29 15:39 ` cvs-commit at gcc dot gnu.org [this message] 2022-04-29 15:54 ` [Bug ipa/100413] [11/12/13 " jamborm at gcc dot gnu.org 2022-05-11 21:29 ` cvs-commit at gcc dot gnu.org 2022-05-19 12:07 ` cvs-commit at gcc dot gnu.org 2022-05-19 12:08 ` 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-100413-4-ztRIv7KcBG@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: linkBe 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).