From: Alexander Monakov <amonakov@ispras.ru>
To: musl@lists.openwall.com
Subject: Re: [PATCH] force LTO to be disabled when compiling dlstart.lo
Date: Tue, 28 Apr 2015 21:41:14 +0300 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.11.1504282131510.22867@monopod.intra.ispras.ru> (raw)
In-Reply-To: <20150428134317.GL17573@brightrain.aerifal.cx>
> This seems to be a common problem then. I helped someone on #gcc with
> almost the exact same issue doing freestanding work making a
> kernel/bare-metal app using LTO a week or so ago. I'm not sure the
> linker plugin can solve the problem since it seems to happen for
> symbol references *within* a single translation unit (or a combined .o
> file produced by ld -r, as in the case of the person on #gcc) which
> the linker plugin probably does not track.
I think I see the root cause now. The reference to _dlstart_c is from a GCC
asm statement (toplevel in this case), not from a separate assembly file. The
toplevel asm is part of LTO "bytecode", so when linker symbol resolution runs,
it did not yet have a chance to see the reference from the asm, and GCC is
oblivious to the fact (it would need to parse the asm to notice).
If the person on #gcc with ld -r was using gcc asm statements as well, that
would explain their problem too.
So moving the assembly into its own .s file should avoid the issue; adding
__attribute__((used)) to _dlstart_c fixes it too; but even then ...
> Even if the problem is missing linker plugin though, I think we want
> to avoid LTO on these files. It's likely to be very risky since the
> code is running in a situation where no function calls, global data
> accesses, or symbolic references are possible. Here we really are
> asking the compiler to produce asm for us, rather than asking it to
> produce an optimized way to get an abstract job done.
acknowledged. Your call :)
Thanks.
Alexander
next prev parent reply other threads:[~2015-04-28 18:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 6:12 Andre McCurdy
2015-04-28 8:35 ` Alexander Monakov
2015-04-28 8:45 ` Alexander Monakov
2015-04-28 13:43 ` Rich Felker
2015-04-28 14:48 ` Khem Raj
2015-04-28 18:41 ` Alexander Monakov [this message]
2015-04-28 18:50 ` Alexander Monakov
2015-04-28 18:58 ` Rich Felker
2015-04-28 19:23 ` Alexander Monakov
2015-04-29 3:22 ` Rich Felker
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=alpine.LNX.2.11.1504282131510.22867@monopod.intra.ispras.ru \
--to=amonakov@ispras.ru \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).