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++/97938] [9/10 Regression] g++ crash when inferring type of auto parameter pack in lambda capture Date: Fri, 21 May 2021 14:51:00 +0000 [thread overview] Message-ID: <bug-97938-4-OCkp6GP0he@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97938-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97938 --- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-9 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:7168fb621b4442936d2a9429389a65f15043e5e4 commit r9-9549-g7168fb621b4442936d2a9429389a65f15043e5e4 Author: Jason Merrill <jason@redhat.com> Date: Fri Apr 2 11:05:46 2021 -0400 c++: lambda pack init-capture within generic lambda We represent the type of a pack init-capture as auto... with packs from the initializer stuck into PACK_EXPANSION_PARAMETER_PACKS so that expanding it produces the right number of elements. But when partially instantiating the auto..., we were changing PACK_EXPANSION_PARAMETER_PACKS to refer to only the auto itself. Fixed thus. gcc/cp/ChangeLog: PR c++/97938 * cp-tree.h (PACK_EXPANSION_AUTO_P): New. * lambda.c (add_capture): Set it. * pt.c (tsubst_pack_expansion): Handle it. gcc/testsuite/ChangeLog: PR c++/97938 * g++.dg/cpp2a/lambda-pack-init6.C: New test.
next prev parent reply other threads:[~2021-05-21 14:51 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-22 20:25 [Bug c++/97938] New: " elel at 3wh dot net 2020-11-23 2:22 ` [Bug c++/97938] " mpolacek at gcc dot gnu.org 2020-11-23 2:23 ` [Bug c++/97938] 9/10/11 Regression] " mpolacek at gcc dot gnu.org 2020-11-23 7:36 ` [Bug c++/97938] [9/10/11 " rguenth at gcc dot gnu.org 2021-04-01 22:39 ` jason at gcc dot gnu.org 2021-04-01 22:52 ` jason at gcc dot gnu.org 2021-04-02 16:47 ` cvs-commit at gcc dot gnu.org 2021-04-02 17:03 ` [Bug c++/97938] [9/10 " jason at gcc dot gnu.org 2021-05-20 21:34 ` cvs-commit at gcc dot gnu.org 2021-05-21 14:51 ` cvs-commit at gcc dot gnu.org [this message] 2021-05-21 15:19 ` jason at gcc dot gnu.org 2021-05-24 8:33 ` cvs-commit at gcc dot gnu.org 2022-05-12 12:47 ` 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-97938-4-OCkp6GP0he@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).