public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/60899] undef reference generated with -fdevirtualize-speculatively Date: Sun, 20 Apr 2014 07:23:00 -0000 [thread overview] Message-ID: <bug-60899-4-JZEKgVEPNU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60899-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60899 --- Comment #5 from Jan Hubicka <hubicka at gcc dot gnu.org> --- I am running benchmarks I do not want to disturb, but the following should fix the problem. $ svn diff ../../gcc/gimple-fold.c Index: ../../gcc/gimple-fold.c =================================================================== --- ../../gcc/gimple-fold.c (revision 209526) +++ ../../gcc/gimple-fold.c (working copy) @@ -105,7 +105,9 @@ can_refer_decl_in_current_unit_p (tree d external var. */ if (!from_decl || TREE_CODE (from_decl) != VAR_DECL - || !DECL_EXTERNAL (from_decl) + || (!DECL_EXTERNAL (from_decl) + && (vnode = varpool_get_node (from_decl)) != NULL + && vnode->definition) || (flag_ltrans && symtab_get_node (from_decl)->in_other_partition)) return true;
next prev parent reply other threads:[~2014-04-20 7:23 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-04-20 5:34 [Bug tree-optimization/60899] New: " xinliangli at gmail dot com 2014-04-20 6:26 ` [Bug tree-optimization/60899] " hubicka at ucw dot cz 2014-04-20 6:26 ` hubicka at gcc dot gnu.org 2014-04-20 6:52 ` xinliangli at gmail dot com 2014-04-20 7:10 ` xinliangli at gmail dot com 2014-04-20 7:23 ` hubicka at gcc dot gnu.org [this message] 2014-04-20 15:20 ` ppluzhnikov at google dot com 2014-04-21 3:33 ` xinliangli at gmail dot com 2014-04-21 3:48 ` hubicka at ucw dot cz 2014-04-22 8:51 ` rguenth at gcc dot gnu.org 2014-05-21 6:16 ` hubicka at gcc dot gnu.org 2014-06-27 13:36 ` trippels 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-60899-4-JZEKgVEPNU@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).