In computer programming, volatile means that a value is prone to change over time, outside the control of some code. Volatility has implications within function calling conventions, and also impacts how variables are stored, accessed and cached.
In the C, C++, C#, and Java programming languages, the volatile keyword indicates that a value may change between different accesses, even if it does not appear to be modified. This keyword prevents an optimizing compiler from optimizing away subsequent reads or writes and thus incorrectly reusing a stale value or omitting writes. Volatile values primarily arise in hardware access (memory-mapped I/O), where reading from or writing to memory is used to communicate with peripheral devices, and in threading, where a different thread may have modified a value.
Despite being a common keyword, the behavior of volatile
differs significantly between programming languages, and is easily misunderstood. In C and C++, it is a type qualifier, like [[const (computer programming)|const]]
, and is a property of the type. Furthermore, in C and C++ it does not work in most threading scenarios, and that use is discouraged. In Java and C#, it is a property of a variable and indicates that the object to which the variable is bound may mutate, and is specifically intended for threading. In the D programming language, there is a separate keyword shared
for the threading usage, but no volatile
keyword exists.
In C, and consequently C++, the volatile
keyword was intended to:[1]
[[setjmp]]
and longjmp
sig_atomic_t
variables in signal handlers.Since variables marked as volatile are prone to change outside the standard flow of code, the compiler has to perform every read and write to the variable as indicated by the code. Any access to volatile variables cannot be optimised away, e.g. by use of registers for storage of intermediate values.
While intended by both C and C++, the C standards fail to express that the volatile
semantics refer to the lvalue, not the referenced object. The respective defect report DR 476 (to C11) is still under review with C17.[2]
Operations on volatile
variables are not atomic, nor do they establish a proper happens-before relationship for threading. This is specified in the relevant standards (C, C++, POSIX, WIN32),[1] and volatile variables are not threadsafe in the vast majority of current implementations. Thus, the usage of volatile
keyword as a portable synchronization mechanism is discouraged by many C/C++ groups.[3] [4] [5]
In this example, the code sets the value stored in foo
to 0
. It then starts to poll that value repeatedly until it changes to 255
:
void bar(void)
An optimizing compiler will notice that no other code can possibly change the value stored in foo
, and will assume that it will remain equal to 0
at all times. The compiler will therefore replace the function body with an infinite loop similar to this:
However, foo
might represent a location that can be changed by other elements of the computer system at any time, such as a hardware register of a device connected to the CPU. The above code would never detect such a change; without the volatile
keyword, the compiler assumes that the current program is the only part of the system that could change the value (which is by far the most common situation).
To prevent the compiler from optimizing code as above, the volatile
keyword is used:
void bar (void)
With this modification the loop condition will not be optimized away, and the system will detect the change when it occurs.
Generally, there are memory barrier operations available on platforms (which are exposed in C++11) that should be preferred instead of volatile as they allow the compiler to perform better optimization and more importantly they guarantee correct behaviour in multi-threaded scenarios; neither the C specification (before C11) nor the C++ specification (before C++11) specifies a multi-threaded memory model, so volatile may not behave deterministically across OSes/compilers/CPUs.[6]
The following C programs, and accompanying assembler language excerpts, demonstrate how the volatile
keyword affects the compiler's output. The compiler in this case was GCC.
While observing the assembly code, it is clearly visible that the code generated with volatile
objects is more verbose, making it longer so the nature of volatile
objects can be fulfilled. The volatile
keyword prevents the compiler from performing optimization on code involving volatile objects, thus ensuring that each volatile variable assignment and read has a corresponding memory access. Without the volatile
keyword, the compiler knows a variable does not need to be reread from memory at each use, because there should not be any writes to its memory location from any other thread or process.
Assembly comparison | ||
---|---|---|
Without volatile keyword | With volatile keyword | |
int main |
int main | |
According to the C++11 ISO Standard, the volatile keyword is only meant for use for hardware access; do not use it for inter-thread communication. For inter-thread communication, the standard library provides std::atomic<T>
templates.[7]
The Java programming language also has the volatile
keyword, but it is used for a somewhat different purpose. When applied to a field, the Java qualifier volatile
provides the following guarantees:
Using volatile
may be faster than a lock, but it will not work in some situations before Java 5.[10] The range of situations in which volatile is effective was expanded in Java 5; in particular, double-checked locking now works correctly.[11]
In C#, volatile
ensures that code accessing the field is not subject to some thread-unsafe optimizations that may be performed by the compiler, the CLR, or by hardware. When a field is marked volatile
, the compiler is instructed to generate a "memory barrier" or "fence" around it, which prevents instruction reordering or caching tied to the field. When reading a volatile
field, the compiler generates an acquire-fence, which prevents other reads and writes to the field from being moved before the fence. When writing to a volatile
field, the compiler generates a release-fence; this fence prevents other reads and writes to the field from being moved after the fence.[12]
Only the following types can be marked volatile
: all reference types, Single
, Boolean
, Byte
, SByte
, Int16
, UInt16
, Int32
, UInt32
, Char
, and all enumerated types with an underlying type of Byte
, SByte
, Int16
, UInt16
, Int32
, or UInt32
.[13] (This excludes value structs, as well as the primitive types Double
, Int64
, UInt64
and Decimal
.)
Using the volatile
keyword does not support fields that are passed by reference or captured local variables; in these cases, Thread.VolatileRead
and Thread.VolatileWrite
must be used instead.[12]
In effect, these methods disable some optimizations usually performed by the C# compiler, the JIT compiler, or the CPU itself. The guarantees provided by Thread.VolatileRead
and Thread.VolatileWrite
are a superset of the guarantees provided by the volatile
keyword: instead of generating a "half fence" (ie an acquire-fence only prevents instruction reordering and caching that comes before it), VolatileRead
and VolatileWrite
generate a "full fence" which prevent instruction reordering and caching of that field in both directions.[12] These methods work as follows:[14]
Thread.VolatileWrite
method forces the value in the field to be written to at the point of the call. In addition, any earlier program-order loads and stores must occur before the call to VolatileWrite
and any later program-order loads and stores must occur after the call.Thread.VolatileRead
method forces the value in the field to be read from at the point of the call. In addition, any earlier program-order loads and stores must occur before the call to VolatileRead
and any later program-order loads and stores must occur after the call.The Thread.VolatileRead
and Thread.VolatileWrite
methods generate a full fence by calling the Thread.MemoryBarrier
method, which constructs a memory barrier that works in both directions. In addition to the motivations for using a full fence given above, one potential problem with the volatile
keyword that is solved by using a full fence generated by Thread.MemoryBarrier
is as follows: due to the asymmetric nature of half fences, a volatile
field with a write instruction followed by a read instruction may still have the execution order swapped by the compiler. Because full fences are symmetric, this is not a problem when using Thread.MemoryBarrier
.[12]
VOLATILE
is part of the Fortran 2003 standard,[15] although earlier version supported it as an extension. Making all variables volatile
in a function is also useful finding aliasing related bugs.
By always "drilling down" to memory of a VOLATILE, the Fortran compiler is precluded from reordering reads or writes to volatiles. This makes visible to other threads actions done in this thread, and vice versa.[16]
Use of VOLATILE reduces and can even prevent optimization.[17]