Created on 2019-08-19.00:00:00, last changed 2019-09-15.10:35:38.
This wording is relative to N4830.
Modify [atomics.wait] as indicated:
-4- A call to an atomic waiting operation on an atomic object M is eligible to be unblocked by a call to an atomic notifying operation on M if there exist side effects X and Y on M such that:
(4.1) — the atomic waiting operation has blocked after observing the result of X,
(4.2) — X precedes Y in the modification order of M, and
(4.3) — Y happens before the call to the atomic notifying operation.
[ 2019-09-14 Priority set to 3 based on reflector discussion ]
It appears that in a conforming implementation, all but one wait() call on a given atomic object may block forever, regardless of any notify_one() calls, because in principle every notify_one() call could be considered to unblock the same single wait() call. Common sense suggests (and David Olsen confirms) that the intent is for each waiting function call to be (non-spuriously) unblocked by at most one notifying function call, but as far as I can tell the words never say that.
|2019-09-15 10:35:38||admin||set||messages: + msg10617|
|2019-08-23 17:30:17||admin||set||messages: + msg10582|