Title
Overlapping evaluations are allowed
Status
dup
Section
[atomics.order]
Submitter
BSI

Created on 2010-08-25.00:00:00 last changed 164 months ago

Messages

Date: 2011-03-05.21:44:45

Proposed resolution:

Request the concurrency working group to determine if changes are needed. Consider changing the use of "sequence" in [atomics.lockfree]

Date: 2010-10-26.23:46:55

Duplicate: 1459

Addresses GB-131

[atomics.lockfree] p.8 states:

An atomic store shall only store a value that has been computed from constants and program input values by a finite sequence of program evaluations, such that each evaluation observes the values of variables as computed by the last prior assignment in the sequence.

... but [intro.execution] p.13 states:

If A is not sequenced before B and B is not sequenced before A, then A and B are unsequenced. [ Note: The execution of unsequenced evaluations can overlap. — end note ]

Overlapping executions can make it impossible to construct the sequence described in [atomics.lockfree] p.8. We are not sure of the intention here and do not offer a suggestion for change, but note that [atomics.lockfree] p.8 is the condition that prevents out-of-thin-air reads.

History
Date User Action Args
2010-10-26 23:46:55adminsetmessages: + msg5158
2010-10-26 23:46:55adminsetstatus: open -> dup
2010-10-24 03:04:13adminsetmessages: + msg4948
2010-08-25 00:00:00admincreate