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++/111728] C++ 20 coroutine segmentation fault in generic lambda Date: Sun, 08 Oct 2023 21:55:26 +0000 [thread overview] Message-ID: <bug-111728-4-8zxKpCk2XW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111728-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111728 Andrew Pinski <pinskia at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-10-08 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW --- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> --- Reduced to just using coroutine header file: ``` #include <coroutine> struct promise; struct coroutine : std::coroutine_handle<promise> { using promise_type = ::promise; bool await_ready() { return false; } void await_suspend( coroutine_handle h) {} int await_resume() {} }; struct promise { coroutine get_return_object() { return {coroutine::from_promise(*this)}; } std::suspend_always initial_suspend() noexcept { return {}; } std::suspend_always final_suspend() noexcept { return {}; } void return_void() {} void unhandled_exception() {} }; coroutine write_fields() { int static_buffer[10]; co_await [](auto) -> coroutine { if (sizeof(static_buffer)); co_return; }(0); } ``` Confirmed.
prev parent reply other threads:[~2023-10-08 21:55 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-10-08 17:03 [Bug c++/111728] New: " yunus at ayar dot eu 2023-10-08 17:08 ` [Bug c++/111728] " pinskia at gcc dot gnu.org 2023-10-08 21:55 ` pinskia at gcc dot gnu.org [this message]
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-111728-4-8zxKpCk2XW@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).