From: Nate Eldredge <nate@thatsmathematics.com>
To: Thomas Rodgers <rodgert@twrodgers.com>
Cc: Jonathan Wakely <jwakely.gcc@gmail.com>,
Jonathan Wakely <jwakely@redhat.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
libstdc++ <libstdc++@gcc.gnu.org>
Subject: Re: [PATCH 1/2] libstdc++: Atomic wait/notify ABI stabilization
Date: Thu, 14 Dec 2023 16:30:07 -0700 (MST) [thread overview]
Message-ID: <021f0c1a-3e37-9e3f-bb2b-09b57aca0144@thatsmathematics.com> (raw)
In-Reply-To: <CAAB_aXvy33gLEzxOLkZg5xu-LoD__Q69bw_kcTeXo9hjv4WX_A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
On Thu, 14 Dec 2023, Thomas Rodgers wrote:
> I need to look at this a bit more (and not on my phone, at lunch).
> Ultimately, C++26 expects to add predicate waits and returning a
> ‘tri-state’ result isn’t something that’s been considered or likely to be
> approved.
Ok, then that seems to fit best with my second suggestion: the predicate
should only test the value and do nothing else, and actually trying to
decrement the semaphore is left up to the caller _M_acquire(), which must
then retry __atomic_wait_address if the compare-exchange fails.
--
Nate Eldredge
nate@thatsmathematics.com
next prev parent reply other threads:[~2023-12-14 23:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 8:16 Nate Eldredge
2023-12-11 19:24 ` Nate Eldredge
2023-12-11 20:18 ` Jonathan Wakely
2023-12-14 22:23 ` Thomas Rodgers
2023-12-14 23:30 ` Nate Eldredge [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-11-16 13:45 Jonathan Wakely
2023-11-16 20:46 ` Jonathan Wakely
2024-03-09 12:18 ` Jonathan Wakely
2024-03-09 12:27 ` Jonathan Wakely
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=021f0c1a-3e37-9e3f-bb2b-09b57aca0144@thatsmathematics.com \
--to=nate@thatsmathematics.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=rodgert@twrodgers.com \
/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).