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++/106893] [12 Regression] auto deduces wrong type for function pointer Date: Mon, 12 Sep 2022 20:30:00 +0000 [thread overview] Message-ID: <bug-106893-4-u0IX83KurC@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106893-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106893 --- Comment #4 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:999638cb7b126d33d1ea6548c69ba387b7d7a270 commit r12-8758-g999638cb7b126d33d1ea6548c69ba387b7d7a270 Author: Jason Merrill <jason@redhat.com> Date: Mon Sep 12 13:47:34 2022 -0400 c++: auto member function and auto variable [PR106893] As with PR105623, we need to call mark_single_function sooner to resolve the type of a BASELINK. PR c++/106893 PR c++/90451 gcc/cp/ChangeLog: * decl.cc (cp_finish_decl): Call mark_single_function. gcc/testsuite/ChangeLog: * g++.dg/cpp1y/auto-fn65.C: New test.
next prev parent reply other threads:[~2022-09-12 20:30 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-08 21:53 [Bug c++/106893] New: " dan at stahlke dot org 2022-09-08 22:07 ` [Bug c++/106893] [12/13 Regression] " pinskia at gcc dot gnu.org 2022-09-09 10:36 ` redi at gcc dot gnu.org 2022-09-12 17:28 ` jason at gcc dot gnu.org 2022-09-12 19:47 ` cvs-commit at gcc dot gnu.org 2022-09-12 20:30 ` cvs-commit at gcc dot gnu.org [this message] 2023-04-21 20:13 ` [Bug c++/106893] [12 " jason 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-106893-4-u0IX83KurC@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).