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/43038] DECL_PRESERVE_P or attribute((used)) static globals not completely preserved with -flto
Date: Tue, 01 Mar 2011 16:42:00 -0000 [thread overview]
Message-ID: <bug-43038-4-pUrna8HRVS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43038-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=43038
--- Comment #10 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-03-01 16:42:26 UTC ---
(In reply to comment #9)
> On Tue, 1 Mar 2011, d.g.gorbachev at gmail dot com wrote:
>
> > > The problem is that statics need to be mangled, so they persist
> > > as i.1234 instead. Really refering to a local symbol in asm is
> > > going to be difficult with LTO (any global or other static symbol
> > > with name i will cause a non-resolvable conflict).
> >
> > One solution is to introduce a new attribute, say "nomangle", and shift
> > responsibility for possible conflicts on a user.
>
> The original LTO proposal included assembler changes to allow multiple
> local symbols with the same name in the output. You could resurrect that,
> though allowing references to the multiple local symbols from asm imposes
> extra requirements on what the assembler interface must look like
> (directives to say which versions are being referred to by asms in a
> particular part of the input?).
I think we settled on the idea to delay mangling of local symbols until after
we composed ltrans units (so we can also compose units in a way to avoid
the need to mangle local symbols with a used attribute). It shouldn't be
too difficult to implement but sofar nobody has done the work (and it
will likely be easier with a global symbol table which we hopefully will
get for 4.7).
next prev parent reply other threads:[~2011-03-01 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43038-4@http.gcc.gnu.org/bugzilla/>
2011-03-01 10:21 ` rguenth at gcc dot gnu.org
2011-03-01 12:46 ` d.g.gorbachev at gmail dot com
2011-03-01 16:39 ` joseph at codesourcery dot com
2011-03-01 16:42 ` rguenth at gcc dot gnu.org [this message]
2011-03-01 17:42 ` hubicka at ucw dot cz
2011-03-02 10:16 ` rguenth at gcc dot gnu.org
2011-03-02 16:32 ` hubicka at ucw dot cz
2011-03-02 16:34 ` hubicka at ucw dot cz
2011-03-02 16:39 ` rguenth at gcc dot gnu.org
2011-03-02 16:42 ` rguenth at gcc dot gnu.org
2011-03-02 16:57 ` hubicka at ucw dot cz
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-43038-4-pUrna8HRVS@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).