June 2018 - aarch64-port-dev

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: 8205694: AArch64: Add test to validate volatile load, store and CAS code generation
by Andrew Dinn 28 Jun '18

28 Jun '18

Reviews are welcome for the following webrev webrev: http://cr.openjdk.java.net/~adinn/8205694/webrev.00/ JIRA: https://bugs.openjdk.java.net/browse/JDK-8205694 The patch: ---------- This AArch64-only patch adds tests to ensure that volatile load, store and CAS operations are either: translated to correctly replace memory barriers with combinations of acquiring loads and releasing left untransformed with all necessary memory barriers in place The test requires a debug, aarch64 vm and is disabled if graal is being used (debug is necessary because it relies on -XX:+PrintOptoAssembly to provide evidence of what is in the compiler output). The main driver test program creates subordinate JVMs to execute subordinate programs which perform: normal and unsafe volatile loads, normal and unsafe volatile stores unsafe volatile CASes in each of 5 GC configurations: G1 CMS+CondCardMark CMS-CondCardMark Parallel Serial Arguments -XXCompileCommand,compileonly and XX:+PrintOptoAssembly are used to generate Assembly listings and the driver test program parses these to ensure the correct sequences of instructions are generated (including omitted memory barriers which are flagged in the output). A few changes were made to the aarch64.ad file to ensure that the PrintOptoAssembly output accurately represented the generated code. These were necessary to ensure that the test could be sure that the generated code sequences really were what was intended. Also, some of the comments in aarch64.ad describing the code transformation were updated following feedback from Zhongwei Yao that arrived too late to get checked in with the fix for JDK-8204331. Testing: -------- The test itself passes when run on an AArch64 debug vm. It is ignored when run on an AArch64 product vm. No other testing is needed. Nothing significant in the aarch64.ad file has been modified (only comments of format sequences which have been exercised running the new test). regards, Andrew Dinn ----------- Senior Principal Software Engineer Red Hat UK Ltd Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander

5 18

64-Bit literal oops
by Stuart Monteith 26 Jun '18

26 Jun '18

Hello, As requested, I've gotten what is appears to be near the minimal set of changes for 64-bit literal oops. We really only need this for ZGC, so apart from testing, it would only be ZGC enabling it. Otherwise, there are no other interesting uses, apart from maybe as support for 52-bit addressing. I've tested with movz, movk, movk, possible movk patching in MacroAssembler::pd_patch_instruction_size and MacroAssembler::target_addr_for_insn . The "ShouldNotReachHere()" calls are never tripped, and so could be taken out. I'm pushing down a flag from movoop down to movptr, to indicate when an oop literal is being emitted, which movoop obviously implicitly knows: MacroAssembler::movoop(Register, jobject, bool) MacroAssembler:mov(Register, Address, bool isOop) MacroAssembler:movptr(Register, u_int64_t, bool isOop) NativeMovConstReg has been changed to detect the size of the instruction - as it may be a movz,movk,movk combination, or perhaps it will be an oop with an additional movk for the 64-bit literal oop. It does this conditionally. I have been considering adding an additional check by comparing the register being stored to. I'm looking now at adding information to relocs to indicate they are for an oop, as suggested by aph. BR, Stuart

1 0

RFR(S): 8205475 - AARCH64: optimize FPU loads and stores in C1_Runtime1_aarch64.cpp
by Dmitrij Pochepko 25 Jun '18

25 Jun '18

