December 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

RFR: RFR: Bulk integration shenandoah/jdk8u -> aarch64-port/jdk8u-shenandoah 2018-12-13
by Roman Kennke 29 Apr '19

29 Apr '19

Please review the following proposed changes: This integrates changes from shenandoah/jdk8u into aarch64-port/jdk8u-shenandoah repository, reaching back to September 2018. It's bugfixes, improvements and new features that have been originally done in Shenandoah dev repo, and then backported to Shenandoah JDK8u repo and tested there for a while too. List of changes: http://cr.openjdk.java.net/~rkennke/jdk8u-shenandoah-integration-2018-12-13… Webrev showing only shared-changes: http://cr.openjdk.java.net/~rkennke/jdk8u-shenandoah-integration-2018-12-13… Full webrev: http://cr.openjdk.java.net/~rkennke/jdk8u-shenandoah-integration-2018-12-13… Thanks, Roman

5 15

RFR(S): 8214922: Add vectorization support for fmin/fmax
by Pengfei Li (Arm Technology China) 12 Mar '19

12 Mar '19

Hi, JBS: https://bugs.openjdk.java.net/browse/JDK-8214922 Webrev: http://cr.openjdk.java.net/~pli/rfr/8214922/webrev.00/ This is the vectorization support of floating-point min/max. Both vector binary operations and reduction operations are added. For C2 vectorization nodes, I see similar code in project panama (http://hg.openjdk.java.net/panama/dev/) So to reduce duplicate work and help future code merge between jdk/jdk and panama/dev, most of the hotspot shared codes in this patch are copied from panama/dev. I still made one thing different from panama code. It is that for reduction min/max, scalar operations are transformed only when the number of lanes in the vector is greater than 2. I did this as on some architectures, such as AArch64, there is no reduction min/max for 2 floats or 2 doubles. We can surely add a fallback matching rule in ad file for these cases just like reduce_add2F or reduce_add2D in aarch64.ad. But based on my test[1], the fallback implementations show worse performance than the original scalar version. Please let me know if you agree with this change or not. [1] http://cr.openjdk.java.net/~pli/rfr/8214922/TestSIMDFpMinMax.java -- Thanks, Pengfei

6 22

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: AArch64: jtreg test vmTestbase/nsk/jvmti/PopFrame/popframe005 segfaults
by Nick Gasson (Arm Technology China) 07 Jan '19

07 Jan '19

Hi, Please review a one-line fix to prevent a JVMTI PopFrame crash on AArch64: Bug: https://bugs.openjdk.java.net/browse/JDK-8215951 Webrev: http://cr.openjdk.java.net/~njian/8215951/webrev.0/ This jtreg test started intermittently failing on AArch64 with a segfault after 8215425: http://hg.openjdk.java.net/jdk/jdk/rev/1e213c37befa (There is a full crash log attached to the bug.) The faulting instruction is the load of the dispatch table pointer from rdispatch (x21) in InterpreterMacroAssembler::dispatch_base. 0x0000ffff8c939ab8: ldrb w8, [x22, #0]! 0x0000ffff8c939abc: add w9, w8, #0x900 0x0000ffff8c939ac0: ldr x9, [x21, w9, uxtw #3] <------ 0x0000ffff8c939ac4: br x9 When deoptimising a frame that has a JVMTI PopFrame event pending, vframeArrayElement::unpack_on_stack will set the return PC of the deoptimised frame to the the interpreter entry point remove_activation_preserving_args_entry. After the PopFrame handling this calls dispatch_next to dispatch the next opcode, but at this point rdispatch may not have been initialised to point at the dispatch table. Fix by calling get_dispatch() to initialise rdispatch at the same time as the rest of the interpreter state is restored in remove_activation_preserving_args_entry. I guess this has always been a potential problem, but adding the prints in the changeset above changed the timing of when a method was compiled and exposed it? Thanks, Nick

4 8

[RFR] 8u191 Upstream Sync
by Andrew Hughes 07 Jan '19

