public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108606] [13 Regression] ICE in potential_constant_expression_1 with friend function declaration inside a local class of a generic/templated lambda Date: Tue, 21 Feb 2023 13:25:49 +0000 [thread overview] Message-ID: <bug-108606-4-YM4vYyyaL7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108606-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108606 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Adjusted #c0 testcase that is accepted up to r13-2164 and ICEs with r13-2165 up to current trunk: template <typename T> void bar (T) {} void foo () { bar ([&](auto x) { class C { friend void baz (); }; }); } I can confirm #c1 doesn't reproduce for me either.
next prev parent reply other threads:[~2023-02-21 13:25 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-30 20:08 [Bug c++/108606] New: [13 Regression] ICE in potential_constant_expression_1, at cp/constexpr.cc:9713 gscfq@t-online.de 2023-01-30 20:13 ` [Bug c++/108606] [13 Regression] ICE in potential_constant_expression_1 with friend function declaration inside a local class of a generic/templated lambda pinskia at gcc dot gnu.org 2023-01-30 20:13 ` pinskia at gcc dot gnu.org 2023-01-31 15:22 ` mpolacek at gcc dot gnu.org 2023-01-31 15:25 ` mpolacek at gcc dot gnu.org 2023-02-21 12:51 ` rguenth at gcc dot gnu.org 2023-02-21 13:25 ` jakub at gcc dot gnu.org [this message] 2023-02-21 13:48 ` jakub at gcc dot gnu.org 2023-03-01 9:25 ` cvs-commit at gcc dot gnu.org 2023-03-01 9:28 ` jakub 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-108606-4-YM4vYyyaL7@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).