Talk:cpp/atomic/atomic signal fence

According to my understanding, current content of "atomic_signal_fence" site is inaccurate. I proppose to rewrite it in the following way: Establishes memory synchronization ordering of non-atomic and relaxed atomic accesses, as instructed by order, between a thread and a signal handler executed on the same thread. This is equivalent to std::atomic_thread_fence, except no CPU instructions for memory ordering are issued. Only reordering of the instructions by the compiler is suppressed as order instructs. For example, a fence with release semantics prevents reads or writes from being moved past subsequent writes and a fence with acquire semantics prevents reads or writes from being moved ahead of preceding reads. What do you think?

87.207.65.149 15:21, 6 December 2016 (PST)mrn

ah yes, it's a proliferation of a wording bug that was fixed in the memory_order article recently. yes, both reads and writes are affected. --Cubbi (talk) 19:16, 6 December 2016 (PST)