RFR: 8073093: AARCH64: C2 generates poor code for ByteBuffer accesses
vitalyd at gmail.com
Tue Feb 17 19:12:31 UTC 2015
What do you mean exactly? I don't think inlining "hides" anything, so the
explicit fence should still be there for EA to see (and preserve).
sent from my phone
On Feb 17, 2015 1:58 PM, "Andrew Haley" <aph at redhat.com> wrote:
> On 02/17/2015 06:42 PM, John Rose wrote:
> > The remaining store fence is probably a bug. A store fence for
> scalarized (lifted-out-of-memory) final fields should go away, since the
> fields are not actually stored in heap memory.
> After inlining how would escape analysis know that the store fence is
> associated with final fields rather than, say, an explicit
> Unsafe.storeFence() ?
More information about the hotspot-dev