This is an unofficial snapshot of the ISO/IEC JTC1 SC22 WG21 Core Issues List revision 110b. See http://www.open-std.org/jtc1/sc22/wg21/ for the official list.
[Moved to DR at the April, 2013 meeting.]
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.)
Proposed resolution (March, 2013):
Add the following to Clause 3 [intro.defs]:
Change 6.9.1 [intro.execution] paragraph 12 as follows:
Accessingan 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 one
accessesor 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:
accessor modify a volatile object, or
Change 7.6.19 [expr.ass] paragraph 8 as follows:
If the value being stored in an object is
accessed fromanother 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:...