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++/100482] namespaces as int in decltype expression Date: Tue, 08 Aug 2023 20:03:48 +0000 [thread overview] Message-ID: <bug-100482-4-qFRN0Wdbo9@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100482-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100482 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:a90bd3ea6d1ba27b15476f0a768d7952c6723420 commit r14-3087-ga90bd3ea6d1ba27b15476f0a768d7952c6723420 Author: Nathaniel Shead <nathanieloshead@gmail.com> Date: Tue Aug 8 12:48:43 2023 +1000 c++: Report invalid id-expression in decltype [PR100482] This patch ensures that any errors raised by finish_id_expression when parsing a decltype expression are properly reported, rather than potentially going ignored and causing invalid code to be accepted. We can also now remove the separate check for templates without args as this is also checked for in finish_id_expression. PR c++/100482 gcc/cp/ChangeLog: * parser.cc (cp_parser_decltype_expr): Report errors raised by finish_id_expression. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/decltype-100482.C: New test. Signed-off-by: Nathaniel Shead <nathanieloshead@gmail.com>
next prev parent reply other threads:[~2023-08-08 20:03 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-08 2:45 [Bug c++/100482] New: " hahayes12 at tutanota dot com 2021-05-08 3:31 ` [Bug c++/100482] " sand at rifkin dot dev 2021-05-08 8:00 ` redi at gcc dot gnu.org 2021-05-10 8:04 ` rguenth at gcc dot gnu.org 2023-08-08 20:03 ` cvs-commit at gcc dot gnu.org [this message] 2024-04-05 6:48 ` nshead 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-100482-4-qFRN0Wdbo9@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).