public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/100806] deadlock in std::counting_semaphore
Date: Tue, 22 Jun 2021 18:08:15 +0000 [thread overview]
Message-ID: <bug-100806-4-GWF3a4dq8Q@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100806-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100806
--- Comment #4 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-11 branch has been updated by Thomas Rodgers
<rodgertq@gcc.gnu.org>:
https://gcc.gnu.org/g:c24384efbbaeeca3dbc53e7d1226a57bc16e9ad5
commit r11-8638-gc24384efbbaeeca3dbc53e7d1226a57bc16e9ad5
Author: Thomas Rodgers <rodgert@appliantology.com>
Date: Tue Jun 22 10:59:07 2021 -0700
libstdc++: Fix for deadlock in std::counting_semaphore [PR100806]
libstdc++-v3/ChangeLog:
PR libstdc++/100806
* include/bits/semaphore_base.h (__atomic_semaphore::_M_release):
Force _M_release() to wake all waiting threads.
* testsuite/30_threads/semaphore/100806.cc: New test.
(cherry picked from commit e02840c1a92abecd211ffaf05b28329bcb534583)
next prev parent reply other threads:[~2021-06-22 18:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 21:21 [Bug libstdc++/100806] New: " gatroubo at squizzy dot net
2021-05-28 18:08 ` [Bug libstdc++/100806] " rodgertq at gcc dot gnu.org
2021-06-16 18:45 ` rodgertq at gcc dot gnu.org
2021-06-22 18:07 ` cvs-commit at gcc dot gnu.org
2021-06-22 18:08 ` cvs-commit at gcc dot gnu.org [this message]
2022-02-14 17:03 ` rodgertq at gcc dot gnu.org
2022-12-24 21:14 ` pinskia at gcc dot gnu.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-100806-4-GWF3a4dq8Q@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).