public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98112] Add -fdirect-access-external-data & drop HAVE_LD_PIE_COPYRELOC
Date: Mon, 28 Dec 2020 07:34:46 +0000 [thread overview]
Message-ID: <bug-98112-4-55fmXFHqgZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98112-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98112
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |segher at gcc dot gnu.org
--- Comment #4 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Fangrui Song from comment #3)
> Are you happy with the option name -f[no-]direct-access-external-data ?
Not at all, no :-(
The name does not explain its purpose at all, and the whole concept only
makes sense for a fraction of all targets. A -mcopy-relocs ("generate copy
relocations if that is a good idea"), defined *per target*, would be a lot
better, or a -mpic-use-copy-relocs (since you say it is *not* just for pie),
or something like that. You want to have this a generic option, while it is
not clear at all what it would mean, what it would *do*, which is especially
important if you want this to be an option used by multiple compilers: if it
is not clear to every user what simple, sensible thing a flag is the knob
for, that flag simply cannot be used at all -- or worse, some users *will*
use it, but then their intentions are not clear to humans, and different
compilers can (and will!) think the user wanted something else!
next prev parent reply other threads:[~2020-12-28 7:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-03 1:26 [Bug c/98112] New: " i at maskray dot me
2020-12-03 12:16 ` [Bug target/98112] " hjl.tools at gmail dot com
2020-12-03 17:51 ` i at maskray dot me
2020-12-15 0:25 ` i at maskray dot me
2020-12-28 7:34 ` segher at gcc dot gnu.org [this message]
2020-12-28 8:36 ` i at maskray dot me
2020-12-28 9:54 ` segher at gcc dot gnu.org
2020-12-28 17:43 ` i at maskray dot me
2023-01-02 19:54 ` [Bug target/98112] Add -f[no-]direct-access-external-data " foom at fuhm dot net
2023-01-04 18:50 ` thiago at kde dot org
2023-01-04 18:54 ` pinskia at gcc dot gnu.org
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-98112-4-55fmXFHqgZ@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).