java volatile long_Java普通变量（未用volatile的修饰）的读和写是否是原子性的？

For the purposes of the Java programming language memory model, a single write to a non-volatile long or double value is treated as two separate writes: one to each 32-bit half. This can result in a situation where a thread sees the first 32 bits of a 64-bit value from one write, and the second 32 bits from another write.

Writes and reads of volatile long and double values are always atomic.

Writes to and reads of references are always atomic, regardless of whether they are implemented as 32-bit or 64-bit values.

Some implementations may find it convenient to divide a single write action on a 64-bit long or double value into two write actions on adjacent 32-bit values. For efficiency's sake, this behavior is implementation-specific; an implementation of the Java Virtual Machine is free to perform writes to long and double values atomically or in two parts.

Implementations of the Java Virtual Machine are encouraged to avoid splitting 64-bit values where possible. Programmers are encouraged to declare shared 64-bit values as volatile or synchronize their programs correctly to avoid possible complications.

在虚拟机规范中并没有规定对非 volatile 的 double 和 long 的读写是原子的，但是虚拟机的具体实现也可以是原子的，对于 volatile 修饰的，读写必须为原子的。

经测试，在 32 位的 intel 机器上，不是原子的，在 64 位的 intel 机器上是原子的