[lworld] Integrated: 8264414: [lworld] [AArch64] TestBufferTearing.java fails with C1

Nick Gasson ngasson at openjdk.java.net
Thu Apr 15 06:29:51 UTC 2021

On Thu, 1 Apr 2021 10:08:45 GMT, Nick Gasson <ngasson at openjdk.org> wrote:

> We see failures like this on AArch64 when MyValue.incrementAndCheck() is
> compiled with C1:
>   java.lang.RuntimeException: Inconsistent field values: expected 0 to equal 675128
>         at jdk.test.lib.Asserts.fail(Asserts.java:594)
>         at jdk.test.lib.Asserts.assertEquals(Asserts.java:205)
>         at jdk.test.lib.Asserts.assertEQ(Asserts.java:178)
>         at compiler.valhalla.inlinetypes.MyValue.incrementAndCheck(TestBufferTearing.java:81)
>         at compiler.valhalla.inlinetypes.TestBufferTearing$Runner.run(TestBufferTearing.java:124)
> The barrier that is usually inserted on return from a method that wrote
> final fields should be sufficient to prevent another thread seeing the
> zero-initialised intermediate state.  However this barrier isn't
> inserted at the moment because method()->is_object_constructor() is
> false for primitive class constructors.
> C2 has a similar guard around the memory barrier in Parse::do_exits().
> I'm not sure if that needs amending as well but I've not seen any
> failures due to it.

This pull request has now been integrated.

Changeset: 2e6c276a
Author:    Nick Gasson <ngasson at openjdk.org>
Committer: Tobias Hartmann <thartmann at openjdk.org>
URL:       https://git.openjdk.java.net/valhalla/commit/2e6c276a
Stats:     138 lines in 3 files changed: 137 ins; 0 del; 1 mod

8264414: [lworld] [AArch64] TestBufferTearing.java fails with C1

Reviewed-by: thartmann, fparain


PR: https://git.openjdk.java.net/valhalla/pull/376

More information about the valhalla-dev mailing list