07 Jan '19

Hi, This webrev brings jdk8u191-b12 (the upstream version) into the aarch64/shenandoah-jdk8u repositories, tagging the result as aarch64-shenandoah-jdk8u191-b13. https://cr.openjdk.java.net/~andrew/shenandoah-8/u191.upstream/ To illustrate the actual changes, the merge changesets for each repository are also included: https://cr.openjdk.java.net/~andrew/shenandoah-8/u191.upstream/corba/merge.… https://cr.openjdk.java.net/~andrew/shenandoah-8/u191.upstream/jaxp/merge.c… https://cr.openjdk.java.net/~andrew/shenandoah-8/u191.upstream/jaxws/merge.… https://cr.openjdk.java.net/~andrew/shenandoah-8/u191.upstream/jdk/merge.ch… https://cr.openjdk.java.net/~andrew/shenandoah-8/u191.upstream/hotspot/merg… https://cr.openjdk.java.net/~andrew/shenandoah-8/u191.upstream/langtools/me… https://cr.openjdk.java.net/~andrew/shenandoah-8/u191.upstream/nashorn/merg… https://cr.openjdk.java.net/~andrew/shenandoah-8/u191.upstream/root/merge.c… Changes in aarch64-shenandoah-jdk8u191-b13: - S8033251: Use DWARF debug symbols for Linux 32-bit as default - S8206916: Remove jdk8u181-b31 tag from jdk8u181/corba repo - S8206916: Remove jdk8u181-b31 tag from jdk8u181/hotspot repo - S8206916: Remove jdk8u181-b31 tag from jdk8u181/jaxp repo - S8206916: Remove jdk8u181-b31 tag from jdk8u181/jaxws repo - S8206916: Remove jdk8u181-b31 tag from jdk8u181/jdk repo - S8206916: Remove jdk8u181-b31 tag from jdk8u181/langtools repo - S8206916: Remove jdk8u181-b31 tag from jdk8u181/nashorn repo - S8206916: Remove jdk8u181-b31 tag from jdk8u181 repo - S8209415: Fix JVMTI test failure HS202 (already pushed after last tag) - S8210431: Complete backport of libpng 1.6.35 TPRM The many duplicates merged that were already in the aarch64/jdk8u-shenandoah repository have been removed from the list above. diffstat for root b/.hgtags | 32 ++++++++++++++++ b/THIRD_PARTY_README | 98 +++++++++++++++++++++++++++++++-------------------- 2 files changed, 92 insertions(+), 38 deletions(-) diffstat for corba b/.hgtags | 65 +++++++++++++++++++++++++++++++++ b/THIRD_PARTY_README | 98 +++++++++++++++++++++++++++++++-------------------- 2 files changed, 125 insertions(+), 38 deletions(-) diffstat for jaxp b/.hgtags | 44 ++++++++++++++++++++++ b/THIRD_PARTY_README | 98 +++++++++++++++++++++++++++++++-------------------- 2 files changed, 104 insertions(+), 38 deletions(-) diffstat for jaxws b/.hgtags | 64 +++++++++++++++++++++++++++++++++ b/THIRD_PARTY_README | 98 +++++++++++++++++++++++++++++++-------------------- 2 files changed, 124 insertions(+), 38 deletions(-) diffstat for langtools b/.hgtags | 44 ++++++++++++++++++++++ b/THIRD_PARTY_README | 98 +++++++++++++++++++++++++++++++-------------------- 2 files changed, 104 insertions(+), 38 deletions(-) diffstat for nashorn b/.hgtags | 65 +++++++++++++++++++++++++++++++++ b/THIRD_PARTY_README | 98 +++++++++++++++++++++++++++++++-------------------- 2 files changed, 125 insertions(+), 38 deletions(-) diffstat for jdk b/.hgtags | 32 ++ b/THIRD_PARTY_README | 98 +++--- b/test/javax/sound/midi/Gervill/RiffReaderWriter/Skip.java | 22 + b/test/lib/testlibrary/jdk/testlibrary/InMemoryJavaCompiler.java | 154 ++++++++++ b/test/lib/testlibrary/jdk/testlibrary/JarUtils.java | 106 ++++++ b/test/sun/rmi/transport/tcp/DisableRMIOverHttp/DisableRMIOverHTTPTest.java | 2 6 files changed, 370 insertions(+), 44 deletions(-) diffstat for hotspot b/.hgtags | 32 +++++++++++++ b/THIRD_PARTY_README | 98 ++++++++++++++++++++++++---------------- b/make/linux/makefiles/gcc.make | 42 +---------------- 3 files changed, 95 insertions(+), 77 deletions(-) Ok to push? Thanks, -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) Web Site: http://fuseyism.com Twitter: https://twitter.com/gnu_andrew_java PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222

