public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/53282] lto and visibility-inlines-hidden makes "wrongly" hidden symbols and in a way that depends on the order of the input compilation units
Date: Wed, 09 May 2012 10:04:00 -0000 [thread overview]
Message-ID: <bug-53282-4-iVwV4MSRFB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53282-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53282
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2012-05-09
Ever Confirmed|0 |1
--- Comment #7 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-05-09 09:58:09 UTC ---
(In reply to comment #6)
> On 9 May, 2012, at 11:10 AM, rguenth at gcc dot gnu.org wrote:
>
> > All hidden symbols are postfixed with something like .local.77.4195, making
> > them no longer the symbols for the explicitely instantiated functions.
> >
> > I suppose you say that the bug is that you have explicitely instantiated
> > some templates which you want to have appear in the library as exported
> > but LTO makes all instances hidden so that no externally visible symbol
> > for that explicitely instantiated template remains?
>
> correct.
> The additional point is that this happens only for some symbols, not all, even
> if the definitions/declarations are identical.
Ok, so the question would be - why does GCC think this symbol is not
possibly referenced from outside of the LTO unit?
next prev parent reply other threads:[~2012-05-09 9:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 13:51 [Bug lto/53282] New: " vincenzo.innocente at cern dot ch
2012-05-08 13:57 ` [Bug lto/53282] " rguenth at gcc dot gnu.org
2012-05-08 14:02 ` vincenzo.innocente at cern dot ch
2012-05-08 17:11 ` hubicka at gcc dot gnu.org
2012-05-09 7:30 ` vincenzo.innocente at cern dot ch
2012-05-09 9:15 ` rguenth at gcc dot gnu.org
2012-05-09 9:45 ` vincenzo.innocente at cern dot ch
2012-05-09 10:04 ` rguenth at gcc dot gnu.org [this message]
2012-05-09 10:16 ` vincenzo.innocente at cern dot ch
2012-05-09 10:17 ` rguenth at gcc dot gnu.org
2012-05-09 10:46 ` vincenzo.innocente at cern dot ch
2012-05-09 10:50 ` vincenzo.innocente at cern dot ch
2012-05-09 12:32 ` hubicka at ucw dot cz
2012-05-09 12:46 ` vincenzo.innocente at cern dot ch
2012-05-09 13:56 ` rguenth at gcc dot gnu.org
2012-05-09 15:01 ` vincenzo.innocente at cern dot ch
2012-05-10 7:16 ` [Bug lto/53282] [lto w/o linker plugin] " vincenzo.innocente at cern dot ch
2012-05-10 9:56 ` rguenth at gcc dot gnu.org
2012-05-10 10:17 ` vincenzo.innocente at cern dot ch
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-53282-4-iVwV4MSRFB@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).