March 2018 - aarch64-port-dev

RFR [sh/8u]: Revert accidental OpSpinWait matching
by Aleksey Shipilev 30 Apr '18

30 Apr '18

We have a weird difference between our sh/jdk8 development repo and aarch64-port-jdk8u-shenandoah integration forest: it has a little branch that "matches" OpSpinWait, even though there is no such node in 8u at all -- that feature came in JDK 9. This had accidentally leaked during previous merges. So, we want to push this to aarch64-port/jdk8u-shenandoah: diff -r 966a10251cb4 src/share/vm/adlc/formssel.cpp --- a/src/share/vm/adlc/formssel.cpp Wed Mar 21 20:00:58 2018 +0000 +++ b/src/share/vm/adlc/formssel.cpp Thu Mar 22 12:03:44 2018 +0100 @@ -4066,8 +4066,7 @@ !strcmp(_opType,"StoreFence") || !strcmp(_opType,"MemBarVolatile") || !strcmp(_opType,"MemBarCPUOrder") || - !strcmp(_opType,"MemBarStoreStore") || - !strcmp(_opType, "OnSpinWait"); + !strcmp(_opType,"MemBarStoreStore"); } bool MatchRule::is_ideal_loadPC() const { Testing: x86_64 build, hotspot_gc_shenandoah Thanks, -Aleksey

2 3

RFD: AOT for AArch64
by Andrew Haley 11 Apr '18

11 Apr '18

How to build it: Check out jdk-hs. Apply http://cr.openjdk.java.net/~aph/jaotc/jdk-hs-1/ to that checkout then build OpenJDK images. Then $ git checkout https://github.com/theRealAph/graal.git $ cd graal $ git branch aarch64-branch-overflows MAKE SURE that JAVA_HOME is pointing at the jdk-hs you just built: $ export JAVA_HOME=/local/jdk-hs/build/linux-aarch64-normal-server-release/images/jdk/ Follow the "Building Graal" instructions at https://github.com/theRealAph/graal/tree/aarch64-branch-overflows/compiler My graal is in /local/graal/ and my jdk-hs is in /local/jdk-hs/. To run jaotc, I do something like this: /local/jdk-hs/build/linux-aarch64-normal-server-release/images/jdk/bin/jaotc \ -J--module-path=/local/graal/graal/sdk/mxbuild/modules/org.graalvm.graal_sdk.jar:/local/graal/graal/truffle/mxbuild/modules/com.oracle.truffle.truffle_api.jar \ -J--upgrade-module-path=/local/graal/graal/compiler/mxbuild/modules/jdk.internal.vm.compiler.jar \ myjar.jar --output myjar.so Note that the "-J" commands point jaotc at the version of Graal you've just built rather than OpenJDK's built-in version of Graal. Enjoy. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. <https://www.redhat.com> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671

8 42

RFR: 8187472 - AARCH64: array_equals intrinsic doesn't use prefetch for large arrays
by Dmitrij Pochepko 06 Apr '18

06 Apr '18

Hi all, please review patch for JDK-8187472 - AARCH64: array_equals intrinsic doesn't use prefetch for large arrays this patch adds logic with prefetch instruction usage, which is helping most of CPUs. It also introduce 2 ways of loading data: via loading into general-purpose registers and via SIMD registers(controlled by newly introduced vm key: UseSIMDForArrayEquals. I've measured performance on few CPUs (ThunderX, ThunderX2(not yet released), Cortex A53, Cortex A73) and arranged defaults based on measurement results(so, SIMD is default for everything except ThunderX and A53. Also, prefetch instruction slows down A73 - I've disabled it there). In general, this patch changes very short arrays handling(performing 8-byte read instead of few smaller reads, using the fact of 8-byte alignment) and jumping into stub with large 64-byte read loop for larger arrays). Measurements(measured array length 7,64,128,256,512,1024,100000. Improvement in %. 80% improvement means that new version is 80% faster, i.e. 5 times.): ThunderX: 2%, -4%, 0%, 2%, 32%, 55%, 80% ThunderX2: 0%, -3%, 17%, 19%, 29%, 31%, 47% Cortex A53@533MHz: 8%, -1%, -2%, 4%, 6%, 5%, 3% Cortex A73@903MHz: 8%, -3%, 0%, 7%, 8%, 9%, 8% Note: medium sizes are a bit slower because of additional branch added(which checks size and jumps to stub). Note2: Cortex CPUs were downclocked to have stable frequency because of overheat on device I was using(frequency was randomly jumping producing unstable results otherwise), so, results might be a bit different on devices with higher frequency. webrev: http://cr.openjdk.java.net/~dpochepk/8187472/webrev.07/ CR: https://bugs.openjdk.java.net/browse/JDK-8187472 Testing: I've run all hotspot jtreg tests with and without patch on aarch64 and found no new failures Benchmark: http://cr.openjdk.java.net/~dpochepk/8187472/webrev.07/ArrayEqualsBench.java Thanks, Dmitrij

5 9

How to migrate hs17's LIR_Assembler::emit_exception_handler to hs25?
by Leslie Zhai 01 Apr '18

01 Apr '18

Hi HotSpot compiler developers, I am new to HotSpot, and trying to migrate hs17 to hs25, but JDK-6919934 changed: int LIR_Assembler::emit_exception_handler() { // if the last instruction is a call (typically to do a throw which // is coming at the end after block reordering) the return address // must still point into the code area in order to avoid assertion // failures when searching for the corresponding bci => add a nop // (was bug 5/14/1999 - gri) __ nop(); // generate code for exception handler address handler_base = __ start_a_stub(exception_handler_size); if (handler_base == NULL) { // not enough space left for the handler bailout("exception handler overflow"); return -1; } int offset = code_offset(); // if the method does not have an exception handler, then there is // no reason to search for one if (compilation()->has_exception_handlers() || compilation()->env()->jvmti_can_post_on_exceptions()) { // the exception oop and pc are in rax, and rdx // no other registers need to be preserved, so invalidate them __ invalidate_registers(false, true, true, false, true, true); // check that there is really an exception __ verify_not_null_oop(rax); // search an exception handler (rax: exception oop, rdx: throwing pc) __ call(RuntimeAddress(Runtime1::entry_for(Runtime1::handle_exception_nofpu_id))); // if the call returns here, then the exception handler for particular // exception doesn't exist -> unwind activation and forward exception to caller } // the exception oop is in rax, // no other registers need to be preserved, so invalidate them __ invalidate_registers(false, true, true, true, true, true); // check that there is really an exception __ verify_not_null_oop(rax); // unlock the receiver/klass if necessary // rax,: exception ciMethod* method = compilation()->method(); if (method->is_synchronized() && GenerateSynchronizationCode) { monitorexit(FrameMap::rbx_oop_opr, FrameMap::rcx_opr, SYNC_header, 0, rax); } // unwind activation and forward exception to caller // rax,: exception __ jump(RuntimeAddress(Runtime1::entry_for(Runtime1::unwind_exception_id))); assert(code_offset() - offset <= exception_handler_size, "overflow"); __ end_a_stub(); return offset; } To: int LIR_Assembler::emit_exception_handler() { // if the last instruction is a call (typically to do a throw which // is coming at the end after block reordering) the return address // must still point into the code area in order to avoid assertion // failures when searching for the corresponding bci => add a nop // (was bug 5/14/1999 - gri) __ nop(); // generate code for exception handler address handler_base = __ start_a_stub(exception_handler_size); if (handler_base == NULL) { // not enough space left for the handler bailout("exception handler overflow"); return -1; } int offset = code_offset(); // the exception oop and pc are in rax, and rdx // no other registers need to be preserved, so invalidate them __ invalidate_registers(false, true, true, false, true, true); // check that there is really an exception __ verify_not_null_oop(rax); // search an exception handler (rax: exception oop, rdx: throwing pc) __ call(RuntimeAddress(Runtime1::entry_for(Runtime1::handle_exception_nofpu_id))); __ stop("should not reach here"); assert(code_offset() - offset <= exception_handler_size, "overflow"); __ end_a_stub(); return offset; } I have no idea how to check whether or not the Java method have an exception handler *without* the `compilation()->has_exception_handlers()` condition. And after JDK-6939930 and JDK-7012914, it separated `unwind` handler from `exception` handler, added `LIR_Assembler::emit_unwind_handler` and `handle_exception_from_callee` StubID: int LIR_Assembler::emit_exception_handler() { // if the last instruction is a call (typically to do a throw which // is coming at the end after block reordering) the return address // must still point into the code area in order to avoid assertion // failures when searching for the corresponding bci => add a nop // (was bug 5/14/1999 - gri) __ nop(); // generate code for exception handler address handler_base = __ start_a_stub(exception_handler_size()); if (handler_base == NULL) { // not enough space left for the handler bailout("exception handler overflow"); return -1; } int offset = code_offset(); // the exception oop and pc are in rax, and rdx // no other registers need to be preserved, so invalidate them __ invalidate_registers(false, true, true, false, true, true); // check that there is really an exception __ verify_not_null_oop(rax); // search an exception handler (rax: exception oop, rdx: throwing pc) __ call(RuntimeAddress(Runtime1::entry_for(Runtime1::handle_exception_from_callee_id))); __ should_not_reach_here(); guarantee(code_offset() - offset <= exception_handler_size(), "overflow"); __ end_a_stub(); return offset; } How to migrate `if (compilation()->has_exception_handlers()) { } else { }` in `Runtime1::generate_handle_exception` or `Runtime1::generate_unwind_exception` be equivalent for hs25 or even jdk11? My workaround is override `generate_handle_exception`: diff -r 33a61051088d src/share/vm/c1/c1_Runtime1.hpp --- a/src/share/vm/c1/c1_Runtime1.hpp Sat Mar 24 12:18:54 2018 +0800 +++ b/src/share/vm/c1/c1_Runtime1.hpp Tue Mar 27 23:32:54 2018 +0800 @@ -127,6 +127,7 @@ static OopMapSet* generate_code_for(StubID id, StubAssembler* sasm); static OopMapSet* generate_exception_throw(StubAssembler* sasm, address target, bool has_argument); static OopMapSet* generate_handle_exception(StubID id, StubAssembler* sasm); + static OopMapSet* generate_handle_exception(StubAssembler *sasm, OopMapSet* oop_maps, OopMap* oop_map, bool save_fpu_registers); static void generate_unwind_exception(StubAssembler *sasm); static OopMapSet* generate_patching(StubAssembler* sasm, address target); Then reuse hs17's `LIR_Assembler::emit_exception_handler`, `Runtime1::generate_handle_exception`, `Runtime1::generate_code_for`... in hs25, but it is monkey patch... not easy to merge upstream. Please share your porting experience, and give me some advice, thanks a lot! -- Regards, Leslie Zhai

2 2

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

31 Mar '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/090… ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/jan/07 pass: 7,593; fail: 726; error: 20 Build 1: aarch64/2018/jan/11 pass: 7,585; fail: 729; error: 25 Build 2: aarch64/2018/jan/13 pass: 7,591; fail: 726; error: 22 Build 3: aarch64/2018/jan/19 pass: 7,598; fail: 720; error: 23 Build 4: aarch64/2018/jan/21 pass: 7,595; fail: 717; error: 29 Build 5: aarch64/2018/feb/21 pass: 7,623; fail: 749; error: 27 Build 6: aarch64/2018/mar/15 pass: 7,693; fail: 692; error: 20 Build 7: aarch64/2018/mar/17 pass: 7,654; fail: 727; error: 24 Build 8: aarch64/2018/mar/19 pass: 7,657; fail: 722; error: 26 Build 9: aarch64/2018/mar/21 pass: 7,652; fail: 732; error: 21 Build 10: aarch64/2018/mar/23 pass: 7,629; fail: 752; error: 24 Build 11: aarch64/2018/mar/25 pass: 7,778; fail: 629; error: 20 Build 12: aarch64/2018/mar/27 pass: 7,773; fail: 634; error: 20 Build 13: aarch64/2018/mar/29 pass: 7,790; fail: 617; error: 20 Build 14: aarch64/2018/mar/31 pass: 7,766; fail: 643; error: 18 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/jan/07 pass: 3,821; fail: 5; error: 4 Build 1: aarch64/2018/jan/11 pass: 3,824; fail: 5; error: 1 Build 2: aarch64/2018/jan/13 pass: 3,821; fail: 5; error: 4 Build 3: aarch64/2018/jan/19 pass: 3,825; fail: 5; error: 5 Build 4: aarch64/2018/jan/21 pass: 3,824; fail: 5; error: 6 Build 5: aarch64/2018/feb/21 pass: 3,831; fail: 6; error: 9 Build 6: aarch64/2018/mar/15 pass: 3,842; fail: 6; error: 4 Build 7: aarch64/2018/mar/17 pass: 3,842; fail: 6; error: 4 Build 8: aarch64/2018/mar/19 pass: 3,843; fail: 6; error: 3 Build 9: aarch64/2018/mar/21 pass: 3,844; fail: 6; error: 2 Build 10: aarch64/2018/mar/23 pass: 3,843; fail: 6; error: 3 Build 11: aarch64/2018/mar/25 pass: 3,844; fail: 6; error: 7 Build 12: aarch64/2018/mar/27 pass: 3,847; fail: 6; error: 4 Build 13: aarch64/2018/mar/29 pass: 3,849; fail: 6; error: 2 Build 14: aarch64/2018/mar/31 pass: 3,851; fail: 6 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/jan/07 pass: 7,599; fail: 714; error: 26 Build 1: aarch64/2018/jan/11 pass: 7,590; fail: 724; error: 25 Build 2: aarch64/2018/jan/13 pass: 7,598; fail: 715; error: 26 Build 3: aarch64/2018/jan/19 pass: 7,620; fail: 700; error: 21 Build 4: aarch64/2018/jan/21 pass: 7,600; fail: 714; error: 27 Build 5: aarch64/2018/feb/21 pass: 7,656; fail: 716; error: 27 Build 6: aarch64/2018/mar/15 pass: 7,680; fail: 703; error: 22 Build 7: aarch64/2018/mar/17 pass: 7,670; fail: 711; error: 24 Build 8: aarch64/2018/mar/19 pass: 7,669; fail: 714; error: 22 Build 9: aarch64/2018/mar/21 pass: 7,675; fail: 711; error: 19 Build 10: aarch64/2018/mar/23 pass: 7,643; fail: 740; error: 22 Build 11: aarch64/2018/mar/25 pass: 7,811; fail: 599; error: 17 Build 12: aarch64/2018/mar/27 pass: 7,794; fail: 614; error: 19 Build 13: aarch64/2018/mar/29 pass: 7,823; fail: 585; error: 19 Build 14: aarch64/2018/mar/31 pass: 7,798; fail: 611; error: 18 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/jan/07 pass: 3,823; fail: 5; error: 2 Build 1: aarch64/2018/jan/11 pass: 3,824; fail: 5; error: 1 Build 2: aarch64/2018/jan/13 pass: 3,819; fail: 5; error: 6 Build 3: aarch64/2018/jan/19 pass: 3,829; fail: 5; error: 1 Build 4: aarch64/2018/jan/21 pass: 3,827; fail: 5; error: 3 Build 5: aarch64/2018/feb/21 pass: 3,838; fail: 6; error: 2 Build 6: aarch64/2018/mar/15 pass: 3,845; fail: 6; error: 1 Build 7: aarch64/2018/mar/17 pass: 3,841; fail: 6; error: 5 Build 8: aarch64/2018/mar/19 pass: 3,843; fail: 6; error: 3 Build 9: aarch64/2018/mar/21 pass: 3,841; fail: 6; error: 5 Build 10: aarch64/2018/mar/23 pass: 3,843; fail: 6; error: 3 Build 11: aarch64/2018/mar/25 pass: 3,850; fail: 6; error: 1 Build 12: aarch64/2018/mar/27 pass: 3,848; fail: 6; error: 3 Build 13: aarch64/2018/mar/29 pass: 3,848; fail: 6; error: 3 Build 14: aarch64/2018/mar/31 pass: 3,850; fail: 6; error: 1 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): 1.01x Relative performance: Server critical-jOPS (nc): 0.76x 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 client and server compilers on 2014-04-01. Relative performance: Zero: 1.0, Client: 68.19, Server: 113.83 Client 68.19 / Client 2014-04-01 (43.00): 1.59x Server 113.83 / Server 2014-04-01 (71.00): 1.60x 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-01-09 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/007/results/ 2018-01-12 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/011/results/ 2018-01-15 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/013/results/ 2018-01-20 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/019/results/ 2018-01-22 pass rate: 11557/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/021/results/ 2018-02-22 pass rate: 11557/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/052/results/ 2018-03-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/074/results/ 2018-03-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/076/results/ 2018-03-19 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/078/results/ 2018-03-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/080/results/ 2018-03-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/082/results/ 2018-03-26 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/084/results/ 2018-03-29 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/086/results/ 2018-03-30 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/088/results/ 2018-03-31 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/090/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 30 Mar '18

30 Mar '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/088… ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/jan/05 pass: 7,594; fail: 711; error: 30 Build 1: aarch64/2018/jan/07 pass: 7,593; fail: 726; error: 20 Build 2: aarch64/2018/jan/11 pass: 7,585; fail: 729; error: 25 Build 3: aarch64/2018/jan/13 pass: 7,591; fail: 726; error: 22 Build 4: aarch64/2018/jan/19 pass: 7,598; fail: 720; error: 23 Build 5: aarch64/2018/jan/21 pass: 7,595; fail: 717; error: 29 Build 6: aarch64/2018/feb/21 pass: 7,623; fail: 749; error: 27 Build 7: aarch64/2018/mar/15 pass: 7,693; fail: 692; error: 20 Build 8: aarch64/2018/mar/17 pass: 7,654; fail: 727; error: 24 Build 9: aarch64/2018/mar/19 pass: 7,657; fail: 722; error: 26 Build 10: aarch64/2018/mar/21 pass: 7,652; fail: 732; error: 21 Build 11: aarch64/2018/mar/23 pass: 7,629; fail: 752; error: 24 Build 12: aarch64/2018/mar/25 pass: 7,778; fail: 629; error: 20 Build 13: aarch64/2018/mar/27 pass: 7,773; fail: 634; error: 20 Build 14: aarch64/2018/mar/29 pass: 7,790; fail: 617; error: 20 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/jan/05 pass: 3,820; fail: 5; error: 2 Build 1: aarch64/2018/jan/07 pass: 3,821; fail: 5; error: 4 Build 2: aarch64/2018/jan/11 pass: 3,824; fail: 5; error: 1 Build 3: aarch64/2018/jan/13 pass: 3,821; fail: 5; error: 4 Build 4: aarch64/2018/jan/19 pass: 3,825; fail: 5; error: 5 Build 5: aarch64/2018/jan/21 pass: 3,824; fail: 5; error: 6 Build 6: aarch64/2018/feb/21 pass: 3,831; fail: 6; error: 9 Build 7: aarch64/2018/mar/15 pass: 3,842; fail: 6; error: 4 Build 8: aarch64/2018/mar/17 pass: 3,842; fail: 6; error: 4 Build 9: aarch64/2018/mar/19 pass: 3,843; fail: 6; error: 3 Build 10: aarch64/2018/mar/21 pass: 3,844; fail: 6; error: 2 Build 11: aarch64/2018/mar/23 pass: 3,843; fail: 6; error: 3 Build 12: aarch64/2018/mar/25 pass: 3,844; fail: 6; error: 7 Build 13: aarch64/2018/mar/27 pass: 3,847; fail: 6; error: 4 Build 14: aarch64/2018/mar/29 pass: 3,849; fail: 6; error: 2 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/jan/05 pass: 7,576; fail: 738; error: 21 Build 1: aarch64/2018/jan/07 pass: 7,599; fail: 714; error: 26 Build 2: aarch64/2018/jan/11 pass: 7,590; fail: 724; error: 25 Build 3: aarch64/2018/jan/13 pass: 7,598; fail: 715; error: 26 Build 4: aarch64/2018/jan/19 pass: 7,620; fail: 700; error: 21 Build 5: aarch64/2018/jan/21 pass: 7,600; fail: 714; error: 27 Build 6: aarch64/2018/feb/21 pass: 7,656; fail: 716; error: 27 Build 7: aarch64/2018/mar/15 pass: 7,680; fail: 703; error: 22 Build 8: aarch64/2018/mar/17 pass: 7,670; fail: 711; error: 24 Build 9: aarch64/2018/mar/19 pass: 7,669; fail: 714; error: 22 Build 10: aarch64/2018/mar/21 pass: 7,675; fail: 711; error: 19 Build 11: aarch64/2018/mar/23 pass: 7,643; fail: 740; error: 22 Build 12: aarch64/2018/mar/25 pass: 7,811; fail: 599; error: 17 Build 13: aarch64/2018/mar/27 pass: 7,794; fail: 614; error: 19 Build 14: aarch64/2018/mar/29 pass: 7,823; fail: 585; error: 19 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/jan/05 pass: 3,817; fail: 5; error: 5 Build 1: aarch64/2018/jan/07 pass: 3,823; fail: 5; error: 2 Build 2: aarch64/2018/jan/11 pass: 3,824; fail: 5; error: 1 Build 3: aarch64/2018/jan/13 pass: 3,819; fail: 5; error: 6 Build 4: aarch64/2018/jan/19 pass: 3,829; fail: 5; error: 1 Build 5: aarch64/2018/jan/21 pass: 3,827; fail: 5; error: 3 Build 6: aarch64/2018/feb/21 pass: 3,838; fail: 6; error: 2 Build 7: aarch64/2018/mar/15 pass: 3,845; fail: 6; error: 1 Build 8: aarch64/2018/mar/17 pass: 3,841; fail: 6; error: 5 Build 9: aarch64/2018/mar/19 pass: 3,843; fail: 6; error: 3 Build 10: aarch64/2018/mar/21 pass: 3,841; fail: 6; error: 5 Build 11: aarch64/2018/mar/23 pass: 3,843; fail: 6; error: 3 Build 12: aarch64/2018/mar/25 pass: 3,850; fail: 6; error: 1 Build 13: aarch64/2018/mar/27 pass: 3,848; fail: 6; error: 3 Build 14: aarch64/2018/mar/29 pass: 3,848; fail: 6; error: 3 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): 1.01x Relative performance: Server critical-jOPS (nc): 0.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 client and server compilers on 2014-04-01. Relative performance: Zero: 1.0, Client: 67.86, Server: 115.7 Client 67.86 / Client 2014-04-01 (43.00): 1.58x Server 115.7 / Server 2014-04-01 (71.00): 1.63x 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-01-07 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/005/results/ 2018-01-09 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/007/results/ 2018-01-12 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/011/results/ 2018-01-15 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/013/results/ 2018-01-20 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/019/results/ 2018-01-22 pass rate: 11557/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/021/results/ 2018-02-22 pass rate: 11557/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/052/results/ 2018-03-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/074/results/ 2018-03-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/076/results/ 2018-03-19 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/078/results/ 2018-03-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/080/results/ 2018-03-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/082/results/ 2018-03-26 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/084/results/ 2018-03-29 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/086/results/ 2018-03-30 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/088/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 29 Mar '18

29 Mar '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/086… ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/dec/27 pass: 7,575; fail: 736; error: 24 Build 1: aarch64/2018/jan/05 pass: 7,594; fail: 711; error: 30 Build 2: aarch64/2018/jan/07 pass: 7,593; fail: 726; error: 20 Build 3: aarch64/2018/jan/11 pass: 7,585; fail: 729; error: 25 Build 4: aarch64/2018/jan/13 pass: 7,591; fail: 726; error: 22 Build 5: aarch64/2018/jan/19 pass: 7,598; fail: 720; error: 23 Build 6: aarch64/2018/jan/21 pass: 7,595; fail: 717; error: 29 Build 7: aarch64/2018/feb/21 pass: 7,623; fail: 749; error: 27 Build 8: aarch64/2018/mar/15 pass: 7,693; fail: 692; error: 20 Build 9: aarch64/2018/mar/17 pass: 7,654; fail: 727; error: 24 Build 10: aarch64/2018/mar/19 pass: 7,657; fail: 722; error: 26 Build 11: aarch64/2018/mar/21 pass: 7,652; fail: 732; error: 21 Build 12: aarch64/2018/mar/23 pass: 7,629; fail: 752; error: 24 Build 13: aarch64/2018/mar/25 pass: 7,778; fail: 629; error: 20 Build 14: aarch64/2018/mar/27 pass: 7,773; fail: 634; error: 20 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/dec/27 pass: 3,821; fail: 5; error: 1 Build 1: aarch64/2018/jan/05 pass: 3,820; fail: 5; error: 2 Build 2: aarch64/2018/jan/07 pass: 3,821; fail: 5; error: 4 Build 3: aarch64/2018/jan/11 pass: 3,824; fail: 5; error: 1 Build 4: aarch64/2018/jan/13 pass: 3,821; fail: 5; error: 4 Build 5: aarch64/2018/jan/19 pass: 3,825; fail: 5; error: 5 Build 6: aarch64/2018/jan/21 pass: 3,824; fail: 5; error: 6 Build 7: aarch64/2018/feb/21 pass: 3,831; fail: 6; error: 9 Build 8: aarch64/2018/mar/15 pass: 3,842; fail: 6; error: 4 Build 9: aarch64/2018/mar/17 pass: 3,842; fail: 6; error: 4 Build 10: aarch64/2018/mar/19 pass: 3,843; fail: 6; error: 3 Build 11: aarch64/2018/mar/21 pass: 3,844; fail: 6; error: 2 Build 12: aarch64/2018/mar/23 pass: 3,843; fail: 6; error: 3 Build 13: aarch64/2018/mar/25 pass: 3,844; fail: 6; error: 7 Build 14: aarch64/2018/mar/27 pass: 3,847; fail: 6; error: 4 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/dec/27 pass: 7,589; fail: 721; error: 25 Build 1: aarch64/2018/jan/05 pass: 7,576; fail: 738; error: 21 Build 2: aarch64/2018/jan/07 pass: 7,599; fail: 714; error: 26 Build 3: aarch64/2018/jan/11 pass: 7,590; fail: 724; error: 25 Build 4: aarch64/2018/jan/13 pass: 7,598; fail: 715; error: 26 Build 5: aarch64/2018/jan/19 pass: 7,620; fail: 700; error: 21 Build 6: aarch64/2018/jan/21 pass: 7,600; fail: 714; error: 27 Build 7: aarch64/2018/feb/21 pass: 7,656; fail: 716; error: 27 Build 8: aarch64/2018/mar/15 pass: 7,680; fail: 703; error: 22 Build 9: aarch64/2018/mar/17 pass: 7,670; fail: 711; error: 24 Build 10: aarch64/2018/mar/19 pass: 7,669; fail: 714; error: 22 Build 11: aarch64/2018/mar/21 pass: 7,675; fail: 711; error: 19 Build 12: aarch64/2018/mar/23 pass: 7,643; fail: 740; error: 22 Build 13: aarch64/2018/mar/25 pass: 7,811; fail: 599; error: 17 Build 14: aarch64/2018/mar/27 pass: 7,794; fail: 614; error: 19 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/dec/27 pass: 3,820; fail: 5; error: 2 Build 1: aarch64/2018/jan/05 pass: 3,817; fail: 5; error: 5 Build 2: aarch64/2018/jan/07 pass: 3,823; fail: 5; error: 2 Build 3: aarch64/2018/jan/11 pass: 3,824; fail: 5; error: 1 Build 4: aarch64/2018/jan/13 pass: 3,819; fail: 5; error: 6 Build 5: aarch64/2018/jan/19 pass: 3,829; fail: 5; error: 1 Build 6: aarch64/2018/jan/21 pass: 3,827; fail: 5; error: 3 Build 7: aarch64/2018/feb/21 pass: 3,838; fail: 6; error: 2 Build 8: aarch64/2018/mar/15 pass: 3,845; fail: 6; error: 1 Build 9: aarch64/2018/mar/17 pass: 3,841; fail: 6; error: 5 Build 10: aarch64/2018/mar/19 pass: 3,843; fail: 6; error: 3 Build 11: aarch64/2018/mar/21 pass: 3,841; fail: 6; error: 5 Build 12: aarch64/2018/mar/23 pass: 3,843; fail: 6; error: 3 Build 13: aarch64/2018/mar/25 pass: 3,850; fail: 6; error: 1 Build 14: aarch64/2018/mar/27 pass: 3,848; fail: 6; error: 3 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): 1.01x Relative performance: Server critical-jOPS (nc): 0.86x 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 client and server compilers on 2014-04-01. Relative performance: Zero: 1.0, Client: 67.21, Server: 112.02 Client 67.21 / Client 2014-04-01 (43.00): 1.56x Server 112.02 / Server 2014-04-01 (71.00): 1.58x 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. 2017-12-28 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2017/361/results/ 2018-01-07 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/005/results/ 2018-01-09 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/007/results/ 2018-01-12 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/011/results/ 2018-01-15 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/013/results/ 2018-01-20 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/019/results/ 2018-01-22 pass rate: 11557/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/021/results/ 2018-02-22 pass rate: 11557/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/052/results/ 2018-03-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/074/results/ 2018-03-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/076/results/ 2018-03-19 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/078/results/ 2018-03-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/080/results/ 2018-03-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/082/results/ 2018-03-26 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/084/results/ 2018-03-29 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/086/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/

1 0

ZGC & AArch64
by Stuart Monteith 29 Mar '18

29 Mar '18

Hello, After Ed and I spoke with Per and Stefan at FOSDEM I've started working on seeing what is necessary to get ZGC working on the Aarch64 backend. To be clear, this is the hotspot/cpu/aarch64 backend rather than hotspot/cpu/arm backend. I have just some observations and questions so far: 1. The address space used by ZGC is impressive - 17TB on my laptop. However, you need to make sure your kernel is configured for 48-bit virtual address space. I've currently hobbled ZGC a little to work within the 42-bit VA. - basically using 39-bits rather than 42-bits as the base addresses. 2. I'm basing my work on the SPARC port and the Linux x86 port. The top 8-bits on aarch64 can be used as tag bits, and so that's where I'm putting the "colours" - much like SPARC. The os_cpu code is mostly derived from linux_x86, however. I've removed the multi-mapping as that is unnecessary. 3. If this code gets ported on further platforms, we'll need to look at refactoring the code. There will be a lot of redundancy. I'll follow what you are doing for now, until aarch64 is in an acceptable state. 4. How active is the SPARC port? I've largely been taking my cues from that port in the backend, rather than the OS code, and it would be good to know if there are issues doing that. 5. I expected ZAddressBadMask to be held in Universe - is this to ease rebasing? Ordinarily we'd retrieve such values through Universe:: 6. Do you expect signal handlers to play a part in ZGC in the future? It is something to watch on aarch64, as the tag bits will get stripped under most circumstances. I currently have it building, and I can run a GC benchmark on interpreter mode, until hitting an issue with a references to a oop in an unallocated ZPage. Running the same code on x86 completes just fine. Thanks, Stuart

2 1

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

26 Mar '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/084… ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/dec/23 pass: 7,581; fail: 734; error: 20 Build 1: aarch64/2017/dec/27 pass: 7,575; fail: 736; error: 24 Build 2: aarch64/2018/jan/05 pass: 7,594; fail: 711; error: 30 Build 3: aarch64/2018/jan/07 pass: 7,593; fail: 726; error: 20 Build 4: aarch64/2018/jan/11 pass: 7,585; fail: 729; error: 25 Build 5: aarch64/2018/jan/13 pass: 7,591; fail: 726; error: 22 Build 6: aarch64/2018/jan/19 pass: 7,598; fail: 720; error: 23 Build 7: aarch64/2018/jan/21 pass: 7,595; fail: 717; error: 29 Build 8: aarch64/2018/feb/21 pass: 7,623; fail: 749; error: 27 Build 9: aarch64/2018/mar/15 pass: 7,693; fail: 692; error: 20 Build 10: aarch64/2018/mar/17 pass: 7,654; fail: 727; error: 24 Build 11: aarch64/2018/mar/19 pass: 7,657; fail: 722; error: 26 Build 12: aarch64/2018/mar/21 pass: 7,652; fail: 732; error: 21 Build 13: aarch64/2018/mar/23 pass: 7,629; fail: 752; error: 24 Build 14: aarch64/2018/mar/25 pass: 7,778; fail: 629; error: 20 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/dec/23 pass: 3,818; fail: 5; error: 4 Build 1: aarch64/2017/dec/27 pass: 3,821; fail: 5; error: 1 Build 2: aarch64/2018/jan/05 pass: 3,820; fail: 5; error: 2 Build 3: aarch64/2018/jan/07 pass: 3,821; fail: 5; error: 4 Build 4: aarch64/2018/jan/11 pass: 3,824; fail: 5; error: 1 Build 5: aarch64/2018/jan/13 pass: 3,821; fail: 5; error: 4 Build 6: aarch64/2018/jan/19 pass: 3,825; fail: 5; error: 5 Build 7: aarch64/2018/jan/21 pass: 3,824; fail: 5; error: 6 Build 8: aarch64/2018/feb/21 pass: 3,831; fail: 6; error: 9 Build 9: aarch64/2018/mar/15 pass: 3,842; fail: 6; error: 4 Build 10: aarch64/2018/mar/17 pass: 3,842; fail: 6; error: 4 Build 11: aarch64/2018/mar/19 pass: 3,843; fail: 6; error: 3 Build 12: aarch64/2018/mar/21 pass: 3,844; fail: 6; error: 2 Build 13: aarch64/2018/mar/23 pass: 3,843; fail: 6; error: 3 Build 14: aarch64/2018/mar/25 pass: 3,844; fail: 6; error: 7 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/dec/23 pass: 7,596; fail: 717; error: 22 Build 1: aarch64/2017/dec/27 pass: 7,589; fail: 721; error: 25 Build 2: aarch64/2018/jan/05 pass: 7,576; fail: 738; error: 21 Build 3: aarch64/2018/jan/07 pass: 7,599; fail: 714; error: 26 Build 4: aarch64/2018/jan/11 pass: 7,590; fail: 724; error: 25 Build 5: aarch64/2018/jan/13 pass: 7,598; fail: 715; error: 26 Build 6: aarch64/2018/jan/19 pass: 7,620; fail: 700; error: 21 Build 7: aarch64/2018/jan/21 pass: 7,600; fail: 714; error: 27 Build 8: aarch64/2018/feb/21 pass: 7,656; fail: 716; error: 27 Build 9: aarch64/2018/mar/15 pass: 7,680; fail: 703; error: 22 Build 10: aarch64/2018/mar/17 pass: 7,670; fail: 711; error: 24 Build 11: aarch64/2018/mar/19 pass: 7,669; fail: 714; error: 22 Build 12: aarch64/2018/mar/21 pass: 7,675; fail: 711; error: 19 Build 13: aarch64/2018/mar/23 pass: 7,643; fail: 740; error: 22 Build 14: aarch64/2018/mar/25 pass: 7,811; fail: 599; error: 17 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/dec/23 pass: 3,819; fail: 5; error: 3 Build 1: aarch64/2017/dec/27 pass: 3,820; fail: 5; error: 2 Build 2: aarch64/2018/jan/05 pass: 3,817; fail: 5; error: 5 Build 3: aarch64/2018/jan/07 pass: 3,823; fail: 5; error: 2 Build 4: aarch64/2018/jan/11 pass: 3,824; fail: 5; error: 1 Build 5: aarch64/2018/jan/13 pass: 3,819; fail: 5; error: 6 Build 6: aarch64/2018/jan/19 pass: 3,829; fail: 5; error: 1 Build 7: aarch64/2018/jan/21 pass: 3,827; fail: 5; error: 3 Build 8: aarch64/2018/feb/21 pass: 3,838; fail: 6; error: 2 Build 9: aarch64/2018/mar/15 pass: 3,845; fail: 6; error: 1 Build 10: aarch64/2018/mar/17 pass: 3,841; fail: 6; error: 5 Build 11: aarch64/2018/mar/19 pass: 3,843; fail: 6; error: 3 Build 12: aarch64/2018/mar/21 pass: 3,841; fail: 6; error: 5 Build 13: aarch64/2018/mar/23 pass: 3,843; fail: 6; error: 3 Build 14: aarch64/2018/mar/25 pass: 3,850; fail: 6; error: 1 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): 1.01x Relative performance: Server critical-jOPS (nc): 0.92x 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 client and server compilers on 2014-04-01. Relative performance: Zero: 1.0, Client: 66.9, Server: 110.27 Client 66.9 / Client 2014-04-01 (43.00): 1.56x Server 110.27 / Server 2014-04-01 (71.00): 1.55x 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. 2017-12-24 pass rate: 11557/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2017/357/results/ 2017-12-28 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2017/361/results/ 2018-01-07 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/005/results/ 2018-01-09 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/007/results/ 2018-01-12 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/011/results/ 2018-01-15 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/013/results/ 2018-01-20 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/019/results/ 2018-01-22 pass rate: 11557/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/021/results/ 2018-02-22 pass rate: 11557/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/052/results/ 2018-03-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/074/results/ 2018-03-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/076/results/ 2018-03-19 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/078/results/ 2018-03-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/080/results/ 2018-03-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/082/results/ 2018-03-26 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/084/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 25 Mar '18

25 Mar '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/082… ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/dec/19 pass: 7,572; fail: 740; error: 24 Build 1: aarch64/2017/dec/23 pass: 7,581; fail: 734; error: 20 Build 2: aarch64/2017/dec/27 pass: 7,575; fail: 736; error: 24 Build 3: aarch64/2018/jan/05 pass: 7,594; fail: 711; error: 30 Build 4: aarch64/2018/jan/07 pass: 7,593; fail: 726; error: 20 Build 5: aarch64/2018/jan/11 pass: 7,585; fail: 729; error: 25 Build 6: aarch64/2018/jan/13 pass: 7,591; fail: 726; error: 22 Build 7: aarch64/2018/jan/19 pass: 7,598; fail: 720; error: 23 Build 8: aarch64/2018/jan/21 pass: 7,595; fail: 717; error: 29 Build 9: aarch64/2018/feb/21 pass: 7,623; fail: 749; error: 27 Build 10: aarch64/2018/mar/15 pass: 7,693; fail: 692; error: 20 Build 11: aarch64/2018/mar/17 pass: 7,654; fail: 727; error: 24 Build 12: aarch64/2018/mar/19 pass: 7,657; fail: 722; error: 26 Build 13: aarch64/2018/mar/21 pass: 7,652; fail: 732; error: 21 Build 14: aarch64/2018/mar/23 pass: 7,629; fail: 752; error: 24 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/dec/19 pass: 3,819; fail: 3; error: 4 Build 1: aarch64/2017/dec/23 pass: 3,818; fail: 5; error: 4 Build 2: aarch64/2017/dec/27 pass: 3,821; fail: 5; error: 1 Build 3: aarch64/2018/jan/05 pass: 3,820; fail: 5; error: 2 Build 4: aarch64/2018/jan/07 pass: 3,821; fail: 5; error: 4 Build 5: aarch64/2018/jan/11 pass: 3,824; fail: 5; error: 1 Build 6: aarch64/2018/jan/13 pass: 3,821; fail: 5; error: 4 Build 7: aarch64/2018/jan/19 pass: 3,825; fail: 5; error: 5 Build 8: aarch64/2018/jan/21 pass: 3,824; fail: 5; error: 6 Build 9: aarch64/2018/feb/21 pass: 3,831; fail: 6; error: 9 Build 10: aarch64/2018/mar/15 pass: 3,842; fail: 6; error: 4 Build 11: aarch64/2018/mar/17 pass: 3,842; fail: 6; error: 4 Build 12: aarch64/2018/mar/19 pass: 3,843; fail: 6; error: 3 Build 13: aarch64/2018/mar/21 pass: 3,844; fail: 6; error: 2 Build 14: aarch64/2018/mar/23 pass: 3,843; fail: 6; error: 3 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/dec/19 pass: 7,586; fail: 726; error: 24 Build 1: aarch64/2017/dec/23 pass: 7,596; fail: 717; error: 22 Build 2: aarch64/2017/dec/27 pass: 7,589; fail: 721; error: 25 Build 3: aarch64/2018/jan/05 pass: 7,576; fail: 738; error: 21 Build 4: aarch64/2018/jan/07 pass: 7,599; fail: 714; error: 26 Build 5: aarch64/2018/jan/11 pass: 7,590; fail: 724; error: 25 Build 6: aarch64/2018/jan/13 pass: 7,598; fail: 715; error: 26 Build 7: aarch64/2018/jan/19 pass: 7,620; fail: 700; error: 21 Build 8: aarch64/2018/jan/21 pass: 7,600; fail: 714; error: 27 Build 9: aarch64/2018/feb/21 pass: 7,656; fail: 716; error: 27 Build 10: aarch64/2018/mar/15 pass: 7,680; fail: 703; error: 22 Build 11: aarch64/2018/mar/17 pass: 7,670; fail: 711; error: 24 Build 12: aarch64/2018/mar/19 pass: 7,669; fail: 714; error: 22 Build 13: aarch64/2018/mar/21 pass: 7,675; fail: 711; error: 19 Build 14: aarch64/2018/mar/23 pass: 7,643; fail: 740; error: 22 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/dec/19 pass: 3,817; fail: 3; error: 6 Build 1: aarch64/2017/dec/23 pass: 3,819; fail: 5; error: 3 Build 2: aarch64/2017/dec/27 pass: 3,820; fail: 5; error: 2 Build 3: aarch64/2018/jan/05 pass: 3,817; fail: 5; error: 5 Build 4: aarch64/2018/jan/07 pass: 3,823; fail: 5; error: 2 Build 5: aarch64/2018/jan/11 pass: 3,824; fail: 5; error: 1 Build 6: aarch64/2018/jan/13 pass: 3,819; fail: 5; error: 6 Build 7: aarch64/2018/jan/19 pass: 3,829; fail: 5; error: 1 Build 8: aarch64/2018/jan/21 pass: 3,827; fail: 5; error: 3 Build 9: aarch64/2018/feb/21 pass: 3,838; fail: 6; error: 2 Build 10: aarch64/2018/mar/15 pass: 3,845; fail: 6; error: 1 Build 11: aarch64/2018/mar/17 pass: 3,841; fail: 6; error: 5 Build 12: aarch64/2018/mar/19 pass: 3,843; fail: 6; error: 3 Build 13: aarch64/2018/mar/21 pass: 3,841; fail: 6; error: 5 Build 14: aarch64/2018/mar/23 pass: 3,843; fail: 6; error: 3 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): 1.01x Relative performance: Server critical-jOPS (nc): 0.84x 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 client and server compilers on 2014-04-01. Relative performance: Zero: 1.0, Client: 67.86, Server: 112.92 Client 67.86 / Client 2014-04-01 (43.00): 1.58x Server 112.92 / Server 2014-04-01 (71.00): 1.59x 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. 2017-12-20 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2017/353/results/ 2017-12-24 pass rate: 11557/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2017/357/results/ 2017-12-28 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2017/361/results/ 2018-01-07 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/005/results/ 2018-01-09 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/007/results/ 2018-01-12 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/011/results/ 2018-01-15 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/013/results/ 2018-01-20 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/019/results/ 2018-01-22 pass rate: 11557/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/021/results/ 2018-02-22 pass rate: 11557/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/052/results/ 2018-03-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/074/results/ 2018-03-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/076/results/ 2018-03-19 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/078/results/ 2018-03-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/080/results/ 2018-03-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/082/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/

1 0