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

Andrew Haley aph at redhat.com
Thu Dec 17 15:43:38 UTC 2015


The potential problem only arises if "this" is published unsafely and
the object to which it is published doesn't escape.

Can't we detect unsafe publication?  It ought to be easier than escape
analysis: it's a matter of detecting that "this" escapes from the
constructor.

Andrew.


More information about the aarch64-port-dev mailing list