Release store in C2 putfield
aph at redhat.com
Wed Sep 3 17:07:51 UTC 2014
On 09/03/2014 06:04 PM, Vitaly Davidovich wrote:
> Order of new mem allocated, ctor running with additional stores, and the
> assignment to the reference. Or is this point where allocation + ctor are
> already ordered before?
Yes. There's a store barrier after the object is created.
> Sent from my phone
> On Sep 3, 2014 1:03 PM, "Andrew Haley" <aph at redhat.com> wrote:
>> On 09/03/2014 05:54 PM, Vitaly Davidovich wrote:
>>> Also I thought the memord recorded in the node (also) prevents compiler
>>> from reordering the stores. So even if AArch64 cpu doesn't reorder, what
>>> would prevent compiler reordering?
>> What reordering do you wish to prevent? The store can't happen
>> before the object has been created.
More information about the hotspot-dev