public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/100937] configure: Add --enable-default-semantic-interposition
Date: Wed, 03 Nov 2021 12:25:28 +0000	[thread overview]
Message-ID: <bug-100937-4-yqcj7b9KLP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100937-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100937

--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to frankhb1989 from comment #7)
> GCC and the GNU toolchain are not ELF-specific. Nor are they responsible to
> the authority of the specification.

That seems like nonsense to me. The toolchain might not be ELF-specific, but on
targets that *do* use ELF, of course the ELF specification is relevant, and
deviating from it should not be done lightly.

>  The "ELF assumptions" have no natural
> position to be the default at the very first glance from the users' view.

More nonsense.

Just because portability between ELF and PE/COFF is difficult and requires
care, doesn't mean we should also make it difficult to guarantee portability
across different linux distros that are all using ELF. That's just silly. You
don't make anything better by making everything equally bad.

  parent reply	other threads:[~2021-11-03 12:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-06 23:10 [Bug driver/100937] New: " i at maskray dot me
2021-06-06 23:12 ` [Bug driver/100937] " pinskia at gcc dot gnu.org
2021-06-06 23:15 ` i at maskray dot me
2021-06-06 23:19 ` pinskia at gcc dot gnu.org
2021-06-06 23:27 ` pinskia at gcc dot gnu.org
2021-06-07  8:28 ` jakub at gcc dot gnu.org
2021-06-10  5:02 ` i at maskray dot me
2021-11-02 18:16 ` frankhb1989 at gmail dot com
2021-11-03  3:19 ` egallager at gcc dot gnu.org
2021-11-03 12:25 ` redi at gcc dot gnu.org [this message]
2021-11-22 13:26 ` frankhb1989 at gmail dot com
2021-11-22 19:52 ` i at maskray dot me
2021-11-22 22:54   ` Jan Hubicka
2021-11-22 22:54 ` hubicka at kam dot mff.cuni.cz

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-100937-4-yqcj7b9KLP@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).