Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
In this article
Microsoft Specific
Limits the compiler optimizations that can reorder memory access operations across the point of the call.
Caution
The _ReadBarrier
, _WriteBarrier
, and _ReadWriteBarrier
compiler intrinsics and the MemoryBarrier
macro are all deprecated and should not be used. For inter-thread communication, use mechanisms such as atomic_thread_fence and std::atomic<T>, which are defined in the C++ Standard Library. For hardware access, use the /volatile:iso compiler option together with the volatile keyword.
void _WriteBarrier(void);
Intrinsic | Architecture |
---|---|
_WriteBarrier |
x86, x64 |
Header file <intrin.h>
The _WriteBarrier
intrinsic limits the compiler optimizations that can remove or reorder memory access operations across the point of the call.
END Microsoft Specific