June 22, 2023
7:31 a.m.
On Mon Jun 19 13:25:54 2023 +0000, Jinoh Kang wrote:
A compiler barrier is (still) required regardless of whether or not the underlying architecture has strong memory ordering semantics. ```suggestion:-0+0 #define __SHARED_READ_FENCE __asm__ __volatile__( "" ::: "memory" ) ``` I think that it's actually not needed for the same reasons as described below: everything that is accessed in between is volatile.
-- https://gitlab.winehq.org/wine/wine/-/merge_requests/3103#note_36552