From: Marek Polacek <polacek@redhat.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v3] configure: Implement --enable-host-pie
Date: Thu, 15 Jun 2023 16:58:21 -0400 [thread overview]
Message-ID: <ZIt7bUPBBBNricpT@redhat.com> (raw)
In-Reply-To: <ca5a62f4-155a-d5c4-9ca5-c2e261908ec5@gmail.com>
On Mon, Jun 05, 2023 at 09:06:43PM -0600, Jeff Law wrote:
>
>
> On 6/5/23 10:18, Marek Polacek via Gcc-patches wrote:
> > Ping. Anyone have any further comments?
> Given this was approved before, but got reverted due to issues (which have
> since been addressed) -- I think you might as well go forward and sooner
> rather than later so that we can catch fallout earlier.
Thanks, pushed now, after rebasing, adjusting the patch for
r14-1385, and testing with and without --enable-host-pie on
both Debian and Fedora.
If something comes up and I can't fix it quickly enough, I'll
have to revert the patch. We'll see.
Marek
next prev parent reply other threads:[~2023-06-15 20:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2023-06-16 10:26 ` Martin Jambor
2023-06-16 12:32 ` Marek Polacek
2023-06-16 16:15 ` [PATCH] Regenerate some autotools generated files (Was: Re: [PATCH v3] configure: Implement --enable-host-pie) Martin Jambor
-- strict thread matches above, loose matches on Subject: below --
2022-02-10 16:48 [PATCH] configure: Implement --enable-host-pie 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
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=ZIt7bUPBBBNricpT@redhat.com \
--to=polacek@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.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).