November 2018 - aarch64-port-dev

AARCH64 support for lworld
by Dmitry Samersoff 08 Sep '19

08 Sep '19

Hello Everybody, I started implementation of AARCH64 support for lworld. I'm on very early stage so any advices are highly appreciated. Should I file a CR for this task somewhere? What is correct way to do it? -Dmitry -- Dmitry Samersoff http://devnull.samersoff.net * There will come soft rains ...

6 28

[Roland Westrelin] Re: Aarch64 port for ZGC, so far
by Roland Westrelin 24 May '19

24 May '19

Just noticed I didn't include the mailing lists in that reply. Roland.

7 43

RFC: 64 bit literal oops
by Stuart Monteith 14 Feb '19

14 Feb '19

Hello, I've been testing my patch to make literal oops 64-bit rather than 48-bit. This is a necessary prerequisite for ZGC to operate on aarch64 using tagged pointers. I'm not submitting this in it's final form, but just for a view on whether this is the proper way to do this. The patch is here: http://cr.openjdk.java.net/~smonteith/oop64/webrev-20181002/ I've tested it against jtreg and G1GC, and get clean results as compared to without the patch. No issues are apparent running SPECjbb-2015. There are essentially 7 changes: 1. There is a new options: -XX:+Use64BitLiteralOops 2. MacroAssembler::patch_oop(address,address) patches 64-bit addresses if the flag is enabled. 3. MacroAssembler::target_addr_for_insn(address, unsigned) is modified to pull out a 64-bit target address, if there is an extra movk, and then calls ShouldNotReachHere(). 4. MacroAssembler::mov(Register, Address) has been changed to call movptr with a flag set if the address is an Oop. 5. MacroAssembler::movptr(Register, uintptr_t) has been modified to take a flag indicating if it is an oop that is being emitted. If Use64BitLiteralOops has been set, then an additional movk is emitted to make up the 64 bit literal. 6. NativeInstruction::is_oop_at(int) was added, to detect if an oop exists at the address. 7. NativeMovConstReg::next_instruction_address() has been changed to handle get the address after "movz, movk, movk" and with 64 bit oops "movz, movk, movk, movk." (6) has never been observed,, so I don't consider it tested - there aren't circumstances where it returns true, so arguably it it should be replaced by an appropriate assert. Likewise, (3) is also an unnecessary change - the ShouldNotReachHere() never traps during testing - it was left in for review purposes. It has been mentioned to me that we could just use 64-bit literals, as that would make things simpler - I look forward to people's opinions. It was also mentioned ages ago that in future the coloured bits could be made irrelevant for ZGC. There is the up and coming 52-bit VA scheme for Arm v8. If we are to use >48 bits of address space we will have to ask for it explicitly, in which case we'd need to use 64 bit oops. The class metadata could remain 48-bit in that case. There is an interesting presentation on 52-bit VA here: https://connect.linaro.org/resources/yvr18/yvr18-119/ BR, Stuart

4 8

RFR(M): 8212043: Add floating-point Math.min/max intrinsics
by Pengfei Li (Arm Technology China) 13 Dec '18

13 Dec '18

Hi, I would like to enable intrinsics of floating-point Math.min/max methods on AArch64. Could anyone help review this change? Webrev: http://cr.openjdk.java.net/~pli/rfr/8212043/webrev.00/ JBS: https://bugs.openjdk.java.net/browse/JDK-8212043 Below is the description of Math.max(double,double) in Java API doc. Behaviors of the other 3 methods are similar. "Returns the greater of two double values. That is, the result is the argument closer to positive infinity. If the arguments have the same value, the result is that same value. If either value is NaN, then the result is NaN. Unlike the numerical comparison operators, this method considers negative zero to be strictly smaller than positive zero. If one argument is positive zero and the other negative zero, the result is positive zero." [1] In AArch64 floating-point instruction set, the fmax instruction[2] has exactly the same behavior to the API description above. So these min/max calculations can be done in one single instruction. I also added a jtreg case[3] in this change to test these special arguments, including +0.0, -0.0, +inf, -inf and NaN. I ran the full jtreg test and no new issues were found. As I'm not familiar with other ISAs, intrinsics are enabled only on AArch64 in this change. I hope someone else can enable them on other platforms, if possible. [1] https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang/Math… [2] https://developer.arm.com/docs/dui0801/latest/a64-floating-point-instructio… [3] http://cr.openjdk.java.net/~pli/rfr/8212043/webrev.00/test/hotspot/jtreg/co… -- Thanks, Pengfei

