From: Florian Weimer <fweimer@redhat.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
Cc: Fangrui Song <maskray@google.com>,
"H.J. Lu" <hjl.tools@gmail.com>,
Wilco Dijkstra via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [RESEND PATCH] Makeconfig: Set pie-ccflag to -fPIE by default
Date: Tue, 20 Sep 2022 16:12:44 +0200 [thread overview]
Message-ID: <87a66um8wz.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <AS4PR08MB79012BF67DAA9CB0B72F8928834C9@AS4PR08MB7901.eurprd08.prod.outlook.com> (Wilco Dijkstra's message of "Tue, 20 Sep 2022 13:59:45 +0000")
* Wilco Dijkstra:
> Well if changing the default of fPIC is unacceptable in GCC, adding a
> new option should help LLVM too since it could imply more than
> -fno-semantic-interposition. A key question is whether we could
> require that exported symbols are marked explicitly so that we only
> emit GOT and PLT indirections on such exported symbols.
-flto with a linker plugin already covers this. I don't think we need
anything else. Maybe an LTO mode that only deals with visibility, but
otherwise does little cross-TU optimization?
Thanks,
Florian
next prev parent reply other threads:[~2022-09-20 14:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-26 18:39 Wilco Dijkstra
2022-08-26 19:02 ` H.J. Lu
2022-08-26 19:45 ` Richard Henderson
2022-08-26 20:11 ` H.J. Lu
2022-08-29 11:49 ` Wilco Dijkstra
2022-08-29 13:10 ` Florian Weimer
2022-08-29 15:27 ` Wilco Dijkstra
2022-08-29 15:27 ` Wilco Dijkstra
2022-08-29 19:43 ` H.J. Lu
2022-08-29 19:57 ` Fangrui Song
2022-09-05 8:58 ` Wilco Dijkstra
2022-09-15 21:45 ` Fangrui Song
2022-09-20 13:59 ` Wilco Dijkstra
2022-09-20 14:12 ` Florian Weimer [this message]
2022-09-20 16:00 ` Wilco Dijkstra
2022-09-20 22:02 ` Fangrui Song
-- strict thread matches above, loose matches on Subject: below --
2022-08-25 21:01 Richard Henderson
2022-08-26 12:32 ` Adhemerval Zanella Netto
2022-08-26 17:29 ` Richard Henderson
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=87a66um8wz.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=maskray@google.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.
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).