public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "janekb04 at icloud dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99527] New: ICE when using nested lambdas Date: Wed, 10 Mar 2021 19:26:02 +0000 [thread overview] Message-ID: <bug-99527-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99527 Bug ID: 99527 Summary: ICE when using nested lambdas Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: janekb04 at icloud dot com Target Milestone: --- Created attachment 50355 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50355&action=edit The code that causes the error, the preprocessed version of the code and the compiler output When the code in the attachment is compiled it causes an Internal Compiler Error. The code is also available on godbolt: https://godbolt.org/z/vn35js . The code doesn't emit any warning using -Wall -Wextra -Wpedantic. -fno-strict-aliasing -fwrapv don't seem to have any effect. All the information about the compiler version and environment is available on godbolt. For clarity, here is the version and flags. version: g++ (Compiler-Explorer-Build) 11.0.1 20210309 (experimental) Copyright (C) 2021 Free Software Foundation, Inc. flags: -std=c++20 The code that causes the error, the preprocessed version of the code and the compiler output are in the attachment. Not sure if it is relevant, but I will say just in case that the code is based on a technique I discussed here: https://janbielak.com/index.php/2021/01/15/anonymous-types-in-c/ .
next reply other threads:[~2021-03-10 19:26 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-10 19:26 janekb04 at icloud dot com [this message] 2021-08-12 21:54 ` [Bug c++/99527] " pinskia at gcc dot gnu.org 2021-08-13 6:22 ` janekb04 at icloud dot com
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-99527-4@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).