Hi all, please review patch for 8205475 - AARCH64: optimize FPU loads and stores in C1_Runtime1_aarch64.cpp This patch replaces ldpd/stpd instructions with ld1/st1 for saving/restoring registers in C1_Runtime1_aarch64.cpp which is more compact and more beneficial for a number of stubs. webrev: http://cr.openjdk.java.net/~dpochepk/8205475/webrev.01/ CR: https://bugs.openjdk.java.net/browse/JDK-8205475 Testing: hotspot jtreg test in fastdebug and release builds. example: 0x0000ffff88b23468: ldp d0, d1, [sp], #16 0x0000ffff88b2346c: ldp d2, d3, [sp], #16 0x0000ffff88b23470: ldp d4, d5, [sp], #16 0x0000ffff88b23474: ldp d6, d7, [sp], #16 0x0000ffff88b23478: ldp d8, d9, [sp], #16 0x0000ffff88b2347c: ldp d10, d11, [sp], #16 0x0000ffff88b23480: ldp d12, d13, [sp], #16 0x0000ffff88b23484: ldp d14, d15, [sp], #16 0x0000ffff88b23488: ldp d16, d17, [sp], #16 0x0000ffff88b2348c: ldp d18, d19, [sp], #16 0x0000ffff88b23490: ldp d20, d21, [sp], #16 0x0000ffff88b23494: ldp d22, d23, [sp], #16 0x0000ffff88b23498: ldp d24, d25, [sp], #16 0x0000ffff88b2349c: ldp d26, d27, [sp], #16 0x0000ffff88b234a0: ldp d28, d29, [sp], #16 0x0000ffff88b234a4: ldp d30, d31, [sp], #16 changed to: 0x0000ffff9cb23468: ld1 {v0.1d-v3.1d}, [sp], #32 0x0000ffff9cb2346c: ld1 {v4.1d-v7.1d}, [sp], #32 0x0000ffff9cb23470: ld1 {v8.1d-v11.1d}, [sp], #32 0x0000ffff9cb23474: ld1 {v12.1d-v15.1d}, [sp], #32 0x0000ffff9cb23478: ld1 {v16.1d-v19.1d}, [sp], #32 0x0000ffff9cb2347c: ld1 {v20.1d-v23.1d}, [sp], #32 0x0000ffff9cb23480: ld1 {v24.1d-v27.1d}, [sp], #32 0x0000ffff9cb23484: ld1 {v28.1d-v31.1d}, [sp], #32 Thanks, Dmitrij

3 4

RFR: 8204289: AARCH64: enable math intrinsics usage in interpreter and C1
by Dmitrij Pochepko 25 Jun '18

25 Jun '18

Hi all, please review patch for JDK-8204289: AARCH64: enable math intrinsics usage in interpreter and C1 This patch enables usage of math intrinsics for interpreter and C1 in case intrinsics are implemented. Code follows that of x86 port. Testing: I've merged this patch with implemented intrinsic and launched jtreg tests and benchmark in 2 more modes: -Xint and -XX:TieredStopAtLevel=3 Benchmark scores were improved as expected of intrinsic. All tests passed. webrev: http://cr.openjdk.java.net/~dpochepk/8204289/webrev.01/ CR: https://bugs.openjdk.java.net/browse/JDK-8204289 Thanks, Dmitrij

4 9

-XX:CompileCommand=print causes core dump
by Dave Nuechterlein 25 Jun '18

25 Jun '18

I have a very simple maven based JMH test. If I add -XX:+UnlockDiagnosticVMOptions -XX:CompileCommand=print,com.ampere.pipeline_int_mvn.generated.MyBenchmark_test_method_jmhTest::test_method_avgt_jmhStub To my command string, I get a core dump: # Compiler replay data is saved as: # /home/dnuechte/java/pipeline_int_mvn/replay_pid22566.log # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # Current thread is 22577 Dumping core ... Aborted Should I submit a bug report like the spew suggests? Or is there a different mechanism at this point in the project? I built my own hsdis two different ways, neither works. I built one with binutils 2.24, and one with 2.29. Since there was a change in the interface between 2.24 and 2.29, the version with 2.29 needs a patch to hsdis.c /* Finish linking together the various callback blocks. */ app_data->dinfo.application_data = (void*) app_data; - app_data->dfn = disassembler(native_bfd); + app_data->dfn = disassembler(bfd_get_arch(native_bfd), + bfd_big_endian(native_bfd), + bfd_get_mach(native_bfd), + native_bfd); app_data->dinfo.print_address_func = hsdis_print_address_func; app_data->dinfo.read_memory_func = hsdis_read_memory_func; Dave

3 5

RFR(M): 8196402: AARCH64: create intrinsic for Math.log
by Dmitrij Pochepko 25 Jun '18

25 Jun '18