2 4

RFR: 8215202: AArch64: jtreg test test/jdk/sun/nio/cs/FindEncoderBugs.java fails
by Nick Gasson (Arm Technology China) 30 Dec '18

30 Dec '18

Hi, Please help me review this patch to fix an issue with the ISO-8859-1 encoder intrinsic on AArch64 (nio-dev CC-ed due to test change). Webrev: http://cr.openjdk.java.net/~njian/8215202/webrev.0/ Bug: https://bugs.openjdk.java.net/browse/JDK-8215202 The jtreg test test/jdk/sun/nio/cs/FindEncoderBugs.java fails with the following error on AArch64 with compilation: Buffer overrun: ISO-8859-1 "\u8a8e"[0/1] => UNMAPPABLE[1] ""[0/19] -114 failures=1 Passed = 223410156, failed = 10000 STDERR: java.lang.AssertionError: Some tests failed at FindEncoderBugs.main(FindEncoderBugs.java:526) The problem is caused by the encoder function for the ISO-8859-1 character set writing one extra character to the output array when it encounters a character it can't encode. This is implemented as an intrinsic on AArch64, but the intrinsic doesn't exactly match the original Java code in ISO_8859_1.java: @HotSpotIntrinsicCandidate private static int implEncodeISOArray(char[] sa, int sp, byte[] da, int dp, int len) { int i = 0; for (; i < len; i++) { char c = sa[sp++]; if (c > '\u00FF') // (1) break; da[dp++] = (byte)c; // (2) } return i; } In the intrinsic code statements (1) and (2) are swapped. Also Extended the FindEncoderBugs test so that it hits all cases in the intrinsic assembly. Currently only the final NEXT_1 section is covered by this test. Thanks, Nick

3 6

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

