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 lto/49796] [4.7 Regression] 483.xalancbmk/447.dealII in SPEC CPU 2006 failed to build Date: Thu, 21 Jul 2011 12:23:00 -0000 [thread overview] Message-ID: <bug-49796-4-bplUqQ1pvr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49796-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49796 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-07-21 12:22:33 UTC --- verify_edge_corresponds_to_fndecl fails. The reason is that e->callee->former_clone_of is NULL. Since e->callee is _ZN10xalanc_1_814XalanDOMStringC2EPKtj.constprop.15198, that is clearly incorrect. Moreover, the node corresponding to decl, which is "__comp_ctor," does not have an alias flag set. I think that the name implies it should be set too. gimple_has_body returns false for it and, perhaps most importantly, it's analyzed flag and analyzed flag of e->callee->analyzed are cleared too. This is all in ltrans stage of LTO. I assume the flags are weird here because the cloned function, its original and its alias end up in a different partition. I have tried building with -flto-partition=none and it succeeded which supports this theory. Perhaps we just should not do this check for !analyzed nodes? Or should we try to stream this info into different partitions too? Honza?
next prev parent reply other threads:[~2011-07-21 12:23 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-20 14:37 [Bug lto/49796] New: " hjl.tools at gmail dot com 2011-07-20 14:48 ` [Bug lto/49796] " rguenth at gcc dot gnu.org 2011-07-20 15:38 ` rguenth at gcc dot gnu.org 2011-07-20 16:41 ` jamborm at gcc dot gnu.org 2011-07-21 12:23 ` jamborm at gcc dot gnu.org [this message] 2011-07-22 11:24 ` jamborm at gcc dot gnu.org 2011-07-22 15:36 ` jamborm at gcc dot gnu.org 2011-07-22 15:40 ` 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-49796-4-bplUqQ1pvr@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).