3 27

RFR(S): 8205421 - AARCH64: StubCodeMark should be placed after alignment
by Dmitrij Pochepko 11 Dec '18

11 Dec '18

Hi, please review small patch for 8205421 - AARCH64: StubCodeMark should be placed after alignment This patch moves few StubCodeMark declarations after alignment code to have no alignment "nop" instructions in stub listing (like -XX:+PrintStubCode) CR: https://bugs.openjdk.java.net/browse/JDK-8205421 webrev: http://cr.openjdk.java.net/~dpochepk/8205421/webrev.01/ Testing: I checked patched build output via -XX:+PrintStubCode. Thanks, Dmitrij

3 3

RFR: AArch64: 8209415: Fix JVMTI test failure HS202
by Andrew Haley 06 Dec '18

06 Dec '18

In a moment of madness one of us (no names, no pack drill!) managed to translate from x86 __ cmpb(Address(rbcp, 0), Bytecodes::_invokestatic); __ jcc(Assembler::notEqual, L_done); to __ ldrb(rscratch1, Address(rbcp, 0)); __ cmpw(r1, Bytecodes::_invokestatic); __ br(Assembler::EQ, L_done); Two bugs in thee lines... fixed thusly. http://cr.openjdk.java.net/~aph/8209415/ OK for trunk and jdk8u ? -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. <https://www.redhat.com> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

4 3

Aarch64 port for ZGC, so far
by Stuart Monteith 04 Dec '18

04 Dec '18

Hello, I thought I'd update where I am with ZGC. The C1 code seems to be mostly working. I had an issue where ZMarkStack was stripping off the top two bits of the 64-bit addresses, which is where I've put the thread colours to avoid tags in MTE. I've added some support for C2 to the ZGC code. There are some issues, however, with the graph. As before the 64-bit Literal oops support patch is needed: http://cr.openjdk.java.net/~smonteith/oop64/webrev-20181002/ The patchset is here: http://cr.openjdk.java.net/~smonteith/zgc/webrev-20181121/ To run with ZGC enabled, you'll need to pass: -XX:+UnlockExperimentalVMOptions -XX:+UseZGC I've included a test case here: http://cr.openjdk.java.net/~smonteith/zgc/C2Examples/ Which can be executed with or without "-XX:+UseBarriersForVolatile" to reproduce two different errors. With that option I see: # Internal Error (/home/stuart/jdk/src/hotspot/share/opto/matcher.cpp:1663), pid=16859, tid=17048 # assert(C->node_arena()->contains(s->_leaf) || !has_new_node(s->_leaf)) failed: duplicating node that's already been matched and without I see: # Internal Error (/home/stuart/jdk/src/hotspot/cpu/aarch64/aarch64.ad:1438), pid=3436, tid=3503 # assert(ldst->trailing_membar() != __null) failed: expected trailing membar This is due to a combination of the graph generated in ZBarrierSetC2::make_cas_loadbarrier and apparently the memory barrier handling in aarch64.ad that Roland recently changed in "8209420: Track membars for volatile accesses so they can be properly optimized". This is easily triggered in the C2Example.java file I've linked to above, where calls to Unsafe.compareAndSwapObject provoke the issue. I'm trying to unpick the problems with the graph - I've uploaded the replay, hs_err and ideal graph xml files of runs with and without +UseBarriersForVolatile, in case someone could provide some insight. BR, Stuart

6 18

Re: [aarch64-port-dev ] Aarch64 port for ZGC, so far
by Stuart Monteith 29 Nov '18

29 Nov '18

