public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
	Florian Weimer <fweimer@redhat.com>,
	Siddhesh Poyarekar <siddhesh@sourceware.org>,
	GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] New option --enable-pie-programs
Date: Thu, 18 Nov 2021 22:06:51 +0530	[thread overview]
Message-ID: <549f87ce-d3c1-c4ff-8aae-bc899668c730@gotplt.org> (raw)
In-Reply-To: <CAMe9rOqj0tkG99jfDNELyHBXzQbve2CWDRO2OpHmSpZn5A13XQ@mail.gmail.com>

On 11/18/21 19:11, H.J. Lu wrote:
>> HJ, could you describe how you'd expect it to behave?  Would it map to
>> any of the options I describe above?
> 
> --enable-default-pie builds all dynamic programs, including tests, as PIE.   If
> compiler/target supports static PIE, it also builds static programs as PIE.

OK I guess there's close to consensus on a single flag that enables 
dynamic PIE and if supported by the target, transparently enable 
static-pie as well.  So next question: is it OK to enable by default and 
require users to specify --enable-pie=no to disable PIE?

Also, would you be OK with calling it --enable-pie HJ?  Or do you feel 
strongly about calling it --enable-default-pie?  Same question for 
Adhemerval; I am OK with calling it --enable-cake fwiw ;)

Thanks,
Siddhesh

  reply	other threads:[~2021-11-18 16:37 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-16 13:52 Siddhesh Poyarekar
2021-11-16 13:58 ` Florian Weimer
2021-11-16 15:17   ` Siddhesh Poyarekar
2021-11-17  8:39     ` Florian Weimer
2021-11-17  8:50       ` Siddhesh Poyarekar
2021-11-17  9:10         ` Florian Weimer
2021-11-17 10:04           ` Siddhesh Poyarekar
2021-11-18  9:24             ` Siddhesh Poyarekar
2021-11-18 12:42               ` H.J. Lu
2021-11-18 12:49                 ` Adhemerval Zanella
2021-11-18 13:26                   ` Siddhesh Poyarekar
2021-11-18 13:41                     ` H.J. Lu
2021-11-18 16:36                       ` Siddhesh Poyarekar [this message]
2021-11-18 16:44                         ` H.J. Lu
2021-11-18 16:49                           ` Siddhesh Poyarekar
2021-11-18 16:56                             ` H.J. Lu
2021-11-18 17:54                               ` Siddhesh Poyarekar
2021-11-18 17:58                                 ` H.J. Lu
2021-11-18 18:09                                   ` Siddhesh Poyarekar
2021-11-18 18:18                                     ` H.J. Lu
2021-11-22 23:40                                       ` Fangrui Song
2021-11-24  1:04                                         ` Fāng-ruì Sòng
2021-11-24  1:27                                           ` Siddhesh Poyarekar

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=549f87ce-d3c1-c4ff-8aae-bc899668c730@gotplt.org \
    --to=siddhesh@gotplt.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=fweimer@redhat.com \
    --cc=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).