From: Khem Raj <raj.khem@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Khem Raj via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] Propagate -ffile-prefix-map from CFLAGS to ASFLAGS.
Date: Sat, 1 May 2021 06:26:49 -0700 [thread overview]
Message-ID: <CAMKF1soF8M+N85CMUNB-y9hUSifT4qJf9h8OwMVXkvtf=XAq2Q@mail.gmail.com> (raw)
In-Reply-To: <87r1iq3oe8.fsf@oldenburg.str.redhat.com>
On Sat, May 1, 2021 at 12:26 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * Khem Raj via Libc-alpha:
>
> > On Fri, Apr 30, 2021 at 11:28 AM Khem Raj <raj.khem@gmail.com> wrote:
> >>
> >> -ffile-prefix-map could be used as superset to imply -fdebug-prefix-map
> >> as well, therefore it should be propagated too, so cases when
> >> -ffile-prefix-map is used but -fdebug-prefix-map is not, then it should
> >> still rewire the paths in debug info
> >
> > hmm noticed that when I remove -fdebug-prefix-map then
> > -ffile-prefix-map did not work and its because GCC is not
> > translating -ffile-prefix-map to equivalent assembler option
> > --debug-prefix-map like it does for -fdebug-prefix-map
> > it seems a bug in GCC driver.
>
> I haven't look at the patch in detail. Does the above mean you withdraw
> it?
I think it wont be effective unless gcc bug is fixed. So it can be applied or
we can wait for gcc to be fixed.
>
> Thanks,
> Florian
>
next prev parent reply other threads:[~2021-05-01 13:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 18:28 Khem Raj
2021-04-30 19:08 ` Khem Raj
2021-04-30 19:22 ` Khem Raj
2021-05-01 7:26 ` Florian Weimer
2021-05-01 13:26 ` Khem Raj [this message]
2021-05-01 13:38 ` Florian Weimer
2021-05-01 17:50 ` Khem Raj
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='CAMKF1soF8M+N85CMUNB-y9hUSifT4qJf9h8OwMVXkvtf=XAq2Q@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=fweimer@redhat.com \
--cc=libc-alpha@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).