From: Jakub Jelinek <jakub@redhat.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Andrew Pinski <pinskia@gmail.com>,
Fangrui Song <maskray@google.com>, Fangrui Song <i@maskray.me>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Jan Hubicka <hubicka@ucw.cz>
Subject: Re: [PATCH] Add --enable-default-semantic-interposition to GCC configure
Date: Mon, 7 Jun 2021 20:13:21 +0200 [thread overview]
Message-ID: <20210607181321.GL7746@tucnak> (raw)
In-Reply-To: <cf2de059-765a-a1fc-7d28-00a102793bf7@gmail.com>
On Mon, Jun 07, 2021 at 12:01:55PM -0600, Jeff Law via Gcc-patches wrote:
> > This breaks assumptions across the board. If software packages want
> > to use -fno-semantic-interposition that is one thing. But distros
> > should not be changing the default. This is just like using
> > -ffast-math :).
> Some distros already force immediate binding at link time for security
> purposes on a distro-wide basis which, IIUC, does the same thing, but
> without the benefits from a code generation standpoint.
If you are talking about -Wl,-z,now, that is very different, semantic
interposition then still works just fine.
If you are talking about the glibc style by hand "protected" visibility,
bind calls to symbols defined in the same library through internal symbols,
then that is done only for a couple of packages and is stronger than
-fno-semantic-interposition.
Jakub
next prev parent reply other threads:[~2021-06-07 18:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-06 23:12 Fangrui Song
2021-06-06 23:18 ` Andrew Pinski
2021-06-06 23:36 ` Fangrui Song
2021-06-07 18:01 ` Jeff Law
2021-06-07 18:13 ` Jakub Jelinek [this message]
2021-06-07 19:01 ` Fangrui Song
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=20210607181321.GL7746@tucnak \
--to=jakub@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hubicka@ucw.cz \
--cc=i@maskray.me \
--cc=jeffreyalaw@gmail.com \
--cc=maskray@google.com \
--cc=pinskia@gmail.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).