29 Dec '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/362… ------------------------------------------------------------------------------- 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/nov/23 pass: 5,426; fail: 68; not run: 90 Build 1: aarch64/2018/nov/26 pass: 5,427; fail: 67; not run: 90 Build 2: aarch64/2018/nov/28 pass: 5,430; fail: 66; not run: 90 Build 3: aarch64/2018/nov/30 pass: 5,431; fail: 65; not run: 91 Build 4: aarch64/2018/dec/03 pass: 5,432; fail: 66; not run: 91 Build 5: aarch64/2018/dec/05 pass: 5,435; fail: 65; not run: 91 Build 6: aarch64/2018/dec/07 pass: 5,429; fail: 65; not run: 93 Build 7: aarch64/2018/dec/10 pass: 5,475; fail: 19; not run: 93 Build 8: aarch64/2018/dec/12 pass: 5,546; fail: 23; error: 2; not run: 93 Build 9: aarch64/2018/dec/17 pass: 5,550; fail: 22; error: 1; not run: 93 Build 10: aarch64/2018/dec/19 pass: 5,550; fail: 22; error: 1; not run: 93 Build 11: aarch64/2018/dec/21 pass: 5,554; fail: 20; error: 2; not run: 93 Build 12: aarch64/2018/dec/24 pass: 5,553; fail: 22; error: 1; not run: 93 Build 13: aarch64/2018/dec/26 pass: 5,555; fail: 20; error: 1; not run: 93 Build 14: aarch64/2018/dec/28 pass: 5,554; fail: 21; error: 1; not run: 93 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/nov/23 pass: 8,541; fail: 672; error: 24 Build 1: aarch64/2018/nov/26 pass: 8,517; fail: 691; error: 29 Build 2: aarch64/2018/nov/28 pass: 8,535; fail: 685; error: 20 Build 3: aarch64/2018/nov/30 pass: 8,524; fail: 693; error: 28 Build 4: aarch64/2018/dec/03 pass: 8,525; fail: 696; error: 25 Build 5: aarch64/2018/dec/05 pass: 8,546; fail: 681; error: 20 Build 6: aarch64/2018/dec/07 pass: 8,558; fail: 677; error: 29 Build 7: aarch64/2018/dec/10 pass: 8,552; fail: 694; error: 27 Build 8: aarch64/2018/dec/12 pass: 8,561; fail: 680; error: 31 Build 9: aarch64/2018/dec/17 pass: 8,564; fail: 692; error: 22 Build 10: aarch64/2018/dec/19 pass: 8,505; fail: 742; error: 31 Build 11: aarch64/2018/dec/21 pass: 8,567; fail: 686; error: 30 Build 12: aarch64/2018/dec/24 pass: 8,570; fail: 692; error: 25 Build 13: aarch64/2018/dec/26 pass: 8,592; fail: 665; error: 30 Build 14: aarch64/2018/dec/28 pass: 8,576; fail: 684; error: 27 4 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/nov/23 pass: 3,983; fail: 4 Build 1: aarch64/2018/nov/26 pass: 3,983; fail: 4 Build 2: aarch64/2018/nov/28 pass: 3,987; fail: 4 Build 3: aarch64/2018/nov/30 pass: 3,989; fail: 4 Build 4: aarch64/2018/dec/03 pass: 3,989; fail: 4 Build 5: aarch64/2018/dec/05 pass: 3,994; fail: 4 Build 6: aarch64/2018/dec/07 pass: 3,995; fail: 4 Build 7: aarch64/2018/dec/10 pass: 3,995; fail: 4 Build 8: aarch64/2018/dec/12 pass: 3,996; fail: 4 Build 9: aarch64/2018/dec/17 pass: 3,996; fail: 4 Build 10: aarch64/2018/dec/19 pass: 3,997; fail: 4 Build 11: aarch64/2018/dec/21 pass: 3,996; fail: 4 Build 12: aarch64/2018/dec/24 pass: 3,996; fail: 4 Build 13: aarch64/2018/dec/26 pass: 3,996; fail: 4 Build 14: aarch64/2018/dec/28 pass: 3,996; 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.71x Relative performance: Server critical-jOPS (nc): 8.74x 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-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/ 2018-12-01 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/334/results/ 2018-12-04 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/337/results/ 2018-12-06 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/339/results/ 2018-12-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/341/results/ 2018-12-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/344/results/ 2018-12-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/346/results/ 2018-12-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/351/results/ 2018-12-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/353/results/ 2018-12-22 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/355/results/ 2018-12-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/358/results/ 2018-12-27 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/360/results/ 2018-12-29 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/362/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 Dec '18

