public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "egor_suvorov at mail dot ru" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/93642] [Coroutines] internal compiler error: in expand_expr_addr_expr_1, at expr.c:8070 using co_return Date: Mon, 06 Apr 2020 18:05:33 +0000 [thread overview] Message-ID: <bug-93642-4-DwNX3i2NyG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-93642-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93642 Egor Suvorov <egor_suvorov at mail dot ru> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |egor_suvorov at mail dot ru --- Comment #3 from Egor Suvorov <egor_suvorov at mail dot ru> --- It looks like GCC chokes if it has to call unusual constructor of `promise`. E.g. if `get_return_object()` returns `int` and there is `promise(int)` constructor (with no `coroutine_handle` in sight), same error occurs. However, if I return `promise` from `get_return_object()` and provide `promise(const promise&) {}`, GCC does not crash.
next parent reply other threads:[~2020-04-06 18:05 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-93642-4@http.gcc.gnu.org/bugzilla/> 2020-04-06 18:05 ` egor_suvorov at mail dot ru [this message] 2021-09-30 15:30 ` 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-93642-4-DwNX3i2NyG@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).