Hello, This latest patch changes the arraycopy_prologue to pass the source as well as the destination, and for the ZGC array_copy prologue to use the source instead: http://cr.openjdk.java.net/~smonteith/zgc/webrev-20181129/ I'm running a long test with the C1 compiler, so I'll see whether that removes the rarer failures. BR, Stuart On Thu, 29 Nov 2018 at 18:01, Stuart Monteith <stuart.monteith(a)linaro.org> wrote: > > Thanks for pointing that out Ma Chunhui, > > What you suggest can't be done as ZGC isn't just a compile time > option, it is also a run-time option. You are quite right though - the > array prologue needs to take the src and dest and decide what it needs > to do. > > I'll incorporate this into the aarch64 specific code by adding the > source too the method signature and the other dependencies in a manner > that will be correct for with/without ZGC. > > This will explain some of the rarer problems I 'm seeing. > > On Thu, 29 Nov 2018 at 06:13, machunhui (C) <machunhui2(a)huawei.com> wrote: > > > > Hi, Stuart > > > > With your latest patch, It seems that Interpreter and C1 works fine on my machine and my case. But there is a crash when using C2. > > > > > > > > My Option is: -XX:+UseZGC -XX:-TieredCompilation -XX:ParallelGCThreads=1 -XX:ConcGCThreads=1 -XX:+Use64BitLiteralOops > > > > And the crash happens only when java main thread is exited, after DestroyJavaVM. > > > > > > > > The crash stack: > > > > 30 V [libjvm.so+0x121b968] ZPage::is_active() const+0xc > > > > 31 V [libjvm.so+0x123b180] ZMark::try_mark_object(ZMarkCache*, unsigned long, bool)+0x48 > > > > 32 V [libjvm.so+0x123b28c] ZMark::mark_and_follow(ZMarkCache*, ZMarkStackEntry)+0x6c > > > > 33 V [libjvm.so+0x123e6d4] bool ZMark::drain<ZMarkNoTimeout>(ZMarkStripe*, ZMarkThreadLocalStacks*, ZMarkCache*, ZMarkNoTimeout*)+0x7c > > > > > > > > The crash is because when trying to mark object, it failed to find page for the given object address, which is 0xbaadbabe. And the reason is because in StubGenerator:: generate_disjoint_copy, when trying to add load-barrier in aarch64, the barrier is wrongly added to dest, not src. > > > > So the fix is quite simple, when using ZGC, add load-barrier to src instead of dest. > > > > > > > > diff --git a/src/hotspot/cpu/aarch64/stubGenerator_aarch64.cpp b/src/hotspot/cpu/aarch64/stubGenerator_aarch64.cpp > > > > index a1fd069c7b..fc7f209d62 100644 > > > > --- a/src/hotspot/cpu/aarch64/stubGenerator_aarch64.cpp > > > > +++ b/src/hotspot/cpu/aarch64/stubGenerator_aarch64.cpp > > > > @@ -1377,7 +1377,11 @@ class StubGenerator: public StubCodeGenerator { > > > > } > > > > > > > > BarrierSetAssembler *bs = BarrierSet::barrier_set()->barrier_set_assembler(); > > > > +#if INCLUDE_ZGC > > > > + bs->arraycopy_prologue(_masm, decorators, is_oop, s, count, saved_reg); > > > > +#else > > > > bs->arraycopy_prologue(_masm, decorators, is_oop, d, count, saved_reg); > > > > +#endif > > > > > > > > if (is_oop) { > > > > // save regs before copy_memory > > > > @@ -1451,7 +1455,11 @@ class StubGenerator: public StubCodeGenerator { > > > > } > > > > > > > > BarrierSetAssembler *bs = BarrierSet::barrier_set()->barrier_set_assembler(); > > > > +#if INCLUDE_ZGC > > > > + bs->arraycopy_prologue(_masm, decorators, is_oop, s, count, saved_regs); > > > > +#else > > > > bs->arraycopy_prologue(_masm, decorators, is_oop, d, count, saved_regs); > > > > +#endif > > > > > > > > if (is_oop) { > > > > // save regs before copy_memory > > > > > > > > Thanks. > > > > > > > > -------------------------------------------------- > > 马春辉 Ma Chunhui > > Mail: machunhui2(a)huawei.com > > 2012实验室-语言虚拟机实验室 > > 2012 Laboratories-Language VM Lab,2012Labs > > > >

1 0

JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64
by ci_notify＠linaro.org 29 Nov '18

29 Nov '18

