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 c++/107886] New: Problem witch std::latch, std::binary_semaphores in C++2a
Date: Sun, 27 Nov 2022 17:52:09 +0000 [thread overview]
Message-ID: <bug-107886-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107886
Bug ID: 107886
Summary: Problem witch std::latch, std::binary_semaphores in
C++2a
Product: gcc
Version: 11.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: lukaszcz18 at wp dot pl
Target Milestone: ---
https://github.com/meganz/mingw-std-threads/issues/67
next reply other threads:[~2022-11-27 17:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-27 17:52 lukaszcz18 at wp dot pl [this message]
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
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@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).