History log of /art/test/004-checker-UnsafeTest18/src/Main.java
Revision Date Author Comments
d07453889fd9f314849df8c172afadb477e46d64 23-Mar-2016 Aart Bik <ajcbik@google.com> Fix potential race condition with threads array.

Rationale:
Array should be filled with threads prior to first fork,
since only in that case does Java memory model ensure
all threads have consistent view of array, which itself is
subject to one test.

BUG=27805463

Change-Id: I28f1eb8461842217ced2255062d2135ef880e7d5
700ae4071cc297e2c567322661704d5eb5af76ae 12-Mar-2016 Aart Bik <ajcbik@google.com> Complete the 1.8 unsafe memory fences tests.

Rationale:
The tests for the fences were still TODO, and this
change list completes them. Java does not quite allow
for a weak memory order on just the signal, but this
is as close as a real unit test as I can think of.
Also added a test suggested by Hans.

BUG=26264765

Change-Id: I2dcb9b02fa63f72daf4c39b3744ff2010888713e
1193259cb37c9763a111825aa04718a409d07145 08-Mar-2016 Aart Bik <ajcbik@google.com> Implement the 1.8 unsafe memory fences directly in HIR.

Rationale:
More efficient since it exposes full semantics to
all operations on the graph and allows for proper
code generation for all architectures.

bug=26264765

Change-Id: Ic435886cf0645927a101a8502f0623fa573989ff
0e54c0160c84894696c05af6cad9eae3690f9496 04-Mar-2016 Aart Bik <ajcbik@google.com> Unsafe: Recognize intrinsics for 1.8 java.util.concurrent
With unit test.

Rationale:
Recognizing the 1.8 methods as intrinsics is the first step
towards providing efficient implementation on all architectures.
Where not implemented (everywhere for now), the methods fall back
to the JNI native or reference implementation.

NOTE: needs iam's CL first!

bug=26264765

Change-Id: Ife65e81689821a16cbcdd2bb2d35641c6de6aeb6