public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/99710] coroutines: co_yield and co_await should only be allowed in suspension context Date: Sun, 03 Oct 2021 19:54:06 +0000 [thread overview] Message-ID: <bug-99710-4-sbZEsQmwgb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99710-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99710 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Iain D Sandoe <iains@gcc.gnu.org>: https://gcc.gnu.org/g:650beb110538097b9c3e8600149b333a83e7e836 commit r12-4102-g650beb110538097b9c3e8600149b333a83e7e836 Author: Iain Sandoe <iain@sandoe.co.uk> Date: Sat Oct 2 14:43:39 2021 +0100 coroutines: Await expressions are not allowed in handlers [PR 99710]. C++20 [expr.await] / 2 An await-expression shall appear only in a potentially-evaluated expression within the compound-statement of a function-body outside of a handler. Signed-off-by: Iain Sandoe <iain@sandoe.co.uk> PR c++/99710 gcc/cp/ChangeLog: * coroutines.cc (await_statement_walker): Report an error if an await expression is found in a handler body. gcc/testsuite/ChangeLog: * g++.dg/coroutines/pr99710.C: New test.
prev parent reply other threads:[~2021-10-03 19:54 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-22 13:04 [Bug c++/99710] New: " nilsgladitz at gmail dot com 2021-09-30 19:16 ` [Bug c++/99710] " iains at gcc dot gnu.org 2021-09-30 19:16 ` iains at gcc dot gnu.org 2021-10-02 18:40 ` iains at gcc dot gnu.org 2021-10-03 19:54 ` cvs-commit 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-99710-4-sbZEsQmwgb@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).