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++/105623] [12/13 regression][rejects valid] invalid use of auto when deducing return type of base class template Date: Wed, 25 May 2022 15:09:45 +0000 [thread overview] Message-ID: <bug-105623-4-nBcYcOaeiq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105623-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105623 --- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:850a9ce8bcca59c7efabcdeeca14c5bd905e8363 commit r13-768-g850a9ce8bcca59c7efabcdeeca14c5bd905e8363 Author: Jason Merrill <jason@redhat.com> Date: Tue May 24 17:37:58 2022 -0400 c++: deduction from auto fn [PR105623] Since my patch for PR90451, we defer mark_used of single functions as late as possible. And since my r12-1273, we keep BASELINK from lookup around rather than reconstruct it later. These both made us try to instantiate g with a function type that still had 'auto' as its return type. PR c++/105623 gcc/cp/ChangeLog: * decl2.cc (mark_used): Copy type from fn to BASELINK. * pt.cc (unify_one_argument): Call mark_single_function. gcc/testsuite/ChangeLog: * g++.dg/cpp1y/auto-fn62.C: New test.
next prev parent reply other threads:[~2022-05-25 15:09 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-16 21:35 [Bug c++/105623] New: " hello at josephloser dot com 2022-05-16 21:42 ` [Bug c++/105623] " mpolacek at gcc dot gnu.org 2022-05-16 22:05 ` mpolacek at gcc dot gnu.org 2022-05-16 22:23 ` davidfromonline at gmail dot com 2022-05-24 20:10 ` jason at gcc dot gnu.org 2022-05-25 15:09 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-25 17:08 ` jason at gcc dot gnu.org 2022-05-31 19:31 ` cvs-commit at gcc dot gnu.org 2022-05-31 19:32 ` 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-105623-4-nBcYcOaeiq@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).