public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "lewissbaker.opensource at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/94752] New: [coroutines] compiler ICE with coroutine with unnamed parameter Date: Fri, 24 Apr 2020 22:33:07 +0000 [thread overview] Message-ID: <bug-94752-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94752 Bug ID: 94752 Summary: [coroutines] compiler ICE with coroutine with unnamed parameter Product: gcc Version: 10.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: lewissbaker.opensource at gmail dot com Target Milestone: --- See https://godbolt.org/z/QCXqeo Compile the following source code with GCC trunk. Flags: -std=c++20 -fcoroutines ----- #include <coroutine> using namespace std; struct task { struct promise_type { promise_type() {} task get_return_object() { return {}; } suspend_never initial_suspend() { return {}; } suspend_never final_suspend() { return {}; } void return_void() {} void unhandled_exception() {} }; }; task foo(int) { co_return; } ----- Results in an internal-compile-error - segmentation-fault. Pointing at closing curly-brace of 'foo()'. Seems to be related to the parameter being unnamed as naming the parameter results in this code compiling successfully.
next reply other threads:[~2020-04-24 22:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-24 22:33 lewissbaker.opensource at gmail dot com [this message] 2020-04-25 8:47 ` [Bug c++/94752] " iains at gcc dot gnu.org 2020-04-25 9:12 ` iains at gcc dot gnu.org 2020-04-26 19:32 ` cvs-commit at gcc dot gnu.org 2020-04-27 10:01 ` iains 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-94752-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).