From: Jeff Law <law@redhat.com>
To: Segher Boessenkool <segher@kernel.crashing.org>,
Paul E Murphy <murphyp@linux.ibm.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: LTO Optimization with asm renames of intrinsic functions
Date: Thu, 13 Aug 2020 22:24:32 -0600 [thread overview]
Message-ID: <931d1d8d94642824d2b6e71439265b21fffcb5ef.camel@redhat.com> (raw)
In-Reply-To: <20200813230727.GL6753@gate.crashing.org>
On Thu, 2020-08-13 at 18:07 -0500, Segher Boessenkool wrote:
> On Wed, Aug 12, 2020 at 05:26:35PM -0500, Paul E Murphy via Gcc-help wrote:
> > asm ("__bid_floatsidd = __GI___bid_floatsidd");
> > This creative workaround has worked with lto disabled, but
> > when enabled, it is effectively ignored. Is there a more robust way
> > to bypass plt calls for intrinsic functions when using LTO?
>
> Do linker scripts work with LTO? You can do this in a linker script
> (which is neater than doing it in assembler, anyway :-) )
I wouldn't think that anything with symbol manipulation would work since LTO
wouldn't know about anything the linker script did.
jeff
prev parent reply other threads:[~2020-08-14 4:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-12 22:26 Paul E Murphy
2020-08-13 3:17 ` Jeff Law
2020-08-13 23:07 ` Segher Boessenkool
2020-08-14 4:24 ` Jeff Law [this message]
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=931d1d8d94642824d2b6e71439265b21fffcb5ef.camel@redhat.com \
--to=law@redhat.com \
--cc=gcc-help@gcc.gnu.org \
--cc=murphyp@linux.ibm.com \
--cc=segher@kernel.crashing.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).