Additional notes, October, 2018:

This is also library issue 2506. SG1 has requested a paper to deal with this issue, so it is no longer considered editorial.

Notes from the April, 2017 teleconference:

CWG determined that this issue should be handled editorially; it will be in "review" status until the change has been made and verified. See editorial issue 1611.

Suggested resolution:

Change 6.9.2.2 [intro.races] paragraph 3 as follows:

The library defines a number the set of atomic operations (33.5 [atomics]) and operations on mutexes (Clause 33 [thread]) that. Some of these, and some other library operations, such as those on mutexes ( Clause 33 [thread]) are specially identified as synchronization operations. These operations...

It is not sufficiently clear that the only atomic operations are the ones defined in 33.5 [atomics] by the library. The intent is that no accesses are atomic unless the Standard describes them as such.

An additional problem is that, e.g., new and delete are defined to be synchronization operations, but they are not defined in Clauses 33.5 [atomics] and Clause 33 [thread].