public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/94359] new test case g++.dg/coroutines/torture/symmetric-transfer-00-basic.C fails Date: Fri, 27 Mar 2020 17:16:12 +0000 [thread overview] Message-ID: <bug-94359-4-IAx9XbFuUp@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-94359-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94359 --- Comment #2 from Iain Sandoe <iains at gcc dot gnu.org> --- it is not mandatory (for C++20 compliance) that the implementation provides symmetric transfer - so it could be switched off - or XFAILed. However, users state that an impl. that can't do the symmetric transfers is not useful in a number of important applications.
next prev parent reply other threads:[~2020-03-27 17:16 UTC|newest] Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-03-27 16:30 [Bug target/94359] New: " seurer at linux dot vnet.ibm.com 2020-03-27 17:13 ` [Bug target/94359] " iains at gcc dot gnu.org 2020-03-27 17:16 ` iains at gcc dot gnu.org [this message] 2020-03-27 21:48 ` iains at gcc dot gnu.org 2020-03-28 9:18 ` iains at gcc dot gnu.org 2020-03-28 16:10 ` iains at gcc dot gnu.org 2020-03-29 10:58 ` iains at gcc dot gnu.org 2020-04-02 11:09 ` ro at gcc dot gnu.org 2020-04-02 11:26 ` iains at gcc dot gnu.org 2020-04-02 11:51 ` ro at gcc dot gnu.org 2020-04-02 17:38 ` ebotcazou at gcc dot gnu.org 2020-04-09 20:40 ` iains at gcc dot gnu.org 2020-04-09 20:41 ` iains at gcc dot gnu.org 2020-04-14 18:58 ` [Bug c++/94359] " iains at gcc dot gnu.org 2020-04-14 19:44 ` cvs-commit at gcc dot gnu.org 2020-04-15 11:50 ` schwab@linux-m68k.org 2020-04-15 13:03 ` iains at gcc dot gnu.org 2020-04-15 13:24 ` schwab@linux-m68k.org 2020-04-16 23:02 ` cvs-commit at gcc dot gnu.org 2020-04-27 10:23 ` 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-94359-4-IAx9XbFuUp@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).