[aarch64-port-dev ] RFR: 8144993: Elide redundant memory barrier after AllocationNode

[Andrew Haley]

On 12/15/2015 04:01 PM, Lindenmaier, Goetz wrote:

> Further, if the object is NoEscape it might not be scalar
> replaced. If I remember correctly, there are various conditions,
> e.g., too big, allocated in loop.

Well, that's the killer.  The definition of "escape" we need to use
here is the really, truly, honest-to-goodness one: that this object
never becomes visible to any other thread by any means.  Unless that
is so, all bets are off.  In this case, what is intended is "appears
in an OOP map".

Andrew.