public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/39751] [9/10/11/12 Regression] ICE in cp_lexer_new_from_tokens, at cp/parser.c:342
Date: Thu, 10 Mar 2022 07:33:21 +0000 [thread overview]
Message-ID: <bug-39751-4-0zguwWEklx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-39751-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39751
--- Comment #15 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Roger Sayle <sayle@gcc.gnu.org>:
https://gcc.gnu.org/g:2185c9734ad977b88c519a4579187a91b3f71edd
commit r12-7573-g2185c9734ad977b88c519a4579187a91b3f71edd
Author: Roger Sayle <roger@nextmovesoftware.com>
Date: Thu Mar 10 07:32:06 2022 +0000
PR c++/39751: ICE-on-invalid parsing regression.
This is a fix for PR c++/39751 which is an ICE-on-invalid regression in
the C++ parser after encountering the end of file. The one line change
is to check that the tokens cached in DECL_PENDING_INLINE_INFO haven't
been purged before processing them in cp_parser_late_parsing_for_member.
2022-03-10 Roger Sayle <roger@nextmovesoftware.com>
gcc/cp/ChangeLog
PR c++/39751
* parser.cc (cp_parser_late_parsing_for_member): Confirm the token
stream hasn't been purged before processing DECL_PENDING_INLINE.
gcc/testsuite/ChangeLog
PR c++/39751
* g++.dg/parse/pr39751.C: New test case.
next prev parent reply other threads:[~2022-03-10 7:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-39751-4@http.gcc.gnu.org/bugzilla/>
2010-12-09 0:14 ` [Bug c++/39751] " gcc at abeckmann dot de
2011-03-21 14:46 ` zsojka at seznam dot cz
2011-09-25 16:16 ` paolo.carlini at oracle dot com
2021-12-29 0:24 ` pinskia at gcc dot gnu.org
2021-12-29 0:24 ` pinskia at gcc dot gnu.org
2021-12-29 0:25 ` [Bug c++/39751] [9/10/11/12 Regression] " pinskia at gcc dot gnu.org
2022-01-21 13:56 ` rguenth at gcc dot gnu.org
2022-02-27 0:01 ` roger at nextmovesoftware dot com
2022-03-10 7:33 ` cvs-commit at gcc dot gnu.org [this message]
2022-03-10 22:44 ` roger at nextmovesoftware dot com
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=bug-39751-4-0zguwWEklx@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).