public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "de34 at live dot cn" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103726] --disable-hosted-libstdcxx (freestanding C++) does not provide <coroutine> as what standard requires
Date: Wed, 15 Dec 2021 23:42:48 +0000 [thread overview]
Message-ID: <bug-103726-4-q6WSwjdkkm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103726-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103726
Jiang An <de34 at live dot cn> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |de34 at live dot cn
--- Comment #6 from Jiang An <de34 at live dot cn> ---
(In reply to Jonathan Wakely from comment #2)
> cppreference is wrong, <coroutine> is not freestanding.
https://eel.is/c++draft/tab:headers.cpp.fs
<coroutine> is still listed as a freestanding header in the recent working
draft. Is there any changed made?
next prev parent reply other threads:[~2021-12-15 23:42 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 4:23 [Bug libstdc++/103726] New: " unlvsur at live dot com
2021-12-15 8:09 ` [Bug libstdc++/103726] " redi at gcc dot gnu.org
2021-12-15 21:10 ` unlvsur at live dot com
2021-12-15 21:36 ` redi at gcc dot gnu.org
2021-12-15 21:36 ` unlvsur at live dot com
2021-12-15 21:39 ` redi at gcc dot gnu.org
2021-12-15 21:39 ` unlvsur at live dot com
2021-12-15 23:42 ` de34 at live dot cn [this message]
2021-12-15 23:46 ` redi at gcc dot gnu.org
2021-12-15 23:54 ` unlvsur at live dot com
2022-01-10 21:14 ` redi at gcc dot gnu.org
2022-01-11 4:13 ` unlvsur at live dot com
2022-01-11 11:26 ` redi at gcc dot gnu.org
2022-01-11 13:29 ` cvs-commit at gcc dot gnu.org
2022-01-11 13:31 ` redi at gcc dot gnu.org
2022-01-11 17:16 ` unlvsur at live dot com
2022-01-11 17:16 ` unlvsur at live dot com
2022-01-11 17:31 ` redi at gcc dot gnu.org
2022-01-11 17:37 ` unlvsur at live dot com
2022-01-11 17:52 ` redi at gcc dot gnu.org
2022-01-11 18:36 ` cvs-commit 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-103726-4-q6WSwjdkkm@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: link
Be 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).