public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/94702] std::unsequenced_policy should not be defined for C++17
Date: Wed, 22 Apr 2020 22:15:12 +0000 [thread overview]
Message-ID: <bug-94702-4-w10VDxDaoX@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94702-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94702
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> Another bug is that we don't support the __cpp_lib_execution macro, which
> should have been updated to indicate this policy is supported.
That has been fixed in g:aac39307e8f589dba231083a3e9aa3d0ff302837 so that
__cpp_lib_execution is always defined to 201902L even in C++17, to reflect that
this policy is always defined. That way the feature test macro accurately
describes our implementation.
next prev parent reply other threads:[~2020-04-22 22:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 21:02 [Bug libstdc++/94702] New: " redi at gcc dot gnu.org
2020-04-21 21:42 ` [Bug libstdc++/94702] " rodgertq at gcc dot gnu.org
2020-04-22 21:32 ` redi at gcc dot gnu.org
2020-04-22 22:15 ` redi at gcc dot gnu.org [this message]
2020-04-22 22:16 ` redi at gcc dot gnu.org
2020-04-23 20:16 ` 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-94702-4-w10VDxDaoX@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).