public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at ucw dot cz" <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: Wed, 02 Mar 2011 16:34:00 -0000	[thread overview]
Message-ID: <bug-43038-4-zWCnKIEQR2@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 #14 from Jan Hubicka <hubicka at ucw dot cz> 2011-03-02 16:34:22 UTC ---
Ah, the reason for writting reply was primarily the observation that enforcing
partitioning based on origin of asm statement won't fly with crossmoudle
inlining, so I think it is quite useless complication of the whole thing.

Also the not mangling unless we hit conflict probably should be implemented
in a way that when conflict exists all static of same name are renamed, so
asm statements won't compile rather that end up referring random other
variable.

Honza


  parent reply	other threads:[~2011-03-02 16:34 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
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 [this message]
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-zWCnKIEQR2@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).