public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/48585] [4.7 Regression] 483.xalancbmk in SPEC CPU 2006 failed to build Date: Wed, 13 Apr 2011 14:56:00 -0000 [thread overview] Message-ID: <bug-48585-4-WwOeOAw0v1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48585-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48585 Martin Jambor <jamborm at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hubicka at gcc dot gnu.org --- Comment #3 from Martin Jambor <jamborm at gcc dot gnu.org> 2011-04-13 14:55:48 UTC --- Compilation segfaults in LTRANS stage on line 1738 in tree-inline.c (the assert below) because the dereferenced dest is zero. /* Constant propagation on argument done during inlining may create new direct call. Produce an edge for it. */ if ((!edge || (edge->indirect_inlining_edge && id->transform_call_graph_edges == CB_CGE_MOVE_CLONES)) && (fn = gimple_call_fndecl (stmt)) != NULL) { struct cgraph_node *dest = cgraph_get_node (fn); /* We have missing edge in the callgraph. This can happen when previous inlining turned an indirect call into a direct call by constant propagating arguments or we are producing dead clone (for further cloning). In all other cases we hit a bug (incorrect node sharing is the most common reason for missing edges). */ gcc_assert (dest->needed || !dest->analyzed || dest->address_taken || !id->src_node->analyzed || !id->dst_node->analyzed); fn is <function_decl 0x7ffff65d3300 __comp_dtor> id->transform_call_graph_edges is CB_CGE_MOVE_CLONES calling cgraph_edge (id->dst_node, stmt) from within the debugger (to get edge which it says is optimized out) returns NULL. I'd rather avoid calling cgraph_get_create_node here, the node should be created by whatever inserts it into the IL. Let me check whether the bug goes away if I disable IPA-CP first.
next prev parent reply other threads:[~2011-04-13 14:56 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-13 4:31 [Bug middle-end/48585] New: " hjl.tools at gmail dot com 2011-04-13 12:12 ` [Bug middle-end/48585] " rguenth at gcc dot gnu.org 2011-04-13 13:06 ` hjl.tools at gmail dot com 2011-04-13 13:39 ` jamborm at gcc dot gnu.org 2011-04-13 14:56 ` jamborm at gcc dot gnu.org [this message] 2011-04-13 15:39 ` jamborm at gcc dot gnu.org 2011-04-15 9:22 ` hubicka at ucw dot cz 2011-04-15 17:52 ` jamborm at gcc dot gnu.org 2011-04-15 18:34 ` jamborm at gcc dot gnu.org 2011-04-20 17:25 ` jamborm at gcc dot gnu.org 2011-04-20 18:17 ` jamborm at gcc dot gnu.org 2011-04-21 11:08 ` hubicka at gcc dot gnu.org 2011-04-21 13:17 ` jamborm at gcc dot gnu.org 2011-04-21 18:03 ` jamborm at gcc dot gnu.org 2011-04-22 8:46 ` hubicka at ucw dot cz 2011-04-22 12:37 ` jamborm at gcc dot gnu.org 2011-04-22 12:52 ` jamborm at gcc dot gnu.org 2011-04-22 13:02 ` jamborm at gcc dot gnu.org 2011-04-26 8:57 ` 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-48585-4-WwOeOAw0v1@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).