From: "H.J. Lu" <hjl.tools@gmail.com>
To: Siddhesh Poyarekar <siddhesh@sourceware.org>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [COMMITTED] Replace --enable-static-pie with --disable-default-pie
Date: Mon, 13 Dec 2021 05:22:05 -0800 [thread overview]
Message-ID: <CAMe9rOq5-rMnMWRjX1sxRVpx1GEDsL3nT8LWU14fZFtLHjkQtA@mail.gmail.com> (raw)
In-Reply-To: <20211213030233.2286715-1-siddhesh@sourceware.org>
On Sun, Dec 12, 2021 at 7:03 PM Siddhesh Poyarekar via Libc-alpha
<libc-alpha@sourceware.org> wrote:
>
> Build glibc programs and tests as PIE by default and enable static-pie
> automatically if the architecture and toolchain supports it.
>
> Also add a new configuration option --disable-default-pie to prevent
> building programs as PIE.
>
> Only the following architectures now have PIE disabled by default
> because they do not work at the moment. hppa, ia64, alpha and csky
> don't work because the linker is unable to handle a pcrel relocation
Please reference linker bugs here.
> generated from PIE objects. The microblaze compiler is currently
> failing with an ICE. GNU hurd tries to enable static-pie, which does
> not work and hence fails. All these targets have default PIE disabled
> at the moment and I have left it to the target maintainers to enable PIE
> on their targets.
>
> build-many-glibcs runs clean for all targets. I also tested x86_64 on
> Fedora and Ubuntu, to verify that the default build as well as
> --disable-default-pie work as expected with both system toolchains.
>
> Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
> Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
--
H.J.
next prev parent reply other threads:[~2021-12-13 13:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 8:26 [PATCH] " Siddhesh Poyarekar
2021-12-07 16:06 ` Florian Weimer
2021-12-07 16:21 ` Siddhesh Poyarekar
2021-12-07 16:30 ` Florian Weimer
2021-12-07 18:52 ` Joseph Myers
2021-12-07 20:13 ` Adhemerval Zanella
2021-12-08 4:34 ` Siddhesh Poyarekar
2021-12-08 6:39 ` [PATCH v2] " Siddhesh Poyarekar
2021-12-10 17:35 ` Siddhesh Poyarekar
2021-12-10 19:28 ` Adhemerval Zanella
2021-12-13 3:02 ` [COMMITTED] " Siddhesh Poyarekar
2021-12-13 13:22 ` H.J. Lu [this message]
2021-12-13 13:41 ` Siddhesh Poyarekar
2021-12-13 13:43 ` H.J. Lu
2021-12-13 14:28 ` Siddhesh Poyarekar
2021-12-13 15:29 ` Siddhesh Poyarekar
2021-12-16 19:26 ` Florian Weimer
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=CAMe9rOq5-rMnMWRjX1sxRVpx1GEDsL3nT8LWU14fZFtLHjkQtA@mail.gmail.com \
--to=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@sourceware.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).