RFR (S) 8223472: volatile long field corruption on x86_32

David Holmes david.holmes at oracle.com
Wed May 8 12:01:34 UTC 2019


I would very much like an explanation of how this lack of MO_RELAXED 
causes a lack of _atomicity_! What has "MO" got to do with that? And why 
would a volatile access be "relaxed" or "unordered"?

This is not making any sense to me at all.

Thanks,
David

On 8/05/2019 7:07 pm, Erik Österlund wrote:
> Hi Boris,
> 
> Thank you for fixing this. Looks good to me.
> 
> /Erik
> 
> On 2019-05-08 10:17, Boris Ulasevich wrote:
>> Hi all,
>>
>> Please review a simple change to fix long field store atomicity for 
>> 32-bit x86 interpreter.
>>
>> http://bugs.openjdk.java.net/browse/JDK-8223472
>> http://cr.openjdk.java.net/~bulasevich/8223472/webrev.00
>>
>> thanks,
>> Boris
> 


More information about the hotspot-dev mailing list