Hi all, please review patch for 8196402: AARCH64: create intrinsic for Math.log This patch adds Math.log intrinsic to AARCH64. Algorithm is based on a table-based search logic such as described in paper [1]. Algorithm splits argument in 2 parts (exponent-based and mantissa-based), calculate reciprocal estimate of mantissa part and finds reduced argument value using pregenerated table, then calculates final value using 7th degree polynomial of reduced argument. This patch heavily uses vector calculations. Few previously unimplemented vector instructions are added to support it. Performance results: I created separate JMH benchmark: http://cr.openjdk.java.net/~dpochepk/8196402/MathBench.java Benchmark results for logarithm (intrinsic vs without intrinsics (shared runtime)): ThunderX: x1.37 improvement ThunderX2: x1.33 improvement Cortex A73: x1.2 improvement Cortex A53: x1.6 improvement Detailed results can be checked here: http://cr.openjdk.java.net/~dpochepk/8196402/math-log.xls webrev: http://cr.openjdk.java.net/~dpochepk/8196402/webrev.01/ CR: https://bugs.openjdk.java.net/browse/JDK-8196402 Testing: I launched jtreg jdk tests for Math.log: jdk/java/lang/Math/Log* I also launched jck tests for Math.log: All tests were launched both in Xcomp and Xmixed modes, using release and fastdebug builds. No failures found. Additional tests are not required because the algorithm is already present in hotspot for x86. Thanks, Dmitrij [1] Table-driven implementation of the logarithm function in IEEE floating-point arithmetic (https://dl.acm.org/citation.cfm?doid=98267.98294)

5 22

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

