public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rafael.espindola at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/53808] Undefined symbol when building a library with lto
Date: Wed, 04 Sep 2013 12:26:00 -0000	[thread overview]
Message-ID: <bug-53808-4-mSwPZlQ82N@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53808-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53808

--- Comment #4 from Rafael Avila de Espindola <rafael.espindola at gmail dot com> ---
The equivalent clang bug (llvm.org/pr13124) just got fixed by avoiding the
devirtualization in this case.

Not sure how similar the issues are internally, but I summarized what I found
in clang in:

http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20130902/087810.html


  parent reply	other threads:[~2013-09-04 12:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-29 18:20 [Bug lto/53808] New: " rafael.espindola at gmail dot com
2012-07-03 13:18 ` [Bug lto/53808] " hubicka at gcc dot gnu.org
2012-11-06 13:53 ` rafael.espindola at gmail dot com
2013-03-23  0:36 ` jason at gcc dot gnu.org
2013-03-23 21:40 ` hubicka at ucw dot cz
2013-09-04 12:26 ` rafael.espindola at gmail dot com [this message]
2014-02-25 17:47 ` jason at gcc dot gnu.org
2014-02-25 17:57 ` jason at gcc dot gnu.org
2014-02-25 18:55 ` jason at gcc dot gnu.org
2014-02-25 19:00 ` jason at gcc dot gnu.org
2014-02-26 21:33 ` jason at gcc dot gnu.org
2014-06-30 20:21 ` jason at gcc dot gnu.org
2014-07-22 14:03 ` rafael.espindola at gmail dot com
2014-07-30 17:28 ` jason at gcc dot gnu.org
2014-07-30 21:30 ` jason at gcc dot gnu.org
2014-08-19 17:30 ` jason at gcc dot gnu.org
2014-09-10 14:28 ` jason 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-53808-4-mSwPZlQ82N@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).