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/57703] Assembler function definition moved to a different ltrans then call
Date: Wed, 19 Mar 2014 11:03:00 -0000	[thread overview]
Message-ID: <bug-57703-4-emSza7qfsV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57703-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
This is just totally broken and not supportable with LTO.  We'd need to amend
toplevel asm syntax to list defined and used symbols, but that doesn't fix
existing uses.

The proper fix is to excempt these files from LTO or move those assembler
functions to separate TUs (preferably assembler TUs...).

Honza also had the idea of trying to parse the assembler string for
"obvious" symbol definitions / uses.


  parent reply	other threads:[~2014-03-19 11:03 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24 20:49 [Bug lto/57703] New: " marxin.liska at gmail dot com
2013-06-25  8:00 ` [Bug lto/57703] " rguenth at gcc dot gnu.org
2013-06-26 12:45 ` marxin.liska at gmail dot com
2014-03-18 16:05 ` marxin.liska at gmail dot com
2014-03-19 11:03 ` rguenth at gcc dot gnu.org [this message]
2014-03-25 10:39 ` jamborm at gcc dot gnu.org
2014-09-06 10:21 ` trippels at gcc dot gnu.org
2014-09-06 10:29 ` trippels at gcc dot gnu.org
2014-12-28  8:52 ` trippels at gcc dot gnu.org
2014-12-28 10:17 ` amonakov at gcc dot gnu.org
2020-09-21  0:03 ` egallager at gcc dot gnu.org
2020-09-21  7:12 ` marxin at gcc dot gnu.org
2022-01-01 22:58 ` 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-57703-4-emSza7qfsV@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).