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++/97358] [8/9/10/11 Regression] ICE while building firefox since r8-2720
Date: Wed, 14 Oct 2020 19:44:35 +0000 [thread overview]
Message-ID: <bug-97358-4-OQL6ZVAq7d@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97358-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97358
--- Comment #12 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>:
https://gcc.gnu.org/g:270c5a982ccb4ef83bd9ad37d39cf47461acb55a
commit r11-3893-g270c5a982ccb4ef83bd9ad37d39cf47461acb55a
Author: Jason Merrill <jason@redhat.com>
Date: Wed Oct 14 14:55:04 2020 -0400
c++: Diagnose bogus variadic lambda. [PR97358]
If the lambda has a capture pack, it cannot be used unexpanded within the
body of the lambda. If you want to expand the pack across multiple
lambdas,
don't capture the whole pack.
gcc/cp/ChangeLog:
PR c++/97358
* pt.c (check_for_bare_parameter_packs): Diagnose use of
capture pack.
gcc/testsuite/ChangeLog:
PR c++/97358
* g++.dg/cpp0x/lambda/lambda-variadic11.C: New test.
next prev parent reply other threads:[~2020-10-14 19:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 19:11 [Bug c++/97358] New: " jakub at gcc dot gnu.org
2020-10-09 19:11 ` [Bug c++/97358] " jakub at gcc dot gnu.org
2020-10-09 19:32 ` jakub at gcc dot gnu.org
2020-10-12 6:23 ` rguenth at gcc dot gnu.org
2020-10-12 9:42 ` jakub at gcc dot gnu.org
2020-10-12 10:29 ` jakub at gcc dot gnu.org
2020-10-14 15:23 ` jakub at gcc dot gnu.org
2020-10-14 15:34 ` sumbera at volny dot cz
2020-10-14 15:41 ` jakub at gcc dot gnu.org
2020-10-14 18:17 ` ppalka at gcc dot gnu.org
2020-10-14 18:19 ` ppalka at gcc dot gnu.org
2020-10-14 18:27 ` jakub at gcc dot gnu.org
2020-10-14 18:44 ` jason at gcc dot gnu.org
2020-10-14 18:48 ` jason at gcc dot gnu.org
2020-10-14 19:24 ` jakub at gcc dot gnu.org
2020-10-14 19:44 ` cvs-commit at gcc dot gnu.org [this message]
2020-10-14 19:47 ` [Bug c++/97358] [8/9/10 " jason at gcc dot gnu.org
2020-10-14 20:15 ` jakub at gcc dot gnu.org
2020-10-15 7:16 ` dan at danny dot cz
2020-10-15 7:42 ` jakub at gcc dot gnu.org
2020-10-15 8:24 ` sumbera at volny dot cz
2020-10-15 8:42 ` dan at danny dot cz
2020-10-16 0:32 ` richard-gccbugzilla at metafoo dot co.uk
2021-05-14 9:53 ` [Bug c++/97358] [9/10 " jakub at gcc dot gnu.org
2021-06-01 8:18 ` rguenth at gcc dot gnu.org
2022-05-27 9:43 ` [Bug c++/97358] [10 " rguenth at gcc dot gnu.org
2022-06-28 10:42 ` jakub at gcc dot gnu.org
2023-07-07 9:07 ` rguenth 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-97358-4-OQL6ZVAq7d@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: link
Be 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).