public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <richard.guenther@gmail.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] configure: Avoid unnecessary constraints on executables for $build.
Date: Fri, 29 Oct 2021 09:25:18 +0200	[thread overview]
Message-ID: <CAFiYyc2NfZRRGGR5LOdT6MacXG0LLkpeXibXTCdUhjniKnTa3Q@mail.gmail.com> (raw)
In-Reply-To: <EB85EEF2-EBC8-404D-9EBD-DAE37AF5AA0A@sandoe.co.uk>

On Thu, Oct 28, 2021 at 5:44 PM Iain Sandoe <iain@sandoe.co.uk> wrote:
>
> Hi Richard,
>
> > On 8 Sep 2021, at 07:35, Richard Biener <richard.guenther@gmail.com> wrote:
> >
> > On Tue, Sep 7, 2021 at 10:11 PM Iain Sandoe <iain@sandoe.co.uk> wrote:
> >>
>
> >> So, looking through the various email threads and the PR, I think that
> >> what has happened is :
> >>
> >> As the PR points out, our existing PCH model does not work if the compiler
> >> executable is PIE - which manifests on platforms like Darwin (which is PIE
> >> by default) or Linux when configured —enable-default-pie.
> >>
> >> H.J’s original patch forces no-PIE onto the compiler executables, and
> >> because of shared code on $host also to the driver etc.
>
> >> OK for master, and eventually backports?
> >
> > OK for trunk, I think it warrants quite some soaking time before considering
> > backports.
>
> It’s been on master for quite some time now (and presumably several cycles of
> everyone’s CI) without any reports of problems,  it would be good to get this at
> least onto 11 and 10 (since that is the last version we can bootstrap with c++98).
>
> OK for backports now?

OK.

> thanks
> Iain
>

      reply	other threads:[~2021-10-29  7:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-07 20:11 Iain Sandoe
2021-09-08  6:35 ` Richard Biener
2021-10-28 15:44   ` Iain Sandoe
2021-10-29  7:25     ` Richard Biener [this message]

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=CAFiYyc2NfZRRGGR5LOdT6MacXG0LLkpeXibXTCdUhjniKnTa3Q@mail.gmail.com \
    --to=richard.guenther@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=iain@sandoe.co.uk \
    /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).