On Fri, 11 Jul 2025 14:27:21 GMT, Chen Liang <li...@openjdk.org> wrote:

>> On 32 bit platforms, when an access to long/double is aligned, it is 
>> supported but not atomic. The original wording in 
>> `MethodHandles::byteBufferViewVarHandle` sounds as if it is not supported at 
>> all. We can fix that by borrowing the improved specification from 
>> `MemoryLayout::varHandle`.
>> 
>> Note: This doc is copied from 
>> https://github.com/openjdk/jdk/blob/ee0d309bbd33302d8c6f35155e975db77aaea785/src/java.base/share/classes/java/lang/foreign/MemoryLayout.java#L279-L282
>>  with slight adjustments. See the rendering at 
>> https://docs.oracle.com/en/java/javase/24/docs/api/java.base/java/lang/foreign/MemoryLayout.html#access-mode-restrictions
>
> Chen Liang has updated the pull request incrementally with one additional 
> commit since the last revision:
> 
>   Correct term is atomic, not word tearing

You are right. I should use "may be non-atomic", as the implementation can make 
these operations atomic.

Also re JLS 17.7 for 64-bit platforms: this phrase is qualified to be on 32-bit 
platforms, and we are already under aligned access, so I assume we have 
sufficient preconditions to ignore this aspect.

-------------

PR Comment: https://git.openjdk.org/jdk/pull/26258#issuecomment-3063397506

Reply via email to