Expand Minimize

OpCodes.Volatile Field

Specifies that an address currently atop the evaluation stack might be volatile, and the results of reading that location cannot be cached or that multiple stores to that location cannot be suppressed.

Namespace:  System.Reflection.Emit
Assemblies:   System.Reflection.Primitives (in System.Reflection.Primitives.dll)
  mscorlib (in mscorlib.dll)

public static readonly OpCode Volatile

The following table lists the instruction's hexadecimal and Microsoft Intermediate Language (MSIL) assembly format, along with a brief reference summary:

Format

Assembly Format

Description

FE 13

volatile.

Indicates that the subsequent pointer reference is volatile.

The stack transitional behavior, in sequential order, is:

  1. An address is pushed onto the stack.

volatile. specifies that the address is a volatile address (that is, it can be referenced externally to the current thread of execution) and the results of reading that location cannot be cached or that multiple stores to that location cannot be suppressed. Marking an access as volatile affects only that single access; other accesses to the same location must be marked separately. Access to volatile locations need not be performed atomically.

The Unaligned and volatile prefixes can be combined in either order. They must immediately precede a ldind, stind, ldfld, stfld, ldobj, stobj, initblk, or cpblk instruction. Only the volatile prefix is allowed for the Ldsfld and Stsfld instructions.

The following Emit method overload can use the volatile opcode:

  • ILGenerator.Emit(OpCode)

.NET Framework

Supported in: 4.6, 4.5, 4, 3.5, 3.0, 2.0, 1.1

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Supported in: Windows Phone 8.1

Supported in: Windows Phone Silverlight 8.1

Supported in: Windows Phone Silverlight 8
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2015 Microsoft