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++/96623] [11 Regression] ICE in inject_parm_decls, at cp/parser.c:23893 Date: Fri, 22 Jan 2021 22:55:28 +0000 [thread overview] Message-ID: <bug-96623-4-QvqUGHPCdc@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-96623-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96623 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>: https://gcc.gnu.org/g:89100826acec92dfaa6ab8f2646b8053e7dbc67c commit r11-6874-g89100826acec92dfaa6ab8f2646b8053e7dbc67c Author: Marek Polacek <polacek@redhat.com> Date: Thu Jan 21 16:12:28 2021 -0500 c++: ICE with noexcept in class in member function [PR96623] I discovered very strange code in inject_parm_decls: if (args && is_this_parameter (args)) { gcc_checking_assert (current_class_ptr == NULL_TREE); current_class_ptr = NULL_TREE; We are tripping up on the assert because when we call inject_parm_decls, current_class_ptr is set to 'A'. It was set by inject_this_parameter after we've parsed the parameter-declaration-clause of the member function foo. It seems correct to set ccp/ccr to A::B when we're late parsing the noexcept-specifiers of bar* functions in B, so that this-> does the right thing. Since inject_parm_decls doesn't expect to see non-null ccp/ccr, reset it before calling inject_parm_decls. gcc/cp/ChangeLog: PR c++/96623 * parser.c (inject_parm_decls): Remove a redundant assignment. (cp_parser_class_specifier_1): Clear current_class_{ptr,ref} before calling inject_parm_decls. gcc/testsuite/ChangeLog: PR c++/96623 * g++.dg/cpp0x/noexcept64.C: New test.
next prev parent reply other threads:[~2021-01-22 22:55 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-15 2:38 [Bug c++/96623] New: [10/11 " haoxintu at gmail dot com 2020-08-18 14:29 ` [Bug c++/96623] [11 " mpolacek at gcc dot gnu.org 2020-08-18 14:31 ` mpolacek at gcc dot gnu.org 2020-10-12 12:33 ` rguenth at gcc dot gnu.org 2021-01-15 21:37 ` mpolacek at gcc dot gnu.org 2021-01-21 19:30 ` mpolacek at gcc dot gnu.org 2021-01-22 22:55 ` cvs-commit at gcc dot gnu.org [this message] 2021-01-22 22:55 ` mpolacek at gcc dot gnu.org
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-96623-4-QvqUGHPCdc@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: linkBe 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).