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++/105734] [12/13 Regression]: Incorrect "error: invalid use of 'auto'" for explicit destructor inside a template Date: Wed, 01 Jun 2022 19:53:38 +0000 [thread overview] Message-ID: <bug-105734-4-fZMGbauvWq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105734-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105734 --- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:b090938e61260ce841a0d51de3407881a38e3c52 commit r12-8447-gb090938e61260ce841a0d51de3407881a38e3c52 Author: Jason Merrill <jason@redhat.com> Date: Tue May 31 16:31:35 2022 -0400 c++: auto and dependent member name [PR105734] In r12-3643 I improved our handling of type names after . or -> when unqualified lookup doesn't find anything, but it needs to handle auto specially. PR c++/105734 gcc/cp/ChangeLog: * parser.cc (cp_parser_postfix_dot_deref_expression): Use typeof if the expression has auto type. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/auto57.C: New test.
next prev parent reply other threads:[~2022-06-01 19:53 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-26 4:30 [Bug c++/105734] New: Regression: Incorrect "error: invalid use of 'auto'" llvm at rifkin dot dev 2022-05-26 4:46 ` [Bug c++/105734] " llvm at rifkin dot dev 2022-05-26 5:03 ` pinskia at gcc dot gnu.org 2022-05-26 5:03 ` pinskia at gcc dot gnu.org 2022-05-26 5:05 ` [Bug c++/105734] [12/13 Regression]: Incorrect "error: invalid use of 'auto'" for explicit destructor inside a template pinskia at gcc dot gnu.org 2022-05-26 5:07 ` pinskia at gcc dot gnu.org 2022-05-26 5:09 ` pinskia at gcc dot gnu.org 2022-05-26 7:42 ` redi at gcc dot gnu.org 2022-05-26 7:59 ` redi at gcc dot gnu.org 2022-05-26 15:34 ` llvm at rifkin dot dev 2022-05-27 2:32 ` llvm at rifkin dot dev 2022-05-27 6:27 ` rguenth at gcc dot gnu.org 2022-05-31 20:25 ` jason at gcc dot gnu.org 2022-06-01 19:21 ` cvs-commit at gcc dot gnu.org 2022-06-01 19:53 ` cvs-commit at gcc dot gnu.org [this message] 2022-06-01 19:54 ` jason at gcc dot gnu.org 2022-06-01 23:13 ` llvm at rifkin dot dev
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-105734-4-fZMGbauvWq@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).