From: Lewis Hyatt <lhyatt@gmail.com>
To: gcc-patches@gcc.gnu.org
Cc: David Malcolm <dmalcolm@redhat.com>, Lewis Hyatt <lhyatt@gmail.com>
Subject: [PATCH v2 0/4] diagnostics: libcpp: Overhaul locations for _Pragma tokens
Date: Thu, 5 Jan 2023 17:36:04 -0500 [thread overview]
Message-ID: <cover.1672867272.git.lhyatt@gmail.com> (raw)
Hello-
This series contains the four remaining patches in the series originally
sent here:
https://gcc.gnu.org/pipermail/gcc-patches/2022-November/605029.html
which implements improved locations for tokens lexed from a string inside a
_Pragma directive.
v2 1/4: diagnostics: libcpp: Add LC_GEN linemaps to support in-memory buffers
This was formerly v1 4/6. It has been rewritten in line with that review,
most recently discussed here:
https://gcc.gnu.org/pipermail/gcc-patches/2022-November/606616.html
v2 2/4: diagnostics: Handle generated data locations in edit_context
This was formerly v1 5a/6. It has been approved already conditional on
v2 1/4 as a prerequisite.
v2 3/4: diagnostics: libcpp: Assign real locations to the tokens inside
_Pragma strings
This was formerly v1 6/6 and is unchanged from that one. It has not been
reviewed yet.
v2 4/4: diagnostics: Support generated data locations in SARIF output
This was formerly v1 5c/6. It has not been fully reviewed yet.
Thanks for taking a look!
-Lewis
next reply other threads:[~2023-01-05 22:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 22:36 Lewis Hyatt [this message]
2023-01-05 22:36 ` [PATCH v2 1/4] diagnostics: libcpp: Add LC_GEN linemaps to support in-memory buffers Lewis Hyatt
2023-01-05 22:36 ` [PATCH v2 2/4] diagnostics: Handle generated data locations in edit_context Lewis Hyatt
2023-01-05 22:36 ` [PATCH v2 3/4] diagnostics: libcpp: Assign real locations to the tokens inside _Pragma strings Lewis Hyatt
2023-01-05 22:36 ` [PATCH v2 4/4] diagnostics: Support generated data locations in SARIF output Lewis Hyatt
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=cover.1672867272.git.lhyatt@gmail.com \
--to=lhyatt@gmail.com \
--cc=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.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).