public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lukaszcz18 at wp dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/107886] Problem witch std::latch, std::binary_semaphores in C++20
Date: Sun, 27 Nov 2022 18:12:04 +0000	[thread overview]
Message-ID: <bug-107886-4-pPlWWnyTb5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107886-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107886

--- Comment #6 from Jamaika <lukaszcz18 at wp dot pl> ---
I don't understand something. Why _GLIBCXX_HAS_GTHREADS works for std::jthread
but not for std::latch
```
#if defined _GLIBCXX_HAS_GTHREADS || defined _GLIBCXX_HAVE_LINUX_FUTEX
# define __cpp_lib_atomic_wait 201907L
# if __cpp_aligned_new
# define __cpp_lib_barrier 201907L
# endif
#endif
```

  parent reply	other threads:[~2022-11-27 18:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-27 17:52 [Bug c++/107886] New: Problem witch std::latch, std::binary_semaphores in C++2a lukaszcz18 at wp dot pl
2022-11-27 17:56 ` [Bug libstdc++/107886] Problem witch std::latch, std::binary_semaphores in C++20 pinskia at gcc dot gnu.org
2022-11-27 17:58 ` pinskia at gcc dot gnu.org
2022-11-27 18:01 ` lukaszcz18 at wp dot pl
2022-11-27 18:04 ` lukaszcz18 at wp dot pl
2022-11-27 18:05 ` lukaszcz18 at wp dot pl
2022-11-27 18:12 ` lukaszcz18 at wp dot pl [this message]
2022-11-27 20:25 ` redi at gcc dot gnu.org
2022-11-28  8:40 ` lukaszcz18 at wp dot pl
2022-11-28  9:21 ` redi at gcc dot gnu.org
2022-11-28 11:59 ` lukaszcz18 at wp dot pl
2022-11-28 12:03 ` lukaszcz18 at wp dot pl
2022-11-28 12:05 ` lukaszcz18 at wp dot pl
2022-11-28 15:58 ` redi at gcc dot gnu.org
2022-11-28 16:03 ` redi at gcc dot gnu.org
2022-11-28 16:09 ` redi at gcc dot gnu.org
2022-11-28 16:29 ` redi at gcc dot gnu.org
2022-11-28 18:05 ` lukaszcz18 at wp dot pl
2023-01-17 19:36 ` i.nixman at autistici dot 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-107886-4-pPlWWnyTb5@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).