public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Bader, Lucas" <lucas.bader@sap.com>
To: Jeff Law <jeffreyalaw@gmail.com>, David Malcolm <dmalcolm@redhat.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: Ping^3 [PATCH] get source line for diagnostic from preprocessed file / PR preprocessor/79106
Date: Tue, 28 Jan 2025 19:52:48 +0000	[thread overview]
Message-ID: <CBF80DCF-EAA5-4AF9-83DA-8B2F2555A22D@sap.com> (raw)
In-Reply-To: <43ad8c36-7d56-4bfc-b24c-bcd1e4f44cbb@gmail.com>


Thanks for having a look Jeff. Would be great to hear your thoughts on this patch David.

Best
Lucas

> On 18. Jan 2025, at 17:41, Jeff Law <jeffreyalaw@gmail.com> wrote:
>
> 
>
>> On 1/3/25 7:27 AM, Bader, Lucas wrote:
>> Hello and Happy New Year,
>> as https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79106 is still open, I wanted to again bump this patch I provided a while back.
>> It was earmarked for gcc-11 in https://gcc.gnu.org/pipermail/gcc-patches/2020-January/539201.html but did not make it into the release.
>> Original submission: https://gcc.gnu.org/legacy-ml/gcc-patches/2019-12/msg01113.html
>> Please let me know if something is missing.
> Martin S. is no longer active in GCC development and stuff like input locations tends to fall more towards David M's space.
>
> David M probably needs to chime in here (on cc).
>
> Jeff

      reply	other threads:[~2025-01-28 19:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02  8:27 [PING] " Bader, Lucas
2024-01-22  9:02 ` Bader, Lucas
2025-01-03 14:27   ` Ping^3 " Bader, Lucas
2025-01-18 16:41     ` Jeff Law
2025-01-28 19:52       ` Bader, Lucas [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=CBF80DCF-EAA5-4AF9-83DA-8B2F2555A22D@sap.com \
    --to=lucas.bader@sap.com \
    --cc=dmalcolm@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).