24 Jun '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/174… ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/may/23 pass: 3,868; fail: 37; error: 4; not run: 11,619 Build 1: aarch64/2018/may/25 pass: 5,209; fail: 45; error: 3; not run: 11,619 Build 2: aarch64/2018/may/27 pass: 5,210; fail: 43; error: 4; not run: 11,619 Build 3: aarch64/2018/may/29 pass: 5,209; fail: 44; error: 4; not run: 11,619 Build 4: aarch64/2018/jun/03 pass: 5,640; fail: 24; error: 5; not run: 11,619 Build 5: aarch64/2018/jun/05 pass: 5,642; fail: 25; error: 3; not run: 11,619 Build 6: aarch64/2018/jun/07 pass: 5,640; fail: 26; error: 4; not run: 11,619 Build 7: aarch64/2018/jun/09 pass: 5,654; fail: 25; error: 3; not run: 11,619 Build 8: aarch64/2018/jun/11 pass: 5,653; fail: 26; error: 3; not run: 11,619 Build 9: aarch64/2018/jun/13 pass: 5,674; fail: 24; error: 2; not run: 11,619 Build 10: aarch64/2018/jun/15 pass: 5,674; fail: 23; error: 2; not run: 11,619 Build 11: aarch64/2018/jun/17 pass: 5,698; fail: 23; error: 2; not run: 11,619 Build 12: aarch64/2018/jun/19 pass: 5,698; fail: 23; error: 2; not run: 11,619 Build 13: aarch64/2018/jun/21 pass: 5,700; fail: 23; error: 2; not run: 11,619 Build 14: aarch64/2018/jun/23 pass: 5,701; fail: 24; error: 1; not run: 11,619 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/may/23 pass: 8,328; fail: 610; error: 24 Build 1: aarch64/2018/may/25 pass: 8,302; fail: 638; error: 23 Build 2: aarch64/2018/may/27 pass: 8,331; fail: 611; error: 23 Build 3: aarch64/2018/may/29 pass: 8,320; fail: 616; error: 29 Build 4: aarch64/2018/jun/03 pass: 8,362; fail: 629; error: 25 Build 5: aarch64/2018/jun/05 pass: 8,395; fail: 599; error: 23 Build 6: aarch64/2018/jun/07 pass: 8,384; fail: 612; error: 24 Build 7: aarch64/2018/jun/09 pass: 8,388; fail: 614; error: 22 Build 8: aarch64/2018/jun/11 pass: 8,399; fail: 601; error: 24 Build 9: aarch64/2018/jun/13 pass: 8,435; fail: 576; error: 15 Build 10: aarch64/2018/jun/15 pass: 8,391; fail: 621; error: 16 Build 11: aarch64/2018/jun/17 pass: 8,423; fail: 594; error: 16 Build 12: aarch64/2018/jun/19 pass: 8,433; fail: 583; error: 17 Build 13: aarch64/2018/jun/21 pass: 8,428; fail: 630; error: 18 Build 14: aarch64/2018/jun/23 pass: 8,434; fail: 627; error: 20 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/may/23 pass: 3,871; fail: 6; error: 3 Build 1: aarch64/2018/may/25 pass: 3,877; fail: 6; error: 5 Build 2: aarch64/2018/may/27 pass: 3,880; fail: 6; error: 2 Build 3: aarch64/2018/may/29 pass: 3,879; fail: 6; error: 4 Build 4: aarch64/2018/jun/03 pass: 3,882; fail: 6; error: 3 Build 5: aarch64/2018/jun/05 pass: 3,884; fail: 6; error: 4 Build 6: aarch64/2018/jun/07 pass: 3,887; fail: 6; error: 3 Build 7: aarch64/2018/jun/09 pass: 3,887; fail: 6; error: 5 Build 8: aarch64/2018/jun/11 pass: 3,887; fail: 6; error: 5 Build 9: aarch64/2018/jun/13 pass: 3,891; fail: 6; error: 2 Build 10: aarch64/2018/jun/15 pass: 3,894; fail: 4; error: 4 Build 11: aarch64/2018/jun/17 pass: 3,893; fail: 4; error: 5 Build 12: aarch64/2018/jun/19 pass: 3,894; fail: 4; error: 5 Build 13: aarch64/2018/jun/21 pass: 3,899; fail: 4; error: 3 Build 14: aarch64/2018/jun/23 pass: 3,902; fail: 4 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/may/23 pass: 3,879; fail: 34; error: 3; not run: 11,619 Build 1: aarch64/2018/may/25 pass: 5,219; fail: 42; error: 3; not run: 11,619 Build 2: aarch64/2018/may/27 pass: 5,220; fail: 40; error: 4; not run: 11,619 Build 3: aarch64/2018/may/29 pass: 5,219; fail: 42; error: 3; not run: 11,619 Build 4: aarch64/2018/jun/03 pass: 5,651; fail: 22; error: 3; not run: 11,619 Build 5: aarch64/2018/jun/05 pass: 5,651; fail: 23; error: 3; not run: 11,619 Build 6: aarch64/2018/jun/07 pass: 5,650; fail: 24; error: 3; not run: 11,619 Build 7: aarch64/2018/jun/09 pass: 5,663; fail: 24; error: 2; not run: 11,619 Build 8: aarch64/2018/jun/11 pass: 5,664; fail: 23; error: 2; not run: 11,619 Build 9: aarch64/2018/jun/13 pass: 5,682; fail: 23; error: 2; not run: 11,619 Build 10: aarch64/2018/jun/15 pass: 5,681; fail: 23; error: 2; not run: 11,619 Build 11: aarch64/2018/jun/17 pass: 5,705; fail: 22; error: 3; not run: 11,619 Build 12: aarch64/2018/jun/19 pass: 5,705; fail: 23; error: 2; not run: 11,619 Build 13: aarch64/2018/jun/21 pass: 5,708; fail: 23; error: 1; not run: 11,619 Build 14: aarch64/2018/jun/23 pass: 5,707; fail: 25; error: 1; not run: 11,619 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/may/23 pass: 8,361; fail: 583; error: 19 Build 1: aarch64/2018/may/25 pass: 8,357; fail: 591; error: 16 Build 2: aarch64/2018/may/27 pass: 8,359; fail: 589; error: 18 Build 3: aarch64/2018/may/29 pass: 8,372; fail: 576; error: 18 Build 4: aarch64/2018/jun/03 pass: 8,379; fail: 618; error: 20 Build 5: aarch64/2018/jun/05 pass: 8,415; fail: 586; error: 17 Build 6: aarch64/2018/jun/07 pass: 8,382; fail: 622; error: 17 Build 7: aarch64/2018/jun/09 pass: 8,425; fail: 584; error: 16 Build 8: aarch64/2018/jun/11 pass: 8,416; fail: 592; error: 17 Build 9: aarch64/2018/jun/13 pass: 8,423; fail: 589; error: 15 Build 10: aarch64/2018/jun/15 pass: 8,420; fail: 590; error: 19 Build 11: aarch64/2018/jun/17 pass: 8,436; fail: 581; error: 17 Build 12: aarch64/2018/jun/19 pass: 8,432; fail: 585; error: 17 Build 13: aarch64/2018/jun/21 pass: 8,484; fail: 575; error: 18 Build 14: aarch64/2018/jun/23 pass: 8,454; fail: 613; error: 15 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/may/23 pass: 3,867; fail: 6; error: 7 Build 1: aarch64/2018/may/25 pass: 3,878; fail: 6; error: 4 Build 2: aarch64/2018/may/27 pass: 3,877; fail: 6; error: 5 Build 3: aarch64/2018/may/29 pass: 3,877; fail: 6; error: 6 Build 4: aarch64/2018/jun/03 pass: 3,884; fail: 6; error: 1 Build 5: aarch64/2018/jun/05 pass: 3,885; fail: 6; error: 3 Build 6: aarch64/2018/jun/07 pass: 3,887; fail: 6; error: 3 Build 7: aarch64/2018/jun/09 pass: 3,888; fail: 6; error: 4 Build 8: aarch64/2018/jun/11 pass: 3,886; fail: 6; error: 6 Build 9: aarch64/2018/jun/13 pass: 3,892; fail: 6; error: 1 Build 10: aarch64/2018/jun/15 pass: 3,894; fail: 4; error: 4 Build 11: aarch64/2018/jun/17 pass: 3,893; fail: 4; error: 5 Build 12: aarch64/2018/jun/19 pass: 3,894; fail: 4; error: 5 Build 13: aarch64/2018/jun/21 pass: 3,902; fail: 4 Build 14: aarch64/2018/jun/23 pass: 3,902; fail: 4 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.00x Relative performance: Server critical-jOPS (nc): 0.88x 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.52, Server: 116.65 Client 68.52 / Client 2014-04-01 (43.00): 1.59x Server 116.65 / Server 2014-04-01 (71.00): 1.64x 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-05-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/143/results/ 2018-05-26 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/145/results/ 2018-05-28 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/147/results/ 2018-05-31 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/149/results/ 2018-06-04 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/154/results/ 2018-06-06 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/156/results/ 2018-06-09 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/158/results/ 2018-06-10 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/160/results/ 2018-06-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/162/results/ 2018-06-15 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/164/results/ 2018-06-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/166/results/ 2018-06-19 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/168/results/ 2018-06-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/170/results/ 2018-06-22 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/172/results/ 2018-06-24 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/174/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 22 Jun '18

