8230392: Define AArch64 as MULTI_COPY_ATOMIC

[Andrew Haley]

On 1/24/20 9:01 AM, Andrew Dinn wrote:
> On 23/01/2020 22:41, David Holmes wrote:
>
>> This does make me wonder whether other lock-free code in the VM needs
>> special handling for non-CPU_MULTI_COPY_ATOMIC ??
>
> The only other place I could find a mention (not a use) of symbol
> CPU_MULTI_COPY_ATOMIC -- excluding the point where it is defined -- was
> in a comment in parse1.cpp. That comment talks about barriers for final
> fields which I believe is handled via definition of
> support_IRIW_for_not_multiple_copy_atomic_cpu.

Mmm, but that's an answer to a different question. I'm wondering how
many places there are where multi-copy atomicity is assumed but not
stated (or even realized by the programmer.)

-- 
Andrew Haley  (he/him)
Java Platform Lead Engineer
Red Hat UK Ltd. <https://www.redhat.com>
https://keybase.io/andrewhaley
EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671