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 target/94504] On powerpc, -ffunction-sections -fdata-sections is not as effective as expected for PIE executables.
Date: Tue, 07 Apr 2020 06:47:55 +0000 [thread overview]
Message-ID: <bug-94504-4-uW1lGguZhF@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94504-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94504
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
gc-sections with a GOT is probably difficult since I'm quite sure we don't have
an extra section for every datum in the GOT. Likely applies to the PLT as
well.
Of course relying on --gc-sections to "fix" your link because you are missing
definitions is more than fragile...
next prev parent reply other threads:[~2020-04-07 6:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-06 18:08 [Bug target/94504] New: " gcc-bugzilla at mkarcher dot dialup.fu-berlin.de
2020-04-07 6:47 ` rguenth at gcc dot gnu.org [this message]
2020-04-07 7:04 ` [Bug target/94504] " rguenth at gcc dot gnu.org
2020-04-07 15:09 ` gcc-bugzilla at mkarcher dot dialup.fu-berlin.de
2020-04-07 17:14 ` rguenther at suse dot de
2020-04-07 21:28 ` [Bug target/94504] On powerpc, -ffunction-sections -fdata-sections is not as effective as expected for non-PIE executables gcc-bugzilla at mkarcher dot dialup.fu-berlin.de
2020-04-13 3:49 ` [Bug target/94504] On powerpc, -ffunction-sections -fdata-sections is not as effective as expected for PIE and PIC amodra at gmail dot com
2020-04-13 6:53 ` glaubitz at physik dot fu-berlin.de
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-94504-4-uW1lGguZhF@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).