From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Richard Biener <rguenther@suse.de>, Jakub Jelinek <jakub@redhat.com>
Cc: Jeff Law <jeffreyalaw@gmail.com>, gcc-patches@gcc.gnu.org
Subject: Re: Patch ping - [PATCH] file-prefix-map: Fix up -f*-prefix-map= [PR108464]
Date: Fri, 10 Mar 2023 10:14:27 +0000 [thread overview]
Message-ID: <6f81d7ed79c19eb490986a39d62b9e84222e4c59.camel@linuxfoundation.org> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2303100904200.18795@jbgna.fhfr.qr>
On Fri, 2023-03-10 at 09:05 +0000, Richard Biener wrote:
> On Fri, 10 Mar 2023, Jakub Jelinek wrote:
>
> > Hi!
> >
> > I'd like to ping these patches. All 3 variants have been
> > bootstrapped/regtested on x86_64-linux and i686-linux, the last
> > one is my preference I guess. The current state breaks e.g. ccache.
> >
> > https://gcc.gnu.org/pipermail/gcc-patches/2023-January/610285.html
> > - PR108464 - P1 - file-prefix-map: Fix up -f*-prefix-map= (3 variants)
>
> Let's go with your preference - I was hoping on comments from Richard
> Purdie as of his preference but then ..
> >
Sorry, I hadn't realised you were waiting on me :(.
I'd commented on the bug and thought that covered things. We should be
fine with the third option, sorry about the issue and thanks for
resolving it!
Cheers,
Richard
next prev parent reply other threads:[~2023-03-10 10:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 12:15 [PATCH 1/2] gcc/file-prefix-map: Allow remapping of relative paths Richard Purdie
2022-08-17 12:15 ` [PATCH 2/2] libcpp: Avoid remapping filenames within directives Richard Purdie
2022-08-17 14:19 ` Richard Purdie
2022-11-01 19:32 ` Jeff Law
2022-11-02 10:52 ` Richard Purdie
2022-11-01 19:46 ` [PATCH 1/2] gcc/file-prefix-map: Allow remapping of relative paths Jeff Law
2023-01-19 13:06 ` Jakub Jelinek
2023-01-20 15:05 ` [PATCH] file-prefix-map: Fix up -f*-prefix-map= [PR108464] Jakub Jelinek
2023-01-23 15:39 ` Jakub Jelinek
2023-03-10 8:49 ` Patch ping - " Jakub Jelinek
2023-03-10 9:05 ` Richard Biener
2023-03-10 10:14 ` Richard Purdie [this message]
2022-11-04 9:12 ` [PATCH 1/2] gcc/file-prefix-map: Allow remapping of relative paths Eric Botcazou
2022-11-04 17:21 ` Richard Purdie
2022-11-07 8:01 ` Eric Botcazou
2022-11-07 16:21 ` Jeff Law
2022-11-07 16:36 ` Eric Botcazou
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=6f81d7ed79c19eb490986a39d62b9e84222e4c59.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=rguenther@suse.de \
/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).