public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <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: Mon, 28 Nov 2022 15:58:29 +0000 [thread overview] Message-ID: <bug-107886-4-fM4t8RycDH@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 #13 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Jamaika from comment #6) > I don't understand something. Why _GLIBCXX_HAS_GTHREADS works for > std::jthread but not for std::latch std::jthread doesn't depend on _GLIBCXX_HAS_GTHREADS, it's always available. But you might not be able to create a new thread using std::jthread if your platform doesn't provide what's needed for it to work. (In reply to Jamaika from comment #10) > ``` > Using built-in specs. > COLLECT_GCC=g++.exe > Target: x86_64-w64-mingw32 > Configured with: /home/ma/m/source/gcc-g/configure --host=x86_64-w64-mingw32 > --target=x86_64-w64-mingw32 --disable-nls > --enable-languages=c,c++,objc,obj-c++ --with-gmp=/home/ma/m/build/for_target > --with-mpfr=/home/ma/m/build/for_target > --with-mpc=/home/ma/m/build/for_target > --with-isl=/home/ma/m/build/for_target --enable-twoprocess > --disable-libstdcxx-pch --disable-win32-registry --disable-shared > --enable-fully-dynamic-string --enable-libssp --prefix=/home/ma/m/target > --with-sysroot=/home/ma/m/target > Thread model: win32 This is the problem. You need a thread model that provides the support needed for C++.
next prev parent reply other threads:[~2022-11-28 15:58 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 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 [this message] 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-fM4t8RycDH@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: 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).