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++/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 15:12:30 +0000 [thread overview] Message-ID: <bug-109241-4-pPkA2qvmnU@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 --- Comment #9 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:396a4e76afec30d2461638f569cae18955eb4ad2 commit r12-9539-g396a4e76afec30d2461638f569cae18955eb4ad2 Author: Jason Merrill <jason@redhat.com> Date: Wed Mar 22 16:11:47 2023 -0400 c++: local class in nested generic lambda [PR109241] In this testcase, the tree walk to look for bare parameter packs was confused by finding a type with no TREE_BINFO. But it should be fine that it's unset; we already checked for unexpanded packs at parse time. I also tried doing the partial instantiation of the local class, which is probably the long-term direction we want to go, but for stage 4 let's go with this safer change. PR c++/109241 gcc/cp/ChangeLog: * pt.cc (find_parameter_packs_r): Handle null TREE_BINFO. gcc/testsuite/ChangeLog: * g++.dg/cpp1y/lambda-generic-local-class2.C: New test.
next prev parent reply other threads:[~2023-05-15 15:12 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 ` [Bug c++/109241] [12/13/14 " rguenth at gcc dot gnu.org 2023-05-15 15:12 ` cvs-commit at gcc dot gnu.org [this message] 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-pPkA2qvmnU@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).