From: Joseph Myers <joseph@codesourcery.com>
To: Marek Polacek <polacek@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Alexandre Oliva <oliva@adacore.com>
Subject: Re: [PATCH] configure: Implement --enable-host-pie
Date: Thu, 10 Feb 2022 21:10:17 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2202102101410.196416@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20220210164805.580636-1-polacek@redhat.com>
Some general observations:
* There are various toplevel GCC subdirectories that are built for the
host (possibly in addition to the target in some cases) but aren't changed
in this patch. Do they get a PIE or PIC build anyway by default? Such
directories include, I think: fixincludes (as a corner case, for the
installed fixincludes), gmp, mpfr, mpc, isl (host libraries whose
configure scripts aren't part of GCC, so any changes to ensure they build
as PIE when needed would need to be at top level), intl, libbacktrace,
libiberty, gnattools, gotools.
(Using a bootstrap compiler that *doesn't* default to PIE might help
detect any such issues, though only for directores that get built for the
host in that build - some may not get built by default.)
For directories that are only used as host libraries but don't install any
executables, even if this patch needs additions the -z now one shouldn't.
* I don't see anything obvious here (or for the existing
--enable-host-shared) that actually causes the configure option to apply
only to the host and not to the target, in the case of subdirectories such
as libbacktrace that get built for both host and target. (Though static
target libraries may well default to PIC in many cases anyway.)
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2022-02-10 21:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 16:48 Marek Polacek
2022-02-10 21:10 ` Joseph Myers [this message]
2022-02-24 20:32 ` [PATCH v2] " Marek Polacek
2022-02-25 0:04 ` Joseph Myers
2022-03-04 23:17 ` [PATCH v3] " Marek Polacek
2022-03-27 21:25 ` Alexandre Oliva
2022-03-28 12:26 ` Marek Polacek
2022-11-11 2:52 [PATCH] " Marek Polacek
2022-11-20 15:06 ` Jeff Law
2022-11-23 2:18 ` Marek Polacek
2023-05-09 19:41 Marek Polacek
2023-05-16 15:29 ` Marek Polacek
2023-05-16 20:11 ` Iain Sandoe
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=alpine.DEB.2.22.394.2202102101410.196416@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=oliva@adacore.com \
--cc=pbonzini@redhat.com \
--cc=polacek@redhat.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).