public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "davidledger at live dot com.au" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/97452] [coroutines] incorrect sequencing of await_resume() when multiple co_await expressions occur in a single statement Date: Thu, 29 Oct 2020 06:11:29 +0000 [thread overview] Message-ID: <bug-97452-4-nVPvMmtvnx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97452-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97452 --- Comment #4 from David Ledger <davidledger at live dot com.au> --- @Iain Sandoe In terms of the standard do you think this is technically undefined behaviour? I tried bring this up with Std-Proposals but got no response at all. I believe either I'm very bad at writing (likely), or nobody knows whether or not this is undefined behaviour and therefore the conversation didn't start. If this is undefined behaviour I believe a defect report is in order.
next prev parent reply other threads:[~2020-10-29 6:11 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-16 1:40 [Bug c++/97452] New: " lewissbaker.opensource at gmail dot com 2020-10-16 6:55 ` [Bug c++/97452] " iains at gcc dot gnu.org 2020-10-16 7:04 ` iains at gcc dot gnu.org 2020-10-17 3:15 ` davidledger at live dot com.au 2020-10-17 7:30 ` iains at gcc dot gnu.org 2020-10-29 6:11 ` davidledger at live dot com.au [this message] 2020-10-29 7:52 ` iains at gcc dot gnu.org 2020-12-02 9:01 ` davidledger at live dot com.au 2020-12-02 9:02 ` iains at gcc dot gnu.org 2021-04-08 12:02 ` rguenth at gcc dot gnu.org 2021-04-09 10:23 ` lewissbaker.opensource at gmail dot com 2021-05-04 12:31 ` rguenth at gcc dot gnu.org 2022-06-28 10:42 ` jakub at gcc dot gnu.org 2022-11-12 3:31 ` davidledger at live dot com.au 2023-01-19 14:08 ` davidledger at live dot com.au 2023-07-07 9:10 ` rguenth 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-97452-4-nVPvMmtvnx@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).