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++/108829] [13 Regression] internal compiler error: in is_capture_proxy, at cp/lambda.cc:272 Date: Thu, 16 Feb 2023 18:48:40 +0000 [thread overview] Message-ID: <bug-108829-4-UdJa9RjTpY@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108829-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108829 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |13.0 Keywords| |ice-on-valid-code, | |needs-bisection Last reconfirmed|2023-02-16 00:00:00 | Summary|internal compiler error: in |[13 Regression] internal |is_capture_proxy, at |compiler error: in |cp/lambda.cc:272 |is_capture_proxy, at | |cp/lambda.cc:272 Known to work| |12.2.0 --- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Reduced better (to a valid testcase): ``` template <int> void f(void) { constexpr int IDX_PAGE_SIZE = 4096; int abyPage = [=, abyPage] { return IDX_PAGE_SIZE; }(); } void h() { f<1>(); } ```
next prev parent reply other threads:[~2023-02-16 18:48 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-16 18:42 [Bug c++/108829] New: " v.barinov at samsung dot com 2023-02-16 18:43 ` [Bug c++/108829] " v.barinov at samsung dot com 2023-02-16 18:46 ` mpolacek at gcc dot gnu.org 2023-02-16 18:48 ` pinskia at gcc dot gnu.org [this message] 2023-02-16 18:49 ` [Bug c++/108829] [13 Regression] " pinskia at gcc dot gnu.org 2023-02-16 18:50 ` [Bug c++/108829] [12/13 " pinskia at gcc dot gnu.org 2023-02-16 18:55 ` mpolacek at gcc dot gnu.org 2023-02-20 14:18 ` cvs-commit at gcc dot gnu.org 2023-02-20 15:48 ` [Bug c++/108829] [12 " mpolacek at gcc dot gnu.org 2023-02-20 17:27 ` cvs-commit at gcc dot gnu.org 2023-02-20 17:28 ` mpolacek 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-108829-4-UdJa9RjTpY@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).