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++/83476] [9 Regression] Template argument deduction fails with reference template parameter Date: Wed, 11 May 2022 14:59:48 +0000 [thread overview] Message-ID: <bug-83476-4-yYaJvSJxIq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-83476-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83476 --- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:c6432e17960799509c48df6b500a8d069110980b commit r9-10154-gc6432e17960799509c48df6b500a8d069110980b Author: Patrick Palka <ppalka@redhat.com> Date: Wed Apr 14 08:54:30 2021 -0400 c++: Fix deduction with reference NTTP [PR83476] In the testcase ref11.C below, during deduction for the call f(a), uses_deducible_template_parms returns false for the dependent specialization A<V> because the generic template argument V here is wrapped in an implicit INDIRECT_REF (formed from template_parm_to_arg). Since uses_deducible_template_parms returns false, unify_one_argument exits early without ever attempting to deduce 'n' for 'V'. This patch fixes this by making deducible_expression look through such implicit INDIRECT_REFs. gcc/cp/ChangeLog: PR c++/83476 PR c++/99885 * pt.c (deducible_expression): Look through implicit INDIRECT_REFs as well. gcc/testsuite/ChangeLog: PR c++/83476 PR c++/99885 * g++.dg/cpp1z/class-deduction85.C: New test. * g++.dg/template/ref11.C: New test. (cherry picked from commit 2ccc05a5141506fde0e20dec702c717fd67bf6ee)
next prev parent reply other threads:[~2022-05-11 14:59 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-83476-4@http.gcc.gnu.org/bugzilla/> 2021-04-13 20:04 ` [Bug c++/83476] [8/9/10/11 " ppalka at gcc dot gnu.org 2021-04-13 20:04 ` ppalka at gcc dot gnu.org 2021-04-14 12:55 ` cvs-commit at gcc dot gnu.org 2021-04-14 15:51 ` [Bug c++/83476] [8/9/10 " ppalka at gcc dot gnu.org 2021-04-20 16:09 ` cvs-commit at gcc dot gnu.org 2021-04-30 7:43 ` [Bug c++/83476] [8/9 " rguenth at gcc dot gnu.org 2021-05-14 9:49 ` [Bug c++/83476] [9 " jakub at gcc dot gnu.org 2021-06-01 8:09 ` rguenth at gcc dot gnu.org 2021-12-08 19:03 ` pinskia at gcc dot gnu.org 2022-05-11 14:59 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-11 15:01 ` ppalka 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-83476-4-yYaJvSJxIq@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).