This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2018/332… ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/22 pass: 5,790; fail: 18; not run: 90 Build 1: aarch64/2018/oct/29 pass: 5,789; fail: 19; not run: 90 Build 2: aarch64/2018/nov/01 pass: 5,469; fail: 21; not run: 90 Build 3: aarch64/2018/nov/02 pass: 5,469; fail: 21; not run: 90 Build 4: aarch64/2018/nov/05 pass: 5,467; fail: 22; not run: 90 Build 5: aarch64/2018/nov/07 pass: 5,470; fail: 20; not run: 90 Build 6: aarch64/2018/nov/08 pass: 5,469; fail: 22; not run: 90 Build 7: aarch64/2018/nov/09 pass: 5,472; fail: 22; not run: 90 Build 8: aarch64/2018/nov/12 pass: 5,474; fail: 20; not run: 90 Build 9: aarch64/2018/nov/19 pass: 5,426; fail: 65; not run: 90 Build 10: aarch64/2018/nov/21 pass: 5,426; fail: 66; not run: 90 Build 11: aarch64/2018/nov/23 pass: 5,426; fail: 68; not run: 90 Build 12: aarch64/2018/nov/26 pass: 5,427; fail: 67; not run: 90 Build 13: aarch64/2018/nov/28 pass: 5,430; fail: 66; not run: 90 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/22 pass: 8,497; fail: 685; error: 29 Build 1: aarch64/2018/oct/29 pass: 8,538; fail: 653; error: 25 Build 2: aarch64/2018/nov/01 pass: 8,512; fail: 673; error: 31 Build 3: aarch64/2018/nov/02 pass: 8,517; fail: 673; error: 29 Build 4: aarch64/2018/nov/05 pass: 8,506; fail: 684; error: 29 Build 5: aarch64/2018/nov/07 pass: 8,526; fail: 664; error: 31 Build 6: aarch64/2018/nov/08 pass: 8,512; fail: 678; error: 31 Build 7: aarch64/2018/nov/09 pass: 8,516; fail: 681; error: 27 Build 8: aarch64/2018/nov/12 pass: 8,507; fail: 685; error: 34 Build 9: aarch64/2018/nov/19 pass: 8,520; fail: 682; error: 26 Build 10: aarch64/2018/nov/21 pass: 8,516; fail: 689; error: 31 Build 11: aarch64/2018/nov/23 pass: 8,541; fail: 672; error: 24 Build 12: aarch64/2018/nov/26 pass: 8,517; fail: 691; error: 29 Build 13: aarch64/2018/nov/28 pass: 8,535; fail: 685; error: 20 6 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/22 pass: 3,971; fail: 5 Build 1: aarch64/2018/oct/29 pass: 3,972; fail: 5 Build 2: aarch64/2018/nov/01 pass: 3,973; fail: 5 Build 3: aarch64/2018/nov/02 pass: 3,974; fail: 4 Build 4: aarch64/2018/nov/05 pass: 3,973; fail: 5 Build 5: aarch64/2018/nov/07 pass: 3,974; fail: 5 Build 6: aarch64/2018/nov/08 pass: 3,974; fail: 5 Build 7: aarch64/2018/nov/09 pass: 3,977; fail: 4 Build 8: aarch64/2018/nov/12 pass: 3,979; fail: 5 Build 9: aarch64/2018/nov/19 pass: 3,980; fail: 4 Build 10: aarch64/2018/nov/21 pass: 3,982; fail: 4 Build 11: aarch64/2018/nov/23 pass: 3,983; fail: 4 Build 12: aarch64/2018/nov/26 pass: 3,983; fail: 4 Build 13: aarch64/2018/nov/28 pass: 3,987; fail: 4 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.75x Relative performance: Server critical-jOPS (nc): 8.77x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 201.64 Server 201.64 / Server 2014-04-01 (71.00): 2.84x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2018-10-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/295/results/ 2018-10-30 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/302/results/ 2018-11-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/305/results/ 2018-11-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/306/results/ 2018-11-06 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/309/results/ 2018-11-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/311/results/ 2018-11-09 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/312/results/ 2018-11-10 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/313/results/ 2018-11-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/316/results/ 2018-11-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/323/results/ 2018-11-22 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/325/results/ 2018-11-24 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/327/results/ 2018-11-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/330/results/ 2018-11-29 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/332/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/

