This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 119a. See http://www.open-std.org/jtc1/sc22/wg21/ for the official list.
2025-12-20
[Voted into the WP at the November, 2010 meeting as part of paperN3196.]
N3092 comment CA 15The current draft has release/acquire synchronize-withedges only between a release on one thread and anacquire on adifferent thread, whereas the definition ofdependency-ordered-before permits the release andconsume to be on the same thread; it seems odd to permitthe latter. (At the moment function arguments can't race orsync with each other, but they can be dependencyordered before each other.)
We don't currently have an example in which this makes a realdifference, but for symmetry could suggest changing the definition ofdependency-ordered-before in 6.10.2 [intro.multithread].
Proposed resolution (August, 2010):
Change 6.10.2 [intro.multithread] paragraph 9 as follows:
An evaluationA isdependency-ordered before anevaluationB if
A performs a release operation on an atomic objectM, and, on another thread,B performs aconsume operation onM and reads a value written by any sideeffect in the release sequence headed byA, or
for some evaluationX,A is dependency-orderedbeforeX andX carries a dependency toB.
[Note:...