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/46820] Undefined reference errors with LTO
Date: Sat, 11 Dec 2010 15:04:00 -0000	[thread overview]
Message-ID: <bug-46820-4-fjxyNbEujj@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-46820-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Jan Hubicka <hubicka at ucw dot cz> 2010-12-11 15:03:44 UTC ---
Note that while working on mozilla, I noticed that SUN's compiler extends the
toplevel asm syntax by allowing parameters (and the usual %n references to
them).  It probably makes sense to adopt this syntax in future.  Until then
Iguess we will need to explain users that toplevel asm statements basically
exists outside of LTO unit and thus everything used by them needs to be marked
as externally visible.

Honza


  parent reply	other threads:[~2010-12-11 15:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 13:16 [Bug lto/46820] New: " d.g.gorbachev at gmail dot com
2010-12-06 13:17 ` [Bug lto/46820] " d.g.gorbachev at gmail dot com
2010-12-06 13:18 ` d.g.gorbachev at gmail dot com
2010-12-06 13:18 ` d.g.gorbachev at gmail dot com
2010-12-06 13:43 ` rguenth at gcc dot gnu.org
2010-12-06 17:41 ` d.g.gorbachev at gmail dot com
2010-12-07 11:50 ` rguenth at gcc dot gnu.org
2010-12-11 13:31 ` hubicka at ucw dot cz
2010-12-11 15:04 ` hubicka at ucw dot cz [this message]
2010-12-13 22:02 ` d.g.gorbachev at gmail dot com
2010-12-14 10:27 ` hubicka at gcc dot gnu.org
2010-12-14 10:46 ` hubicka at gcc dot gnu.org
2010-12-15  0:15 ` d.g.gorbachev at gmail dot com
2012-05-11 22:34 ` [Bug lto/46820] toplevel ASM statements should be allowed to reffer local symbols in LTO hubicka at gcc dot gnu.org
2012-05-11 23:02 ` hubicka at gcc dot gnu.org
2022-01-01 22:58 ` [Bug lto/46820] toplevel ASM statements being moved away from the functions in the TU pinskia at gcc dot gnu.org
2023-10-24 21:32 ` pinskia 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-46820-4-fjxyNbEujj@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).