From: Lewis Hyatt <lhyatt@gmail.com>
To: Marek Polacek <polacek@redhat.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] preprocessor: Reinitialize frontend parser after loading a PCH [PR112319]
Date: Thu, 30 Nov 2023 17:20:26 -0500 [thread overview]
Message-ID: <CAA_5UQ6KbQnsxt5moDBVusP61X+QP24V6JfBVLWiuia+PJ4a0A@mail.gmail.com> (raw)
In-Reply-To: <ZWj8cykegns1n0+k@redhat.com>
On Thu, Nov 30, 2023 at 4:19 PM Marek Polacek <polacek@redhat.com> wrote:
>
> On Wed, Nov 01, 2023 at 05:54:57PM -0400, Lewis Hyatt wrote:
> > Hello-
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112319
> >
> > This is a one-line patch to fix the GCC 14 regression noted in the
> > PR. Bootstrap + regtest all languages on x86-64 looks good. Is it OK please?
> > Thanks!
> >
> > -Lewis
> >
> > -- >8 --
> >
> > Since r14-2893, the frontend parser object needs to exist when running in
> > preprocess-only mode, because pragma_lex() is now called in that mode and
> > needs to make use of it. This is handled by calling c_init_preprocess() at
> > startup. If -fpch-preprocess is in effect (commonly, because of
> > -save-temps), a PCH file may be loaded during preprocessing, in which
> > case the parser will be destroyed, causing the issue noted in the
> > PR. Resolve it by reinitializing the frontend parser after loading the PCH.
> >
> > gcc/c-family/ChangeLog:
> >
> > PR pch/112319
> > * c-ppoutput.cc (cb_read_pch): Reinitialize the frontend parser
>
> "front-end"
>
> > after loading a PCH.
> >
> > gcc/testsuite/ChangeLog:
> >
> > PR pch/112319
> > * g++.dg/pch/pr112319.C: New test.
> > * g++.dg/pch/pr112319.Hs: New test.
> > * gcc.dg/pch/pr112319.c: New test.
> > * gcc.dg/pch/pr112319.hs: New test.
> > ---
> > gcc/c-family/c-ppoutput.cc | 5 +++++
> > gcc/testsuite/g++.dg/pch/pr112319.C | 5 +++++
> > gcc/testsuite/g++.dg/pch/pr112319.Hs | 1 +
> > gcc/testsuite/gcc.dg/pch/pr112319.c | 5 +++++
> > gcc/testsuite/gcc.dg/pch/pr112319.hs | 1 +
> > 5 files changed, 17 insertions(+)
> > create mode 100644 gcc/testsuite/g++.dg/pch/pr112319.C
> > create mode 100644 gcc/testsuite/g++.dg/pch/pr112319.Hs
> > create mode 100644 gcc/testsuite/gcc.dg/pch/pr112319.c
> > create mode 100644 gcc/testsuite/gcc.dg/pch/pr112319.hs
> >
> > diff --git a/gcc/c-family/c-ppoutput.cc b/gcc/c-family/c-ppoutput.cc
> > index 4aa2bef2c0f..4f973767976 100644
> > --- a/gcc/c-family/c-ppoutput.cc
> > +++ b/gcc/c-family/c-ppoutput.cc
> > @@ -862,4 +862,9 @@ cb_read_pch (cpp_reader *pfile, const char *name,
> >
> > fprintf (print.outf, "#pragma GCC pch_preprocess \"%s\"\n", name);
> > print.src_line++;
> > +
> > + /* The process of reading the PCH has destroyed the frontend parser,
>
> "front-end"
>
> > + so ask the frontend to reinitialize it, in case we need it to
>
> "front end"
>
> (sorry to be overly pedantic...)
>
> Patch looks fine to me; please go ahead if you haven't pushed it already.
>
Thanks for the review! I did push it a few days ago as Jakub approved
it... I will spell front end correctly next time :).
-Lewis
prev parent reply other threads:[~2023-11-30 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 21:54 Lewis Hyatt
2023-11-17 14:16 ` ping: " Lewis Hyatt
2023-11-24 16:04 ` Jakub Jelinek
2023-11-30 21:19 ` Marek Polacek
2023-11-30 22:20 ` Lewis Hyatt [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=CAA_5UQ6KbQnsxt5moDBVusP61X+QP24V6JfBVLWiuia+PJ4a0A@mail.gmail.com \
--to=lhyatt@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=polacek@redhat.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).