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++/94546] [10 Regression] unimplemented: unexpected AST of kind nontype_argument_pack Date: Sat, 27 Feb 2021 20:43:05 +0000 [thread overview] Message-ID: <bug-94546-4-Td944PPlQe@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94546-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94546 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:f98a3c8a58b3cb39d4073e8a5b2671a5d68b8ce4 commit r10-9393-gf98a3c8a58b3cb39d4073e8a5b2671a5d68b8ce4 Author: Jason Merrill <jason@redhat.com> Date: Thu Feb 11 19:45:22 2021 -0500 c++: variadic lambda template and empty pack [PR97246] In get<0>, Is is empty, so the first parameter pack of the lambda is empty, but after the fix for PR94546 we were wrongly associating it with the partial instantiation of 'v'. gcc/cp/ChangeLog: PR c++/97246 PR c++/94546 * pt.c (extract_fnparm_pack): Check DECL_PACK_P here. (register_parameter_specializations): Not here. gcc/testsuite/ChangeLog: PR c++/97246 * g++.dg/cpp2a/lambda-generic-variadic21.C: New test.
prev parent reply other threads:[~2021-02-27 20:43 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-10 7:20 [Bug c++/94546] New: " bisqwit at iki dot fi 2020-04-10 13:32 ` [Bug c++/94546] " mpolacek at gcc dot gnu.org 2020-04-10 13:50 ` [Bug c++/94546] [10 Regression] " mpolacek at gcc dot gnu.org 2020-04-10 21:31 ` jason at gcc dot gnu.org 2020-04-20 13:46 ` rguenth at gcc dot gnu.org 2020-04-22 6:28 ` cvs-commit at gcc dot gnu.org 2020-04-22 6:28 ` jason at gcc dot gnu.org 2021-02-12 2:47 ` cvs-commit at gcc dot gnu.org 2021-02-27 20:43 ` cvs-commit at gcc dot gnu.org [this message]
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-94546-4-Td944PPlQe@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).