[concurrency-interest] JLS 17.7 Non-atomic treatment of double and long : Android
vitalyd at gmail.com
Tue Apr 30 11:56:01 EDT 2013
I don't see how 32bit Hotspot can *not * split 64 bit values given
registers are not wide enough.
Easiest would be to hook up hsdis to hotspot and look at the disassembly.
Sent from my phone
On Apr 30, 2013 10:42 AM, "Tim Halloran" <hallorant at gmail.com> wrote:
> On Mon, Apr 29, 2013 at 4:59 PM, Aleksey Shipilev <
> aleksey.shipilev at oracle.com> wrote:
>> Yes, that's exactly what I had in mind:
>> a. Declare "long a"
>> b. Ramp up two threads.
>> c. Make thread 1 write 0L and -1L over and over to field $a
>> d. Make thread 2 observe the field a, and count the observed values
>> e. ...
>> f. PROFIT!
>> P.S. It is important to do some action on value read in thread 2, so
>> that it does not hoisted from the loop, since $a is not supposed to be
> This discussion is getting a bit far afield, I guess, but to get back onto
> the topic. I followed Aleksey's advice. And wrote an implementation that
> tests this. I used two separate threads to write 0L and -1L into the long
> field "a" but that is the only real change I made. (I already had some
> scaffolding code to run things on Android or desktop Java).
> *Android: splits writes to longs into two parts.*
> On a Samsung Galaxy II with Android 4.0.4 a Nexus 4 phone with Android
> 4.2.2 I saw non-atomic treatment of long. The value -4294967296
> (xFFFFFFFF00000000) showed up as well as 4294967295 (x00000000FFFFFFFF).
> So looks like Android does not follow the (albeit optional) advice in the
> Java language specification about this.
> *JDK: DOES NOT split writes to longs into two parts (even 32-bit
> Of course we couldn't get this to happen on any 64-bit JVM, but we tried
> it out under Linux on 32-bit OpenJDK 1.7.0_21 it does NOT happen. The
> 32-bit JVM implementations follow the recommendation of the Java language
> An interesting curio. I wonder how many crashes in "working" Java code
> moved from desktop Java onto Android programmers are going to lose sleep
> tracking down this one.
> Best regards,
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Concurrency-interest