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++/99047] ICE on simple task coroutine example Date: Mon, 15 Mar 2021 16:00:08 +0000 [thread overview] Message-ID: <bug-99047-4-7XHOqWIwUD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99047-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99047 --- 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:541840b891d61ea70cddd046c96698bb70d7f52c commit r11-7677-g541840b891d61ea70cddd046c96698bb70d7f52c Author: Iain Sandoe <iain@sandoe.co.uk> Date: Sun Mar 14 14:42:52 2021 +0000 coroutines : Convert await_ready () expressions to bool [PR99047]. The awaiter.await_ready() should be converted per [expr.await]/3 (3.6) await-ready is the expression e.await_ready(), contextually converted to bool. gcc/cp/ChangeLog: PR c++/99047 * coroutines.cc (expand_one_await_expression): If the await_ready() expression is not a boolean then convert it as required. gcc/testsuite/ChangeLog: PR c++/99047 * g++.dg/coroutines/pr99047.C: New test.
next prev parent reply other threads:[~2021-03-15 16:00 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-09 22:46 [Bug c++/99047] New: " redbeard0531 at gmail dot com 2021-03-14 13:27 ` [Bug c++/99047] " iains at gcc dot gnu.org 2021-03-14 14:49 ` iains at gcc dot gnu.org 2021-03-15 16:00 ` cvs-commit at gcc dot gnu.org [this message] 2021-03-22 22:04 ` cvs-commit at gcc dot gnu.org 2021-03-24 12:41 ` 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-99047-4-7XHOqWIwUD@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).