22 Jun '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/172… ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/may/21 pass: 3,769; fail: 38; error: 5; not run: 11,619 Build 1: aarch64/2018/may/23 pass: 3,868; fail: 37; error: 4; not run: 11,619 Build 2: aarch64/2018/may/25 pass: 5,209; fail: 45; error: 3; not run: 11,619 Build 3: aarch64/2018/may/27 pass: 5,210; fail: 43; error: 4; not run: 11,619 Build 4: aarch64/2018/may/29 pass: 5,209; fail: 44; error: 4; not run: 11,619 Build 5: aarch64/2018/jun/03 pass: 5,640; fail: 24; error: 5; not run: 11,619 Build 6: aarch64/2018/jun/05 pass: 5,642; fail: 25; error: 3; not run: 11,619 Build 7: aarch64/2018/jun/07 pass: 5,640; fail: 26; error: 4; not run: 11,619 Build 8: aarch64/2018/jun/09 pass: 5,654; fail: 25; error: 3; not run: 11,619 Build 9: aarch64/2018/jun/11 pass: 5,653; fail: 26; error: 3; not run: 11,619 Build 10: aarch64/2018/jun/13 pass: 5,674; fail: 24; error: 2; not run: 11,619 Build 11: aarch64/2018/jun/15 pass: 5,674; fail: 23; error: 2; not run: 11,619 Build 12: aarch64/2018/jun/17 pass: 5,698; fail: 23; error: 2; not run: 11,619 Build 13: aarch64/2018/jun/19 pass: 5,698; fail: 23; error: 2; not run: 11,619 Build 14: aarch64/2018/jun/21 pass: 5,700; fail: 23; error: 2; not run: 11,619 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/may/21 pass: 8,326; fail: 604; error: 25 Build 1: aarch64/2018/may/23 pass: 8,328; fail: 610; error: 24 Build 2: aarch64/2018/may/25 pass: 8,302; fail: 638; error: 23 Build 3: aarch64/2018/may/27 pass: 8,331; fail: 611; error: 23 Build 4: aarch64/2018/may/29 pass: 8,320; fail: 616; error: 29 Build 5: aarch64/2018/jun/03 pass: 8,362; fail: 629; error: 25 Build 6: aarch64/2018/jun/05 pass: 8,395; fail: 599; error: 23 Build 7: aarch64/2018/jun/07 pass: 8,384; fail: 612; error: 24 Build 8: aarch64/2018/jun/09 pass: 8,388; fail: 614; error: 22 Build 9: aarch64/2018/jun/11 pass: 8,399; fail: 601; error: 24 Build 10: aarch64/2018/jun/13 pass: 8,435; fail: 576; error: 15 Build 11: aarch64/2018/jun/15 pass: 8,391; fail: 621; error: 16 Build 12: aarch64/2018/jun/17 pass: 8,423; fail: 594; error: 16 Build 13: aarch64/2018/jun/19 pass: 8,433; fail: 583; error: 17 Build 14: aarch64/2018/jun/21 pass: 8,428; fail: 630; error: 18 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/may/21 pass: 3,867; fail: 6; error: 2 Build 1: aarch64/2018/may/23 pass: 3,871; fail: 6; error: 3 Build 2: aarch64/2018/may/25 pass: 3,877; fail: 6; error: 5 Build 3: aarch64/2018/may/27 pass: 3,880; fail: 6; error: 2 Build 4: aarch64/2018/may/29 pass: 3,879; fail: 6; error: 4 Build 5: aarch64/2018/jun/03 pass: 3,882; fail: 6; error: 3 Build 6: aarch64/2018/jun/05 pass: 3,884; fail: 6; error: 4 Build 7: aarch64/2018/jun/07 pass: 3,887; fail: 6; error: 3 Build 8: aarch64/2018/jun/09 pass: 3,887; fail: 6; error: 5 Build 9: aarch64/2018/jun/11 pass: 3,887; fail: 6; error: 5 Build 10: aarch64/2018/jun/13 pass: 3,891; fail: 6; error: 2 Build 11: aarch64/2018/jun/15 pass: 3,894; fail: 4; error: 4 Build 12: aarch64/2018/jun/17 pass: 3,893; fail: 4; error: 5 Build 13: aarch64/2018/jun/19 pass: 3,894; fail: 4; error: 5 Build 14: aarch64/2018/jun/21 pass: 3,899; fail: 4; error: 3 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/may/21 pass: 3,783; fail: 34; error: 2; not run: 11,619 Build 1: aarch64/2018/may/23 pass: 3,879; fail: 34; error: 3; not run: 11,619 Build 2: aarch64/2018/may/25 pass: 5,219; fail: 42; error: 3; not run: 11,619 Build 3: aarch64/2018/may/27 pass: 5,220; fail: 40; error: 4; not run: 11,619 Build 4: aarch64/2018/may/29 pass: 5,219; fail: 42; error: 3; not run: 11,619 Build 5: aarch64/2018/jun/03 pass: 5,651; fail: 22; error: 3; not run: 11,619 Build 6: aarch64/2018/jun/05 pass: 5,651; fail: 23; error: 3; not run: 11,619 Build 7: aarch64/2018/jun/07 pass: 5,650; fail: 24; error: 3; not run: 11,619 Build 8: aarch64/2018/jun/09 pass: 5,663; fail: 24; error: 2; not run: 11,619 Build 9: aarch64/2018/jun/11 pass: 5,664; fail: 23; error: 2; not run: 11,619 Build 10: aarch64/2018/jun/13 pass: 5,682; fail: 23; error: 2; not run: 11,619 Build 11: aarch64/2018/jun/15 pass: 5,681; fail: 23; error: 2; not run: 11,619 Build 12: aarch64/2018/jun/17 pass: 5,705; fail: 22; error: 3; not run: 11,619 Build 13: aarch64/2018/jun/19 pass: 5,705; fail: 23; error: 2; not run: 11,619 Build 14: aarch64/2018/jun/21 pass: 5,708; fail: 23; error: 1; not run: 11,619 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/may/21 pass: 8,363; fail: 578; error: 15 Build 1: aarch64/2018/may/23 pass: 8,361; fail: 583; error: 19 Build 2: aarch64/2018/may/25 pass: 8,357; fail: 591; error: 16 Build 3: aarch64/2018/may/27 pass: 8,359; fail: 589; error: 18 Build 4: aarch64/2018/may/29 pass: 8,372; fail: 576; error: 18 Build 5: aarch64/2018/jun/03 pass: 8,379; fail: 618; error: 20 Build 6: aarch64/2018/jun/05 pass: 8,415; fail: 586; error: 17 Build 7: aarch64/2018/jun/07 pass: 8,382; fail: 622; error: 17 Build 8: aarch64/2018/jun/09 pass: 8,425; fail: 584; error: 16 Build 9: aarch64/2018/jun/11 pass: 8,416; fail: 592; error: 17 Build 10: aarch64/2018/jun/13 pass: 8,423; fail: 589; error: 15 Build 11: aarch64/2018/jun/15 pass: 8,420; fail: 590; error: 19 Build 12: aarch64/2018/jun/17 pass: 8,436; fail: 581; error: 17 Build 13: aarch64/2018/jun/19 pass: 8,432; fail: 585; error: 17 Build 14: aarch64/2018/jun/21 pass: 8,484; fail: 575; error: 18 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/may/21 pass: 3,863; fail: 6; error: 6 Build 1: aarch64/2018/may/23 pass: 3,867; fail: 6; error: 7 Build 2: aarch64/2018/may/25 pass: 3,878; fail: 6; error: 4 Build 3: aarch64/2018/may/27 pass: 3,877; fail: 6; error: 5 Build 4: aarch64/2018/may/29 pass: 3,877; fail: 6; error: 6 Build 5: aarch64/2018/jun/03 pass: 3,884; fail: 6; error: 1 Build 6: aarch64/2018/jun/05 pass: 3,885; fail: 6; error: 3 Build 7: aarch64/2018/jun/07 pass: 3,887; fail: 6; error: 3 Build 8: aarch64/2018/jun/09 pass: 3,888; fail: 6; error: 4 Build 9: aarch64/2018/jun/11 pass: 3,886; fail: 6; error: 6 Build 10: aarch64/2018/jun/13 pass: 3,892; fail: 6; error: 1 Build 11: aarch64/2018/jun/15 pass: 3,894; fail: 4; error: 4 Build 12: aarch64/2018/jun/17 pass: 3,893; fail: 4; error: 5 Build 13: aarch64/2018/jun/19 pass: 3,894; fail: 4; error: 5 Build 14: aarch64/2018/jun/21 pass: 3,902; fail: 4 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): 0.60x Relative performance: Server critical-jOPS (nc): 0.56x 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: 65.96, Server: 109.42 Client 65.96 / Client 2014-04-01 (43.00): 1.53x Server 109.42 / Server 2014-04-01 (71.00): 1.54x 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-05-22 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/141/results/ 2018-05-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/143/results/ 2018-05-26 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/145/results/ 2018-05-28 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/147/results/ 2018-05-31 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/149/results/ 2018-06-04 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/154/results/ 2018-06-06 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/156/results/ 2018-06-09 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/158/results/ 2018-06-10 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/160/results/ 2018-06-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/162/results/ 2018-06-15 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/164/results/ 2018-06-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/166/results/ 2018-06-19 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/168/results/ 2018-06-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/170/results/ 2018-06-22 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/172/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/

1 0

Re: [aarch64-port-dev ] RFR: JDK-8205004: AArch64: fix failures in jtreg ArraysEqCmpTest
by Joshua Zhu 22 Jun '18

22 Jun '18

Hi Dmitrij, >> and label LEN_IS_ZERO and its path can also be deleted like below: >> bind(SHORT); >> cmp(cnt2, cnt1); >> br(NE, DONE); >> cbz(cnt1, SAME); >regarding LEN_IS_ZERO removal: we must keep it. Otherwise it'll compare >garbage memory later, because loaded data is shifted by lslv(tmp5, tmp4, >tmp5); to remove extra data. In case of 0 length, shift will be 0, so, a >memory after this particular array will be compared. It will not execute the instruction you mentioned, because my added instruction cbz(cnt1, SAME); will directly goto SAME path when cnt1 is zero. (no need to goto LEN_IS_ZERO to execute another compare and branch) Best Regards, Joshua

3 13