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 libstdc++/97876] stop_token header doesn't compile on clang-8 with -std=c++20
Date: Fri, 20 Nov 2020 13:49:12 +0000 [thread overview]
Message-ID: <bug-97876-4-E4tQjjSV4H@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97876-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97876
--- Comment #10 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jonathan Wakely
<redi@gcc.gnu.org>:
https://gcc.gnu.org/g:a186d72afd6cfb13efd4a0ec82049d79892334fd
commit r10-9056-ga186d72afd6cfb13efd4a0ec82049d79892334fd
Author: Jonathan Wakely <jwakely@redhat.com>
Date: Thu Nov 19 22:32:54 2020 +0000
libstdc++: Fix compilation error with clang-8 [PR 97876]
This fixes a compilation error with clang-8 and earlier. This change is
only on the gcc-10 branch, not master, because the <stop_token> header
is included indirectly in more places on the branch than on master.
PR libstdc++/97876
* include/std/stop_token (_Stop_state_t): Define default
constructor as user-provided not defaulted.
next prev parent reply other threads:[~2020-11-20 13:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-17 17:29 [Bug libstdc++/97876] New: " eric.niebler at gmail dot com
2020-11-17 19:19 ` [Bug libstdc++/97876] " redi at gcc dot gnu.org
2020-11-17 19:22 ` redi at gcc dot gnu.org
2020-11-17 21:19 ` eric.niebler at gmail dot com
2020-11-18 17:09 ` redi at gcc dot gnu.org
2020-11-19 21:24 ` eric.niebler at gmail dot com
2020-11-19 21:39 ` redi at gcc dot gnu.org
2020-11-19 21:41 ` redi at gcc dot gnu.org
2020-11-19 22:54 ` redi at gcc dot gnu.org
2020-11-20 13:27 ` cvs-commit at gcc dot gnu.org
2020-11-20 13:49 ` cvs-commit at gcc dot gnu.org [this message]
2020-11-20 13:49 ` cvs-commit at gcc dot gnu.org
2020-11-20 13:57 ` redi 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-97876-4-E4tQjjSV4H@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).