public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/51929] [4.7 Regression] ICE: verify_cgraph_node failed with -O2 -fno-guess-branch-probability -fipa-cp-clone Date: Fri, 10 Feb 2012 11:28:00 -0000 [thread overview] Message-ID: <bug-51929-4-yVMG3WbWLF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-51929-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51929 --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-02-10 11:27:39 UTC --- What happens is that cgraph_materialize_clone on the _ZN1BIcEC2E1Ai.constprop.1 clone performs: 2451 if (!node->clone_of->analyzed && !node->clone_of->clones) 2452 { 2453 cgraph_release_function_body (node->clone_of); 2454 cgraph_node_remove_callees (node->clone_of); 2455 ipa_remove_all_references (&node->clone_of->ref_list); 2456 } 2457 node->clone_of = NULL; where node->clone_of is _ZN1BIcEC2E1Ai, i.e. the __base_ctor and so the verification fails. Even before this cgraph_remove_unreachable_nodes marks the _ZN1BIcEC1E1Ai (i.e. __comp_ctor to which the call_stmts still refer) as unreachable and calls ipa_remove_all_references on it, which means I don't see a way how we could get from the _ZN1BIcEC2E1Ai to _ZN1BIcEC1E1Ai node anymore. Honza?
next prev parent reply other threads:[~2012-02-10 11:28 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-21 11:34 [Bug middle-end/51929] New: ICE: verify_cgraph_node failed with -O2 -fno-guess-branch-probability -fipa-cp-clone --param ipa-cp-eval-threshold=0 --param max-inline-insns-single=1 zsojka at seznam dot cz 2012-02-05 15:15 ` [Bug middle-end/51929] [4.7 Regression] ICE: verify_cgraph_node failed with -O2 -fno-guess-branch-probability -fipa-cp-clone zsojka at seznam dot cz 2012-02-06 12:37 ` rguenth at gcc dot gnu.org 2012-02-07 15:40 ` rguenth at gcc dot gnu.org 2012-02-09 16:52 ` jakub at gcc dot gnu.org 2012-02-09 16:56 ` zsojka at seznam dot cz 2012-02-09 18:43 ` jakub at gcc dot gnu.org 2012-02-10 10:33 ` jakub at gcc dot gnu.org 2012-02-10 11:28 ` jakub at gcc dot gnu.org [this message] 2012-02-10 11:49 ` jakub at gcc dot gnu.org 2012-02-10 12:32 ` hubicka at gcc dot gnu.org 2012-02-16 7:34 ` jakub at gcc dot gnu.org 2012-02-16 7:47 ` jakub 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-51929-4-yVMG3WbWLF@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).