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 r11-6229] libstdc++: Fix -Wunused warning Date: Thu, 17 Dec 2020 14:03:42 +0000 (GMT) [thread overview] Message-ID: <20201217140342.31CAC3890420@sourceware.org> (raw) https://gcc.gnu.org/g:9f9dbc8e09cf48406aa24b6c78735f1a7912cc4e commit r11-6229-g9f9dbc8e09cf48406aa24b6c78735f1a7912cc4e Author: Jonathan Wakely <jwakely@redhat.com> Date: Thu Dec 17 13:16:02 2020 +0000 libstdc++: Fix -Wunused warning As noted in PR 66146 comment 35, there is a new warning in the new std::call_once implementation. libstdc++-v3/ChangeLog: * src/c++11/mutex.cc (std::once_flag::_M_finish): Add maybe_unused attribute to variable used in assertion. Diff: --- libstdc++-v3/src/c++11/mutex.cc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/libstdc++-v3/src/c++11/mutex.cc b/libstdc++-v3/src/c++11/mutex.cc index 4d42bed8ecc..93a5eae391d 100644 --- a/libstdc++-v3/src/c++11/mutex.cc +++ b/libstdc++-v3/src/c++11/mutex.cc @@ -74,7 +74,8 @@ std::once_flag::_M_finish(bool returning) noexcept } else { - int prev = __atomic_exchange_n(&_M_once, newval, __ATOMIC_RELEASE); + int prev [[maybe_unused]] + = __atomic_exchange_n(&_M_once, newval, __ATOMIC_RELEASE); __glibcxx_assert(prev & _Bits::_Active); // Wake any other threads waiting for this execution to finish. constexpr int futex_wake = 129; // FUTEX_WAKE_PRIVATE
reply other threads:[~2020-12-17 14:03 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=20201217140342.31CAC3890420@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: 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).