27 Dec '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/360… ------------------------------------------------------------------------------- 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/nov/21 pass: 5,426; fail: 66; not run: 90 Build 1: aarch64/2018/nov/23 pass: 5,426; fail: 68; not run: 90 Build 2: aarch64/2018/nov/26 pass: 5,427; fail: 67; not run: 90 Build 3: aarch64/2018/nov/28 pass: 5,430; fail: 66; not run: 90 Build 4: aarch64/2018/nov/30 pass: 5,431; fail: 65; not run: 91 Build 5: aarch64/2018/dec/03 pass: 5,432; fail: 66; not run: 91 Build 6: aarch64/2018/dec/05 pass: 5,435; fail: 65; not run: 91 Build 7: aarch64/2018/dec/07 pass: 5,429; fail: 65; not run: 93 Build 8: aarch64/2018/dec/10 pass: 5,475; fail: 19; not run: 93 Build 9: aarch64/2018/dec/12 pass: 5,546; fail: 23; error: 2; not run: 93 Build 10: aarch64/2018/dec/17 pass: 5,550; fail: 22; error: 1; not run: 93 Build 11: aarch64/2018/dec/19 pass: 5,550; fail: 22; error: 1; not run: 93 Build 12: aarch64/2018/dec/21 pass: 5,554; fail: 20; error: 2; not run: 93 Build 13: aarch64/2018/dec/24 pass: 5,553; fail: 22; error: 1; not run: 93 Build 14: aarch64/2018/dec/26 pass: 5,555; fail: 20; error: 1; not run: 93 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/nov/21 pass: 8,516; fail: 689; error: 31 Build 1: aarch64/2018/nov/23 pass: 8,541; fail: 672; error: 24 Build 2: aarch64/2018/nov/26 pass: 8,517; fail: 691; error: 29 Build 3: aarch64/2018/nov/28 pass: 8,535; fail: 685; error: 20 Build 4: aarch64/2018/nov/30 pass: 8,524; fail: 693; error: 28 Build 5: aarch64/2018/dec/03 pass: 8,525; fail: 696; error: 25 Build 6: aarch64/2018/dec/05 pass: 8,546; fail: 681; error: 20 Build 7: aarch64/2018/dec/07 pass: 8,558; fail: 677; error: 29 Build 8: aarch64/2018/dec/10 pass: 8,552; fail: 694; error: 27 Build 9: aarch64/2018/dec/12 pass: 8,561; fail: 680; error: 31 Build 10: aarch64/2018/dec/17 pass: 8,564; fail: 692; error: 22 Build 11: aarch64/2018/dec/19 pass: 8,505; fail: 742; error: 31 Build 12: aarch64/2018/dec/21 pass: 8,567; fail: 686; error: 30 Build 13: aarch64/2018/dec/24 pass: 8,570; fail: 692; error: 25 Build 14: aarch64/2018/dec/26 pass: 8,592; fail: 665; error: 30 3 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/nov/21 pass: 3,982; fail: 4 Build 1: aarch64/2018/nov/23 pass: 3,983; fail: 4 Build 2: aarch64/2018/nov/26 pass: 3,983; fail: 4 Build 3: aarch64/2018/nov/28 pass: 3,987; fail: 4 Build 4: aarch64/2018/nov/30 pass: 3,989; fail: 4 Build 5: aarch64/2018/dec/03 pass: 3,989; fail: 4 Build 6: aarch64/2018/dec/05 pass: 3,994; fail: 4 Build 7: aarch64/2018/dec/07 pass: 3,995; fail: 4 Build 8: aarch64/2018/dec/10 pass: 3,995; fail: 4 Build 9: aarch64/2018/dec/12 pass: 3,996; fail: 4 Build 10: aarch64/2018/dec/17 pass: 3,996; fail: 4 Build 11: aarch64/2018/dec/19 pass: 3,997; fail: 4 Build 12: aarch64/2018/dec/21 pass: 3,996; fail: 4 Build 13: aarch64/2018/dec/24 pass: 3,996; fail: 4 Build 14: aarch64/2018/dec/26 pass: 3,996; 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.80x Relative performance: Server critical-jOPS (nc): 8.58x 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: 204.57 Server 204.57 / Server 2014-04-01 (71.00): 2.88x 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-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/ 2018-12-01 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/334/results/ 2018-12-04 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/337/results/ 2018-12-06 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/339/results/ 2018-12-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/341/results/ 2018-12-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/344/results/ 2018-12-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/346/results/ 2018-12-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/351/results/ 2018-12-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/353/results/ 2018-12-22 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/355/results/ 2018-12-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/358/results/ 2018-12-27 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/360/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/

1 0