1 0

JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64
by ci_notify＠linaro.org 27 Nov '18

27 Nov '18

This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2018/330… ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/22 pass: 5,790; fail: 18; not run: 90 Build 1: aarch64/2018/oct/29 pass: 5,789; fail: 19; not run: 90 Build 2: aarch64/2018/nov/01 pass: 5,469; fail: 21; not run: 90 Build 3: aarch64/2018/nov/02 pass: 5,469; fail: 21; not run: 90 Build 4: aarch64/2018/nov/05 pass: 5,467; fail: 22; not run: 90 Build 5: aarch64/2018/nov/07 pass: 5,470; fail: 20; not run: 90 Build 6: aarch64/2018/nov/08 pass: 5,469; fail: 22; not run: 90 Build 7: aarch64/2018/nov/09 pass: 5,472; fail: 22; not run: 90 Build 8: aarch64/2018/nov/12 pass: 5,474; fail: 20; not run: 90 Build 9: aarch64/2018/nov/19 pass: 5,426; fail: 65; not run: 90 Build 10: aarch64/2018/nov/21 pass: 5,426; fail: 66; not run: 90 Build 11: aarch64/2018/nov/23 pass: 5,426; fail: 68; not run: 90 Build 12: aarch64/2018/nov/26 pass: 5,427; fail: 67; not run: 90 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/22 pass: 8,497; fail: 685; error: 29 Build 1: aarch64/2018/oct/29 pass: 8,538; fail: 653; error: 25 Build 2: aarch64/2018/nov/01 pass: 8,512; fail: 673; error: 31 Build 3: aarch64/2018/nov/02 pass: 8,517; fail: 673; error: 29 Build 4: aarch64/2018/nov/05 pass: 8,506; fail: 684; error: 29 Build 5: aarch64/2018/nov/07 pass: 8,526; fail: 664; error: 31 Build 6: aarch64/2018/nov/08 pass: 8,512; fail: 678; error: 31 Build 7: aarch64/2018/nov/09 pass: 8,516; fail: 681; error: 27 Build 8: aarch64/2018/nov/12 pass: 8,507; fail: 685; error: 34 Build 9: aarch64/2018/nov/19 pass: 8,520; fail: 682; error: 26 Build 10: aarch64/2018/nov/21 pass: 8,516; fail: 689; error: 31 Build 11: aarch64/2018/nov/23 pass: 8,541; fail: 672; error: 24 Build 12: aarch64/2018/nov/26 pass: 8,517; fail: 691; error: 29 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/22 pass: 3,971; fail: 5 Build 1: aarch64/2018/oct/29 pass: 3,972; fail: 5 Build 2: aarch64/2018/nov/01 pass: 3,973; fail: 5 Build 3: aarch64/2018/nov/02 pass: 3,974; fail: 4 Build 4: aarch64/2018/nov/05 pass: 3,973; fail: 5 Build 5: aarch64/2018/nov/07 pass: 3,974; fail: 5 Build 6: aarch64/2018/nov/08 pass: 3,974; fail: 5 Build 7: aarch64/2018/nov/09 pass: 3,977; fail: 4 Build 8: aarch64/2018/nov/12 pass: 3,979; fail: 5 Build 9: aarch64/2018/nov/19 pass: 3,980; fail: 4 Build 10: aarch64/2018/nov/21 pass: 3,982; fail: 4 Build 11: aarch64/2018/nov/23 pass: 3,983; fail: 4 Build 12: aarch64/2018/nov/26 pass: 3,983; fail: 4 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.75x Relative performance: Server critical-jOPS (nc): 9.24x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 207.57 Server 207.57 / Server 2014-04-01 (71.00): 2.92x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2018-10-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/295/results/ 2018-10-30 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/302/results/ 2018-11-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/305/results/ 2018-11-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/306/results/ 2018-11-06 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/309/results/ 2018-11-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/311/results/ 2018-11-09 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/312/results/ 2018-11-10 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/313/results/ 2018-11-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/316/results/ 2018-11-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/323/results/ 2018-11-22 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/325/results/ 2018-11-24 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/327/results/ 2018-11-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/330/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/

1 0