public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/109241] [12/13/14 Regression] ICE Segmentation fault for statement expression with a local type inside inside a generic lambda inside a generic lambda since r13-6722-gb323f52ccf966800
Date: Mon, 15 May 2023 07:54:17 +0000 [thread overview]
Message-ID: <bug-109241-4-p07I9GKRlx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109241-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109241
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[12/13 Regression] ICE |[12/13/14 Regression] ICE
|Segmentation fault for |Segmentation fault for
|statement expression with a |statement expression with a
|local type inside inside a |local type inside inside a
|generic lambda inside a |generic lambda inside a
|generic lambda since |generic lambda since
|r13-6722-gb323f52ccf966800 |r13-6722-gb323f52ccf966800
CC| |rguenth at gcc dot gnu.org
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Marek Polacek from comment #5)
> In GCC 12 this test still ICEs:
>
> template<class T>
> void foo(T) {
> [](auto){
> [] {
> struct X {};
> };
> };
> }
>
> template void foo(int);
How so? I can't reproduce. Likewise for PR109850. Is trunk actually fixed?
Please update known-to-work.
next prev parent reply other threads:[~2023-05-15 7:54 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 20:47 [Bug c++/109241] New: [13 Regression] ICE Segmentation fault since for ccache package r13-6722-gb323f52ccf966800 marxin at gcc dot gnu.org
2023-03-21 20:47 ` [Bug c++/109241] " marxin at gcc dot gnu.org
2023-03-21 21:01 ` pinskia at gcc dot gnu.org
2023-03-22 19:31 ` [Bug c++/109241] [13 Regression] ICE Segmentation fault for statement expression with a local type inside inside a generic lambda inside a generic lambda since r13-6722-gb323f52ccf966800 jason at gcc dot gnu.org
2023-03-23 3:24 ` cvs-commit at gcc dot gnu.org
2023-03-23 8:08 ` marxin at gcc dot gnu.org
2023-04-26 21:16 ` cvs-commit at gcc dot gnu.org
2023-05-10 20:41 ` mpolacek at gcc dot gnu.org
2023-05-10 20:41 ` mpolacek at gcc dot gnu.org
2023-05-13 22:51 ` [Bug c++/109241] [12/13 " pinskia at gcc dot gnu.org
2023-05-13 22:51 ` pinskia at gcc dot gnu.org
2023-05-15 7:54 ` rguenth at gcc dot gnu.org [this message]
2023-05-15 15:12 ` [Bug c++/109241] [12/13/14 " cvs-commit at gcc dot gnu.org
2023-05-16 10:11 ` pinskia at gcc dot gnu.org
2023-06-19 12:42 ` pinskia at gcc dot gnu.org
2023-07-18 13:55 ` rguenth at gcc dot gnu.org
2024-04-13 8:11 ` pinskia at gcc dot gnu.org
2024-05-22 19:13 ` pinskia 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-109241-4-p07I9GKRlx@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).