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++/67829] Bogus "ambiguous template instantiation" error with partial specializations involving a template template parameter Date: Thu, 10 Jun 2021 22:33:34 +0000 [thread overview] Message-ID: <bug-67829-4-HhnbYeoIcd@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67829-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67829 --- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Patrick Palka <ppalka@gcc.gnu.org>: https://gcc.gnu.org/g:edec2660ff4890ecf8cc191f7c92cf527de51fe2 commit r12-1374-gedec2660ff4890ecf8cc191f7c92cf527de51fe2 Author: Patrick Palka <ppalka@redhat.com> Date: Thu Jun 10 18:31:21 2021 -0400 c++: matching deduced template template parameters [PR67829] During deduction, when the template of the argument for a bound ttp is a template template parameter, we need to consider the TEMPLATE_TEMPLATE_PARAMETER for matching rather than the TEMPLATE_DECL thereof, because the canonical form of a template template parameter as a template argument is the former tree, not the latter. PR c++/67829 gcc/cp/ChangeLog: * pt.c (unify) <case BOUND_TEMPLATE_TEMPLATE_PARM>: When the TEMPLATE_DECL of a BOUND_TEMPLATE_TEMPLATE_PARM argument is a template template parameter, adjust to the TEMPLATE_TEMPLATE_PARAMETER before falling through. gcc/testsuite/ChangeLog: * g++.dg/template/ttp34.C: New test. * g++.dg/template/ttp34a.C: New test. * g++.dg/template/ttp34b.C: New test.
next prev parent reply other threads:[~2021-06-10 22:33 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-03 4:29 [Bug c++/67829] New: " rs2740 at gmail dot com 2015-10-22 14:45 ` [Bug c++/67829] " paolo.carlini at oracle dot com 2021-06-06 16:48 ` ppalka at gcc dot gnu.org 2021-06-10 22:33 ` cvs-commit at gcc dot gnu.org [this message] 2021-06-10 22:35 ` ppalka at gcc dot gnu.org 2021-12-09 17:04 ` pinskia 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-67829-4-HhnbYeoIcd@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).