On 01/09/13 07:42, Aleksey Shipilev wrote:
Sorry, this confuses me even more. This [1] seems to be the version
Scavenging through 9-year-old change-logs is probably not the best path to resolving confusion :-) There were several stabs (and back then a highly non-transparent process!) at conforming to and helping to frame JDK5 VM expectations. The main point to keep in mind is that the fallback wrapper (unsafe.cpp Unsafe_CompareAndSwapLong) does what you expect (uses the enclosing lock), unless you are in an uncommon (and possibly non-existent) situation where you need/expect something else. -Doug
