This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of New status.
atomic<T>::notify_one
is unimplementableSection: 32.5.6 [atomics.wait] Status: New Submitter: Anthony Williams Opened: 2019-09-11 Last modified: 2020-09-06
Priority: 2
View other active issues in [atomics.wait].
View all other issues in [atomics.wait].
View all issues with New status.
Discussion:
I am concerned by the wording around atomic<T>::wait()/atomic<T>::notify_one()
.
wait()
observed a
value X
prior to the value Y
which results from a store that happens-before
the notify in order to be eligible to be unlocked.
I am not sure how to implement that.
atomic<int> a = 0; T1: int ra=a, read 0 T1: a.wait(0) T2: a=42 T3: int ra=a, read 42 T3: a.wait(42) T2: a.notify_one()
The wording requires that T1
is eligible to be unlocked, but not T3
, as
there is not a write after the value read by T3
that happens-before
the notify.
T1
and T3
are waiting, so T3
may be woken by the OS.
Waking T3
is allowed (wait()
says it may wake spuriously), but waking T1
is currently required as it is the only thread "eligible to be unblocked".
This requires notify_one()
to wake all waiters, which defeats the purpose.
I suspect we need to change 32.5.6 [atomics.wait] p4.
How about:
"A call to an atomic waiting operation
W
on an atomic objectM
is eligible to be unlocked by a call to an atomic notifying operationN
onM
if"
N
does not happen-beforeW
There are no side effects
X
andY
in the modification order ofM
such thatN
happens-beforeX
,X
precedesY
in the modification order ofM
and an atomic operation that observes the effects ofY
happens-beforeW
.
This would allow T3
to be woken in the preceding example, but prevent it
being woken in the following case:
T1: int ra=a, read 0 T1: a.wait(0) T2: a=42 T2: a.notify_one() T2: a=69 T3: int ra=a, read 69 T3: a.wait(69)
[2020-07-17; Priority set to 2 in telecon]
Proposed resolution:
This wording is relative to N4830.
Modify 32.5.6 [atomics.wait] as indicated:
-4- A call to an atomic waiting operation
W
on an atomic objectM
is eligible to be unblocked by a call to an atomic notifying operationN
onM
ifthere exist side effectsX
andY
onM
such that:
(4.1) —
N
does not happen beforeW
the atomic waiting operation has blocked after observing the result of,X
(4.2) — There are no side effects
X
andprecedesY
in the modification order ofM
, andsuch thatN
happens beforeX
,X
precedesY
in the modification order ofM
and an atomic operation that observes the effects ofY
happens beforeW
.
(4.3) —Y
happens before the call to the atomic notifying operation.