public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tedlion_tang at foxmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/106183] std::atomic::wait might fail to be unblocked by notify_one/all on platforms without platform_wait()
Date: Fri, 15 Jul 2022 12:45:41 +0000 [thread overview]
Message-ID: <bug-106183-4-GkcZa4ivDY@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106183-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106183
Ted_lion <tedlion_tang at foxmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tedlion_tang at foxmail dot com
--- Comment #1 from Ted_lion <tedlion_tang at foxmail dot com> ---
I found my program blocked and it turned out to be the same problem of
atomic::wait. According to the C++20 Standard, the function atomic::wait should
perform an atomic waiting operations. The subprocedure of comparison with old
value and waiting for the notification should not be interrupted by an
operation on same atomic object.
next prev parent reply other threads:[~2022-07-15 12:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-04 13:55 [Bug libstdc++/106183] New: std::atomic::wait might deadlock " lewissbaker.opensource at gmail dot com
2022-07-06 0:04 ` [Bug libstdc++/106183] std::atomic::wait might fail to be unblocked by notify_one/all " rodgertq at gcc dot gnu.org
2022-07-15 12:45 ` tedlion_tang at foxmail dot com [this message]
2022-07-15 14:36 ` redi at gcc dot gnu.org
2022-07-25 13:51 ` anthony.ajw at gmail dot com
2022-08-01 11:38 ` redi at gcc dot gnu.org
2022-08-04 12:30 ` cvs-commit at gcc dot gnu.org
2022-08-04 12:42 ` redi at gcc dot gnu.org
2023-01-16 17:43 ` redi at gcc dot gnu.org
2023-01-16 17:46 ` cvs-commit at gcc dot gnu.org
2023-01-17 6:59 ` i.nixman at autistici dot org
2023-01-18 11:29 ` cvs-commit at gcc dot gnu.org
2023-01-18 11:33 ` redi 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-106183-4-GkcZa4ivDY@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).