Java memory model: volatile variables and happens-before

by
  • i = 1 always happens-before v = 2

True. By JLS section 17.4.5,

If x and y are actions of the same thread and x comes before y in program order, then hb(x, y).

  • v = 2 happens-before vDst = v in JMM only if it’s actually happens before in time
  • i = 1 happens-before iDst = i in JMM (and iDst will be predictably assigned 1) if v = 2 actually happens before vDst = v in time

False. The happens-before order does not make guarantees about things happening before each other in physical time. From the same section of the JLS,

It should be noted that the presence of a happens-before relationship between two actions does not necessarily imply that they have to take place in that order in an implementation. If the reordering produces results consistent with a legal execution, it is not illegal.

It is, however, guaranteed that v = 2 happens-before vDst = v and i = 1 happens-before iDst = i if v = 2 comes before vDst = v in the synchronization order, a total order over the synchronization actions of an execution that is often mistaken for the real-time order.

  • Otherwise order between i = 1 and iDst = i is undefined and resulting value of iDst is undefined as well

This is the case if vDst = v comes before v = 2 in the synchronization order, but actual time doesn’t come into it.

More Related Contents:

  1. What does “volatile” mean in Java?
  2. Volatile guarantees and out-of-order execution [duplicate]
  3. Detailed semantics of volatile regarding timeliness of visibility
  4. What is the volatile keyword useful for?
  5. Difference between volatile and synchronized in Java
  6. Volatile vs Static in Java
  7. What is the difference between atomic / volatile / synchronized?
  8. Volatile boolean vs AtomicBoolean
  9. When exactly do you use the volatile keyword in Java? [duplicate]
  10. What is in Java object header?
  11. Is volatile expensive?
  12. Happens-before relationships with volatile fields and synchronized blocks in Java – and their impact on non-volatile variables?
  13. Must all properties of an immutable object be final?
  14. Volatile variable in Java
  15. Volatile Vs Atomic [duplicate]
  16. do we need volatile when implementing singleton using double-check locking
  17. How can CopyOnWriteArrayList be thread-safe?
  18. Memory effects of synchronization in Java
  19. Instruction reordering & happens-before relationship [duplicate]
  20. Simplest and understandable example of volatile keyword in Java
  21. Is Dalvik’s memory model the same as Java’s?
  22. Are volatile variable ‘reads’ as fast as normal reads?
  23. Java volatile array?
  24. Java volatile modifier and synchronized blocks
  25. Java concurrency: is final field (initialized in constructor) thread-safe?
  26. Why doesn’t volatile in java 5+ ensure visibility from another thread?
  27. Analyzing of x86 output generated by JIT in the context of volatile
  28. How to declare array elements volatile in Java?
  29. How Synchronization works in Java?
  30. When is it preferable to use volatile boolean in Java rather than AtomicBoolean? [duplicate]

Leave a Comment