Created on 2012-07-27.00:00:00 last changed 130 months ago
[Moved to DR at the April, 2013 meeting.]
Proposed resolution (March, 2013):
Add the following to Clause 3 [intro.defs]:
access
<execution-time action> to read or modify the value of an object
Change 6.9.1 [intro.execution] paragraph 12 as follows:
AccessingReading an object designated by a volatile glvalue (7.2.1 [basic.lval]), modifying an object, calling...
Change 6.9.2 [intro.multithread] paragraph 4 as follows:
Two expression evaluations conflict if one of them modifies a memory location (6.7.1 [intro.memory]) and the other oneaccessesreads or modifies the same memory location.
Change 6.9.2 [intro.multithread] paragraph 24 as follows:
The implementation may assume that any thread will eventually do one of the following:
...
accessread or modify a volatile object, or...
Change 7.6.19 [expr.ass] paragraph 8 as follows:
If the value being stored in an object isaccessed fromread via another object that overlaps in any way the storage of the first object, then the overlap shall be exact and the two objects shall have the same type, otherwise the behavior is undefined. [Note:...
The verb “access” is used in various places in the Standard (see 6.7.3 [basic.life] paragraphs 5 and 6 and 7.2.1 [basic.lval] paragraph 10) but is not defined. C99 defines it as
<execution-time action> to read or modify the value of an object
(See also issue 1530.)
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2014-03-03 00:00:00 | admin | set | status: drwp -> cd3 |
| 2013-10-14 00:00:00 | admin | set | status: dr -> drwp |
| 2013-09-03 00:00:00 | admin | set | messages: + msg4559 |
| 2013-09-03 00:00:00 | admin | set | status: ready -> dr |
| 2013-05-03 00:00:00 | admin | set | messages: + msg4304 |
| 2013-05-03 00:00:00 | admin | set | status: drafting -> ready |
| 2012-11-03 00:00:00 | admin | set | status: open -> drafting |
| 2012-07-27 00:00:00 | admin | create | |