public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "harris.hancock at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/102051] [coroutines] ICE in gimplify_var_or_parm_decl, at gimplify.c:2848 Date: Fri, 21 Jul 2023 21:04:26 +0000 [thread overview] Message-ID: <bug-102051-4-2CVS2fdcyH@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-102051-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102051 Harris Hancock <harris.hancock at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |harris.hancock at gmail dot com --- Comment #3 from Harris Hancock <harris.hancock at gmail dot com> --- I have observed this bug, too, while trying to compile Cap'n Proto with coroutine support using GCC 10, 11, and 12. Like Iain, the preprocessed file which Vitali uploaded compiles for me, at least on various versions of x86-64 gcc available in Compiler Explorer. However, Vitali's reduced example, available in the first Compiler Explorer link he posted (https://godbolt.org/z/M5nfEPMKj) readily reproduces the ICE, both in Compiler Explorer on gcc trunk and also locally for me using GCC 12 distributed by Ubuntu Jammy (g++-12 (Ubuntu 12.1.0-2ubuntu1~22.04) 12.1.0), using `g++-12 -o the-file.o -c the-file.i -std=c++20`. The ICE disappears if we modify the following line ~Own() noexcept(false); to ~Own() noexcept(true); So, this appears to be a coroutine bug related to noexcept(false) destructors, similar to Bug 95822.
next prev parent reply other threads:[~2023-07-21 21:04 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-08-24 22:27 [Bug c++/102051] New: " vlovich at gmail dot com 2021-08-24 22:29 ` [Bug c++/102051] " vlovich at gmail dot com 2021-09-30 20:35 ` iains at gcc dot gnu.org 2021-12-17 17:58 ` iains at gcc dot gnu.org 2023-07-21 21:04 ` harris.hancock at gmail dot com [this message] 2023-07-21 21:12 ` harris.hancock at gmail dot com 2024-01-19 11:41 ` vaci at vaci dot org 2024-01-25 19:23 ` ppalka 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-102051-4-2CVS2fdcyH@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).