Travis hosed yet again, still waiting for pull of PRs #227 and #239, looking to implement weak memory-aware read/writes
adinn at redhat.com
Thu Jul 27 08:55:20 UTC 2017
Thanks for your reply and apologies for the delay in responding -- I
have been kept busy by other things.
> MembarNodes in graal aren't particularly special as far as memory
> optimization goes. Any fixed node which is a MemoryCheckpoint can have
> the required graph effects, so a specialized read node should work just
> as well.
Thanks, that's very useful to know. Having worked through some of the
required changes I think this means modifying the AArch64 code to use
acquiring loads/releasing stores will not be very difficult to implement.
> A NonEmittingMembarNode is just a MembarNode with barriers == 0, so no
> need for a new node I think.
I was beginning to think that was all there was to it. I was just
concerned that one of the phases might decide to delete such nodes as
redundant. Anyway, the info you provided above makes that concern academic.
Senior Principal Software Engineer
Red Hat UK Ltd
Registered in England and Wales under Company Registration No. 03798903
Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander
More information about the graal-dev