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++/113788] Deducing this is broken with structured binding Date: Tue, 06 Feb 2024 21:35:24 +0000 [thread overview] Message-ID: <bug-113788-4-TSFMZo5BJ4@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113788-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113788 --- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>: https://gcc.gnu.org/g:40485378ade83102d7aa30c317f5d6c90c1d232b commit r14-8832-g40485378ade83102d7aa30c317f5d6c90c1d232b Author: Jakub Jelinek <jakub@redhat.com> Date: Tue Feb 6 22:34:55 2024 +0100 c++: Disallow this specifier except for parameter declarations [PR113788] The deducing this patchset added parsing of this specifier to cp_parser_decl_specifier_seq unconditionally, but in the C++ grammar this[opt] only appears in the parameter-declaration non-terminal, so rather than checking in all the callers of cp_parser_decl_specifier_seq except for cp_parser_parameter_declaration that this specifier didn't appear I think it is far easier and closer to what the standard says to only parse this specifier when called from cp_parser_parameter_declaration. 2024-02-06 Jakub Jelinek <jakub@redhat.com> PR c++/113788 * parser.cc (CP_PARSER_FLAGS_PARAMETER): New enumerator. (cp_parser_decl_specifier_seq): Parse RID_THIS only if CP_PARSER_FLAGS_PARAMETER is set in flags. (cp_parser_parameter_declaration): Or in CP_PARSER_FLAGS_PARAMETER when calling cp_parser_decl_specifier_seq. * g++.dg/parse/pr113788.C: New test.
next prev parent reply other threads:[~2024-02-06 21:35 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-06 16:43 [Bug c++/113788] New: " hewillk at gmail dot com 2024-02-06 17:13 ` [Bug c++/113788] " mpolacek at gcc dot gnu.org 2024-02-06 17:15 ` jakub at gcc dot gnu.org 2024-02-06 17:31 ` mpolacek at gcc dot gnu.org 2024-02-06 17:34 ` jakub at gcc dot gnu.org 2024-02-06 17:48 ` jakub at gcc dot gnu.org 2024-02-06 21:35 ` cvs-commit at gcc dot gnu.org [this message] 2024-02-06 21:35 ` jakub at gcc dot gnu.org 2024-02-07 9:46 ` redi 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-113788-4-TSFMZo5BJ4@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).