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-6228] libstdc++: Fix preprocessor condition [PR 98344]
Date: Thu, 17 Dec 2020 14:03:36 +0000 (GMT)	[thread overview]
Message-ID: <20201217140336.F2C343890420@sourceware.org> (raw)

https://gcc.gnu.org/g:8dc63f13f03facc49b777195c9068432477b5dcd

commit r11-6228-g8dc63f13f03facc49b777195c9068432477b5dcd
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Dec 17 12:09:20 2020 +0000

    libstdc++: Fix preprocessor condition [PR 98344]
    
    libstdc++-v3/ChangeLog:
    
            PR libstdc++/98344
            * include/bits/semaphore_base.h: Fix preprocessor condition.

Diff:
---
 libstdc++-v3/include/bits/semaphore_base.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/libstdc++-v3/include/bits/semaphore_base.h b/libstdc++-v3/include/bits/semaphore_base.h
index e4e57de4acf..c796a77f3b1 100644
--- a/libstdc++-v3/include/bits/semaphore_base.h
+++ b/libstdc++-v3/include/bits/semaphore_base.h
@@ -276,7 +276,7 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
 
 // Note: the _GLIBCXX_REQUIRE_POSIX_SEMAPHORE macro can be used to force the
 // use of Posix semaphores (sem_t). Doing so however, alters the ABI.
-#ifdef _GLIBCXX_HAVE_LINUX_FUTEX && !_GLIBCXX_REQUIRE_POSIX_SEMAPHORE
+#if defined _GLIBCXX_HAVE_LINUX_FUTEX && !_GLIBCXX_REQUIRE_POSIX_SEMAPHORE
   // Use futex if available and didn't force use of POSIX
   using __fast_semaphore = __atomic_semaphore<__detail::__platform_wait_t>;
 #elif _GLIBCXX_HAVE_POSIX_SEMAPHORE


                 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=20201217140336.F2C343890420@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).