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++/92909] [8/9/10 Regression] ICE on incorrect lambda inside variadic template
Date: Sun, 15 Mar 2020 22:09:30 +0000 [thread overview]
Message-ID: <bug-92909-4-Lo1VetPvV4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-92909-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92909
--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-8 branch has been updated by Jason Merrill
<jason@gcc.gnu.org>:
https://gcc.gnu.org/g:eee8f2161e072c1b9da4f334f882c385a27baa1f
commit r8-10128-geee8f2161e072c1b9da4f334f882c385a27baa1f
Author: Jason Merrill <jason@redhat.com>
Date: Sat Mar 14 17:10:39 2020 -0400
c++: Find parameter pack in typedef in lambda [92909].
find_parameter_packs_r doesn't look through typedefs, which is normally
correct, but that means we need to handle their declarations specially.
gcc/cp/ChangeLog
2020-03-14 Jason Merrill <jason@redhat.com>
PR c++/92909
* pt.c (find_parameter_packs_r): [DECL_EXPR]: Walk
DECL_ORIGINAL_TYPE of a typedef.
next prev parent reply other threads:[~2020-03-15 22:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-92909-4@http.gcc.gnu.org/bugzilla/>
2020-03-13 20:31 ` jason at gcc dot gnu.org
2020-03-14 21:13 ` cvs-commit at gcc dot gnu.org
2020-03-15 22:09 ` cvs-commit at gcc dot gnu.org
2020-03-15 22:09 ` cvs-commit at gcc dot gnu.org [this message]
2020-03-15 22:10 ` jason at gcc dot gnu.org
2020-03-16 15:07 ` jakub at gcc dot gnu.org
2021-10-18 18:40 ` ppalka 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-92909-4-Lo1VetPvV4@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).