public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rodgertq at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/104442] atomic<T>::wait incorrectly loops in case of spurious notification when __waiter is shared
Date: Wed, 09 Feb 2022 15:29:13 +0000 [thread overview]
Message-ID: <bug-104442-4-VjfSO2ideI@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104442-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104442
--- Comment #4 from Thomas Rodgers <rodgertq at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> Tom submitted
> https://gcc.gnu.org/pipermail/gcc-patches/2022-February/590050.html already,
> which is slightly different.
The primary difference was changing the memory order of the load in _M_do_spin.
I may revert that part of the change and submit it separately, as I've noticed
one other case where I'd like to change it from RELAXED to SEQ_CST.
next prev parent reply other threads:[~2022-02-09 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-08 16:31 [Bug libstdc++/104442] New: " poulhies at adacore dot com
2022-02-09 0:27 ` [Bug libstdc++/104442] " rodgertq at gcc dot gnu.org
2022-02-09 8:51 ` poulhies at adacore dot com
2022-02-09 10:16 ` redi at gcc dot gnu.org
2022-02-09 15:29 ` rodgertq at gcc dot gnu.org [this message]
2022-02-09 20:31 ` cvs-commit at gcc dot gnu.org
2022-02-09 20:32 ` cvs-commit at gcc dot gnu.org
2022-02-10 8:52 ` poulhies at adacore dot com
2022-02-10 17:57 ` rodgertq at gcc dot gnu.org
2022-02-11 8:16 ` poulhies at adacore dot com
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-104442-4-VjfSO2ideI@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).