Skip to content

Latest commit

 

History

History
149 lines (81 loc) · 4.1 KB

nf-winnt-interlockedxor16.md

File metadata and controls

149 lines (81 loc) · 4.1 KB
UID title description helpviewer_keywords old-location tech.root ms.assetid ms.date ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.ddi-compliance req.unicode-ansi req.idl req.max-support req.namespace req.assembly req.type-library req.lib req.dll req.irql targetos req.typenames req.redist ms.custom f1_keywords dev_langs topic_type api_type api_location api_name
NF:winnt.InterlockedXor16
InterlockedXor16 function (winnt.h)
Performs an atomic XOR operation on the specified SHORT values.
InterlockedXor16
InterlockedXor16 function
base.interlockedxor16
winnt/InterlockedXor16
base\interlockedxor16.htm
backup
414830ba-ce2b-4ed0-96f4-db5edd8e4ebe
12/05/2018
InterlockedXor16, InterlockedXor16 function, base.interlockedxor16, winnt/InterlockedXor16
winnt.h
Windows.h
Windows
Windows
19H1
InterlockedXor16
winnt/InterlockedXor16
c++
APIRef
kbSyntax
HeaderDef
Winnt.h
InterlockedXor16

InterlockedXor16 function

-description

Performs an atomic XOR operation on the specified SHORT values. The function prevents more than one thread from using the same variable simultaneously.

-parameters

-param Destination [in, out]

A pointer to the first operand. This value will be replaced with the result of the operation.

-param Value [in]

The second operand.

-returns

The function returns the original value of the Destination parameter.

-remarks

The interlocked functions provide a simple mechanism for synchronizing access to a variable that is shared by multiple threads. This function is atomic with respect to calls to other interlocked functions.

For the Intel Itanium-based systems and x64 architectures, this function is implemented using the compiler intrinsic. For the x86 architecture, use the _InterlockedXor16 compiler intrinsic directly.

This function generates a full memory barrier (or fence) to ensure that memory operations are completed in order.

Itanium-based systems:  For performance-critical applications, use InterlockedXor16Acquire or InterlockedXor16Release instead.

Note  This function is supported on Windows RT-based systems.
 

-see-also

Interlocked Variable Access

InterlockedXor

InterlockedXor16Acquire

InterlockedXor16NoFence

InterlockedXor16Release

InterlockedXor64

InterlockedXor64Acquire

InterlockedXor64NoFence

InterlockedXor64Release

InterlockedXor8

InterlockedXor8Acquire

InterlockedXor8NoFence

InterlockedXor8Release

InterlockedXorAcquire

InterlockedXorNoFence

InterlockedXorRelease

Synchronization Functions