From: Marek Polacek <polacek@redhat.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH v3] configure: Implement --enable-host-pie
Date: Mon, 28 Mar 2022 08:26:43 -0400 [thread overview]
Message-ID: <YkGpg1hRS6pXgDz+@redhat.com> (raw)
In-Reply-To: <orlewv5br7.fsf@lxoliva.fsfla.org>
Hi,
On Sun, Mar 27, 2022 at 06:25:16PM -0300, Alexandre Oliva via Gcc-patches wrote:
> Hello, Marek,
>
> The patch looks good to me, and I'd have no trouble approving it if we
> were in stage1. Since we aren't, I'd prefer if we waited for another
> build system maintainer to give it a look, if it's to go in gcc-12. If
> release managers feel I'm being overcautious, I don't mind if they
> overrule my request.
Thanks a lot for having a look! I'll wait till GCC 13; I don't think
it's very important to have the feature in GCC 12.
Marek
next prev parent reply other threads:[~2022-03-28 12:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-10 16:48 [PATCH] " Marek Polacek
2022-02-10 21:10 ` Joseph Myers
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 [this message]
2023-05-09 19:41 [PATCH] " Marek Polacek
2023-05-16 15:29 ` Marek Polacek
2023-05-16 20:11 ` Iain Sandoe
2023-05-18 23:32 ` [PATCH v2] " Marek Polacek
2023-05-19 8:01 ` Iain Sandoe
2023-05-19 18:56 ` [PATCH v3] " Marek Polacek
2023-06-05 16:18 ` Marek Polacek
2023-06-06 3:06 ` Jeff Law
2023-06-15 20:58 ` Marek Polacek
2023-06-16 10:26 ` Martin Jambor
2023-06-16 12:32 ` Marek Polacek
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=YkGpg1hRS6pXgDz+@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=oliva@adacore.com \
--cc=pbonzini@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).