[aarch64-port-dev ] AARCH64 stage: next steps

[David Holmes]

On 22/01/2015 9:17 PM, Andrew Haley wrote:
> On 01/22/2015 10:12 AM, David Holmes wrote:
>> Yes this is a badly documented flag. While originally (when we only had
>> TSO systems) it allowed you to switch between the memory serialization
>> pseudo-membar trick and full membars/fences,  you need UseMembar for any
>> platform for which the memory serialization trick is not guaranteed to
>> work. As we have discussed before we consider that to be any non-TSO
>> platform, but PPC64 decided otherwise (did Aarch64 do the same?). :)
>
> UseMembar is enabled by default on AArch64.

Then you don't need to use the thread_state()/set_thread_state() 
variants that PPC64 uses.

>  Despite reading the code
> for some time I've been unable to figure out how the serialization page
> is supposed to work.

Try this:

http://home.comcast.net/~pjbishop/Dave/Asymmetric-Dekker-Synchronization.txt

David
-----

> Andrew.
>