public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103236] [9/10/11/12 Regression] ICE: in tsubst_pack_expansion, at cp/pt.c:13162 Date: Sun, 14 Nov 2021 21:25:01 +0000 [thread overview] Message-ID: <bug-103236-4-vr89Mfsw6l@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103236-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103236 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Target Milestone|--- |9.5 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Known to fail| |8.1.0 Summary|ICE: in |[9/10/11/12 Regression] |tsubst_pack_expansion, at |ICE: in |cp/pt.c:13162 |tsubst_pack_expansion, at | |cp/pt.c:13162 Known to work| |7.1.0, 7.4.0 Last reconfirmed| |2021-11-14 --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- GCC 7.4.0 and before did: <source>: In lambda function: <source>:5:35: error: parameter packs not expanded with '...': [](auto) { }([](auto... x) { x; }); ^ <source>:5:35: note: 'x' <source>: In function 'void foo(const Ts& ...)': <source>:6:4: error: operand of fold expression has no unexpanded parameter packs ([] { ~~~~ [](auto) { }([](auto... x) { x; }); ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ }(), ...); ~^~
next prev parent reply other threads:[~2021-11-14 21:25 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-14 16:17 [Bug c++/103236] New: " hewillk at gmail dot com 2021-11-14 16:22 ` [Bug c++/103236] " hewillk at gmail dot com 2021-11-14 21:25 ` pinskia at gcc dot gnu.org [this message] 2021-11-15 9:10 ` [Bug c++/103236] [9/10/11/12 Regression] " rguenth at gcc dot gnu.org 2022-04-28 19:32 ` [Bug c++/103236] [9/10/11/12/13 " mpolacek 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-103236-4-vr89Mfsw6l@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).