public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "xinliangli at gmail dot com" <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:10:00 -0000	[thread overview]
Message-ID: <bug-60899-4-d1CsdBegow@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 #4 from davidxl <xinliangli at gmail dot com> ---
(In reply to davidxl from comment #3)
> (In reply to Jan Hubicka from comment #2)
> > David,
> > it seems a_m.C should be different form a.C.  From chain of events you
> > describe I think
> > we need to figure out why the last folding happens.  Does the function pass 
> > can_refer_decl_in_current_unit_p and if so, how does cgraph node look at
> > that time?
> > 
> > Honza
> 
> Cut & paste error:
> 
> // a_m.cc
> 
> #include "a.h"
> struct D2: public DI {
>   virtual int doit () { return 3; }
> };
> 
> extern int bar(DI*);
> int main()
> {
>   D2 d2;
>   return bar(&d2);
> }


stepping into can_refer_decl_in_current_unit_p indicates it returns true (for
A::foo and A::vtable) at the condition @line 106.


  parent reply	other threads:[~2014-04-20  7:10 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 gcc dot gnu.org
2014-04-20  6:26 ` hubicka at ucw dot cz
2014-04-20  6:52 ` xinliangli at gmail dot com
2014-04-20  7:10 ` xinliangli at gmail dot com [this message]
2014-04-20  7:23 ` hubicka at gcc dot gnu.org
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-d1CsdBegow@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: link
Be 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).