public inbox for libstdc++-cvs@sourceware.org
help / color / mirror / Atom feed
From: Jonathan Wakely <redi@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org, libstdc++-cvs@gcc.gnu.org
Subject: [gcc r10-9056] libstdc++: Fix compilation error with clang-8 [PR 97876]
Date: Fri, 20 Nov 2020 13:49:11 +0000 (GMT)	[thread overview]
Message-ID: <20201120134911.3E316384B824@sourceware.org> (raw)

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.

Diff:
---
 libstdc++-v3/include/std/stop_token | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/include/std/stop_token b/libstdc++-v3/include/std/stop_token
index 76709dd59eb..80f50ea83ca 100644
--- a/libstdc++-v3/include/std/stop_token
+++ b/libstdc++-v3/include/std/stop_token
@@ -166,7 +166,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
       __gthread_t _M_requester;
 #endif
 
-      _Stop_state_t() = default;
+      _Stop_state_t() noexcept { }
 
       bool
       _M_stop_possible() noexcept


                 reply	other threads:[~2020-11-20 13:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20201120134911.3E316384B824@sourceware.org \
    --to=redi@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    --cc=libstdc++-cvs@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).