public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <jeffreyalaw@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] preprocessor: Fix tracking of system header state [PR60014, PR60723]
Date: Wed, 12 Oct 2022 11:09:27 -0600	[thread overview]
Message-ID: <a889f578-8294-4d45-6f6b-0b48a00e65a0@gmail.com> (raw)
In-Reply-To: <5dce970b21e788deaa3d08f21995d8cb3cdb3752.1665263871.git.lhyatt@gmail.com>


On 10/8/22 15:18, Lewis Hyatt via Gcc-patches wrote:
> The token_streamer class (which implements gcc mode -E and
> -save-temps/-no-integrated-cpp) needs to keep track whether the last tokens
> output were in a system header, so that it can generate line marker
> annotations as necessary for a downstream consumer to reconstruct the
> state. The logic for tracking it, which was added by r5-1863 to resolve
> PR60723, has some edge case issues as revealed by the three new test
> cases. The first, coming from the original PR60014, was incidentally fixed by
> r9-1926 for unrelated reasons. The other two were still failing on master
> prior to this commit. Such code paths were not realizable prior to r13-1544,
> which made it possible for the token streamer to see CPP_PRAGMA tokens in more
> contexts.
>
> The two main issues being corrected here are:
>
> 1) print.prev_was_system_token needs to indicate whether the previous token
> output was in a system location. However, it was not being set on every token,
> only on those that triggered the main code path; specifically it was not
> triggered on a CPP_PRAGMA token. Testcase 2 covers this case.
>
> 2) The token_streamer uses a variable "line_marker_emitted" to remember
> whether a line marker has been emitted while processing a given token, so that
> it wouldn't be done more than once in case multiple conditions requiring a
> line marker are true. There was no reason for this to be a member variable
> that retains its value from token to token, since it is just needed for
> tracking the state locally while processing a single given token. The fact
> that it could retain its value for a subsequent token is rather difficult to
> observe, but testcase 3 demonstrates incorrect behavior resulting from
> that. Moving this to a local variable also simplifies understanding the
> control flow going forward.
>
> gcc/c-family/ChangeLog:
>
> 	PR preprocessor/60014
> 	PR preprocessor/60723
> 	* c-ppoutput.cc (class token_streamer): Remove member
> 	line_marker_emitted to...
> 	(token_streamer::stream): ...a local variable here. Set
> 	print.prev_was_system_token on all code paths.
>
> gcc/testsuite/ChangeLog:
>
> 	PR preprocessor/60014
> 	PR preprocessor/60723
> 	* gcc.dg/cpp/pr60014-1.c: New test.
> 	* gcc.dg/cpp/pr60014-1.h: New test.
> 	* gcc.dg/cpp/pr60014-2.c: New test.
> 	* gcc.dg/cpp/pr60014-2.h: New test.
> 	* gcc.dg/cpp/pr60014-3.c: New test.
> 	* gcc.dg/cpp/pr60014-3.h: New test.

OK

jeff



      reply	other threads:[~2022-10-12 17:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 21:18 [PATCH] preprocessor: Fix tracking of system header state [PR60014,PR60723] Lewis Hyatt
2022-10-12 17:09 ` Jeff Law [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=a889f578-8294-4d45-6f6b-0b48a00e65a0@gmail.com \
    --to=jeffreyalaw@gmail.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).