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++/104670] [11/12/13/14 Regression] ICE when using decltype of a lambda returning a struct inside of a struct Date: Sat, 13 Apr 2024 20:18:32 +0000 [thread overview] Message-ID: <bug-104670-4-cS23iOOv9U@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-104670-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104670 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Target Milestone|11.5 |12.0 See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=101911 Resolution|--- |FIXED Keywords| |c++-lambda Blocks| |107430 --- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Fixed in GCC 12. Note you can make this an ICE after an invalid error with: ``` struct foo { decltype([] { struct a{ int fn() {} }; a{}; }) bar; }; ``` But that is really PR 101911 . So still closing as fixed. Referenced Bugs: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107430 [Bug 107430] [meta-bug] lambda in decltype
prev parent reply other threads:[~2024-04-13 20:18 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-02-23 20:03 [Bug c++/104670] New: " krzysio.kurek at wp dot pl 2022-02-23 20:30 ` [Bug c++/104670] " pinskia at gcc dot gnu.org 2022-02-23 21:08 ` pinskia at gcc dot gnu.org 2022-02-24 13:12 ` [Bug c++/104670] [9/10/11/12 Regression] " jakub at gcc dot gnu.org 2022-05-27 9:47 ` [Bug c++/104670] [10/11/12/13 " rguenth at gcc dot gnu.org 2022-06-28 10:48 ` jakub at gcc dot gnu.org 2023-07-07 10:42 ` [Bug c++/104670] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-04-13 20:18 ` pinskia at gcc dot gnu.org [this message]
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-104670-4-cS23iOOv9U@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).