This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of C++11 status.
Section: 33.5.11 [atomics.fences] Status: C++11 Submitter: BSI Opened: 2010-08-25 Last modified: 2016-01-28
Priority: Not Prioritized
View all other issues in [atomics.fences].
View all issues with C++11 status.
Discussion:
Addresses GB-137
Thread fence not only establish synchronizes with relationships, there are semantics of fences that are expressed not in terms of synchronizes with relationships (for example see 33.5.4 [atomics.order] p.5). These semantics also need to apply to the use of atomic_signal_fence in a restricted way.
[Batavia: Concurrency group discussed issue, and is OK with the proposed resolution.]
[2011-02-26 Reflector discussion]
Moved to Tentatively Ready after 5 votes.
Proposed resolution:
Change 33.5.11 [atomics.fences] p. 6 as indicated:
void atomic_signal_fence(memory_order);6 Effects: equivalent to atomic_thread_fence(order), except that
synchronizes with relationshipsthe resulting ordering constraints are established only between a thread and a signal handler executed in the same thread.