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/65252] Link time optimization breaks use of filenames in linker scripts
Date: Mon, 02 Mar 2015 08:50:00 -0000 [thread overview]
Message-ID: <bug-65252-4-b8QNVikG7B@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65252-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65252
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |hubicka at gcc dot gnu.org
Resolution|--- |WONTFIX
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
LTO doesn't know about linker scripts and their effects (see other related
bugreports). For your case LTO partitioning might simply tear boot.o and
early.o
apart and put parts in differen LTRANS units.
I don't see any way to fix this but to teach WPA to parse linker scripts and
guide partitioning.
That means basically a WONTFIX with the known workaround to compile boot.o and
early.o without -flto.
Another workaround that might work is to use -flto-partition=1to1 (but the
filenames will still get wrong I think).
prev parent reply other threads:[~2015-03-02 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-65252-4@http.gcc.gnu.org/bugzilla/>
2015-02-28 14:52 ` trippels at gcc dot gnu.org
2015-03-01 7:57 ` goswin-v-b at web dot de
2015-03-02 8:50 ` rguenth at gcc dot gnu.org [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=bug-65252-4-b8QNVikG7B@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).