This topic has not yet been rated - Rate this topic

_ReadWriteBarrier

Visual Studio 2012

Microsoft Specific

Limits the compiler optimizations that can reorder memory accesses 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 Template Library. For hardware access, use the /volatile:iso compiler option together with the volatile (C++) keyword.

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 Template Library. For hardware access, use the /volatile:iso compiler option together with the volatile (C++) keyword.

void _ReadWriteBarrier(void);

Requirements

Intrinsic	Architecture
_ReadWriteBarrier	x86, x64

Header file <intrin.h>

Remarks

The _ReadWriteBarrier intrinsic limits the compiler optimizations that can remove or reorder memory accesses across the point of the call.

Reference

_ReadBarrier

_WriteBarrier

Compiler Intrinsics

C++ Keywords

Did you find this helpful? Yes No

Not accurate

Not enough depth

Need more code examples

(1500 characters remaining)

Community Additions

ADD