March 2017 - aarch64-port-dev

hg: aarch64-port/jdk8u-shenandoah: Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-03-23 for changeset 2a4586827492
by roman＠kennke.org 23 Mar '17

23 Mar '17

Changeset: 31d874083b9e Author: rkennke Date: 2017-03-23 18:23 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/31d874083b9e Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-03-23 for changeset 2a4586827492 ! .hgtags

1 0

hg: aarch64-port/jdk8u-shenandoah/hotspot: Import from Shenandoah tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-03-09
by roman＠kennke.org 23 Mar '17

23 Mar '17

Changeset: a748c134e756 Author: rkennke Date: 2017-03-23 17:38 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/a748c1… Import from Shenandoah tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-03-09 ! make/excludeSrc.make ! make/windows/makefiles/vm.make ! src/cpu/aarch64/vm/macroAssembler_aarch64.cpp ! src/cpu/aarch64/vm/shenandoahBarrierSet_aarch64.cpp ! src/cpu/aarch64/vm/stubGenerator_aarch64.cpp ! src/cpu/aarch64/vm/stubRoutines_aarch64.hpp ! src/cpu/x86/vm/macroAssembler_x86.cpp ! src/cpu/x86/vm/sharedRuntime_x86_64.cpp ! src/cpu/x86/vm/shenandoahBarrierSet_x86.cpp ! src/cpu/x86/vm/stubGenerator_x86_64.cpp ! src/cpu/x86/vm/stubRoutines_x86_64.hpp ! src/share/vm/asm/assembler.cpp ! src/share/vm/gc_implementation/shared/parallelCleaning.cpp ! src/share/vm/gc_implementation/shenandoah/brooksPointer.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahBarrierSet.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahBarrierSet.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahCollectionSet.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahCollectorPolicy.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahCollectorPolicy.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahConcurrentMark.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahConcurrentMark.inline.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahConcurrentThread.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahFreeSet.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.inline.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeapRegion.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeapRegion.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeapRegion.inline.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeapRegionCounters.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeapRegionSet.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeapRegionSet.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHumongous.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahMarkCompact.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahMonitoringSupport.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahPhaseTimes.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahTaskqueue.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahWorkGroup.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoah_globals.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoah_globals.hpp ! src/share/vm/gc_implementation/shenandoah/vm_operations_shenandoah.cpp ! src/share/vm/opto/shenandoahSupport.cpp ! src/share/vm/runtime/arguments.cpp ! src/share/vm/runtime/init.cpp ! src/share/vm/runtime/stubRoutines.cpp ! src/share/vm/runtime/stubRoutines.hpp ! src/share/vm/services/shenandoahMemoryPool.cpp

1 0

RFR: Merge from Shenandoah JDK8u since 2017-03-09
by Roman Kennke 23 Mar '17

23 Mar '17

This merges all changesets from Shenandoah's jdk8u repository since 2017-03-09. It's all build fixes for i586 and Windows 64 builds. http://cr.openjdk.java.net/~rkennke/merge-2017-03-23/webrev.00/ <http://cr.openjdk.java.net/%7Erkennke/merge-2017-03-23/webrev.00/> I'll also tag it with aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-03-23 Ok? Roman

2 1

JDK-8177390: java -version does not differentiate between which port of AArch64 is used
by Mario Torre 23 Mar '17

23 Mar '17

Hi all, [Sorry for cross posting to the aarch64 mailing list, please try to keep all replies to jdk9-dev] I have a proposed fix for JDK-8177390[1]. The whole issue can be seen in details on the aarch64-port-dev thread linked in the bug report[2], but to summarise, we now have two implementations for the aarch64, one is the "original" community contribution and the other is the Oracle version that landed recently in the repositories. The two versions can be build side by side, which is great since users can compare very easily the two implementations, have a feeling of the performances, study the differences in the implementations etc... however, once compiled there is no easy way to tell which one is which, unless you are using the downstream packaged versions, where the name of the JDK may offer a small hint. This is more than just an annoyance, though, it will make life extremely difficult for bug reporting and hunting, and the hotspot crash files may not help either, so we think this should be fixed asap (and the reason why I filed the bug report with a priority a bit higher than usual). It was suggested to play with one of the java.vendor strings to address this, so I'm proposing a patch to alter the java.vendor.url to point to either the usual java.oracle.com or to the aarg64 project page, depending on the choice of the port at compilation time: http://cr.openjdk.java.net/~neugens/8177390/webrev.1/ We would really like to have this patch in before the JDK9 is released, I understand that we need to seek guidance from project leads for that to happen at this stage of development. The patch was taken on the jdk9 client repository, I'm not sure if I will also need to push separately to 10 or if this will be an automatic forward port. Please, let me know what you think. Cheers, Mario [1] https://bugs.openjdk.java.net/browse/JDK-8177390 [2] http://mail.openjdk.java.net/pipermail/aarch64-port-dev/2017-March/004319.h…

1 0

JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64
by ci_notify＠linaro.org 22 Mar '17

22 Mar '17

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/jdk9/openjdk-jtreg-nightly-tests/summary/2017/080… ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/02 pass: 1,358; fail: 10; error: 9 Build 1: aarch64/2017/feb/21 pass: 1,378; fail: 4 Build 2: aarch64/2017/feb/22 pass: 1,378; fail: 4 Build 3: aarch64/2017/feb/25 pass: 1,386; fail: 5 Build 4: aarch64/2017/feb/28 pass: 1,386; fail: 5 Build 5: aarch64/2017/mar/01 pass: 1,387; fail: 5 Build 6: aarch64/2017/mar/02 pass: 1,387; fail: 5 Build 7: aarch64/2017/mar/03 pass: 1,387; fail: 5 Build 8: aarch64/2017/mar/08 pass: 1,388; fail: 5 Build 9: aarch64/2017/mar/11 pass: 1,388; fail: 5 Build 10: aarch64/2017/mar/13 pass: 1,388; fail: 5 Build 11: aarch64/2017/mar/15 pass: 1,387; fail: 6 Build 12: aarch64/2017/mar/17 pass: 1,390; fail: 6 Build 13: aarch64/2017/mar/19 pass: 1,391; fail: 5 Build 14: aarch64/2017/mar/21 pass: 1,391; fail: 5 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/02 pass: 7,294; fail: 622; error: 28 Build 1: aarch64/2017/feb/21 pass: 7,224; fail: 715; error: 20 Build 2: aarch64/2017/feb/22 pass: 7,226; fail: 714; error: 19 Build 3: aarch64/2017/feb/25 pass: 7,266; fail: 705; error: 20 Build 4: aarch64/2017/feb/28 pass: 7,274; fail: 695; error: 23 Build 5: aarch64/2017/mar/01 pass: 7,264; fail: 711; error: 17 Build 6: aarch64/2017/mar/02 pass: 7,272; fail: 705; error: 15 Build 7: aarch64/2017/mar/03 pass: 7,252; fail: 720; error: 21 Build 8: aarch64/2017/mar/08 pass: 7,251; fail: 720; error: 23 Build 9: aarch64/2017/mar/11 pass: 7,263; fail: 718; error: 18 Build 10: aarch64/2017/mar/13 pass: 7,268; fail: 710; error: 21 Build 11: aarch64/2017/mar/15 pass: 7,283; fail: 693; error: 25 Build 12: aarch64/2017/mar/17 pass: 7,273; fail: 709; error: 20 Build 13: aarch64/2017/mar/19 pass: 7,253; fail: 727; error: 24 Build 14: aarch64/2017/mar/21 pass: 7,294; fail: 689; error: 21 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/02 pass: 3,815; fail: 17; error: 10 Build 1: aarch64/2017/feb/21 pass: 3,861 Build 2: aarch64/2017/feb/22 pass: 3,859; error: 2 Build 3: aarch64/2017/feb/25 pass: 3,859; error: 4 Build 4: aarch64/2017/feb/28 pass: 3,861; error: 2 Build 5: aarch64/2017/mar/01 pass: 3,862; error: 2 Build 6: aarch64/2017/mar/02 pass: 3,862; error: 2 Build 7: aarch64/2017/mar/03 pass: 3,863; error: 2 Build 8: aarch64/2017/mar/08 pass: 3,866; error: 1 Build 9: aarch64/2017/mar/11 pass: 3,871; error: 2 Build 10: aarch64/2017/mar/13 pass: 3,872; error: 1 Build 11: aarch64/2017/mar/15 pass: 3,874; error: 4 Build 12: aarch64/2017/mar/17 pass: 3,878; error: 2 Build 13: aarch64/2017/mar/19 pass: 3,878; error: 2 Build 14: aarch64/2017/mar/21 pass: 3,876; error: 5 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/02 pass: 1,273; fail: 61; error: 9 Build 1: aarch64/2017/feb/21 pass: 1,380; fail: 5 Build 2: aarch64/2017/feb/22 pass: 1,378; fail: 6; error: 1 Build 3: aarch64/2017/feb/25 pass: 1,389; fail: 5 Build 4: aarch64/2017/feb/28 pass: 1,388; fail: 6 Build 5: aarch64/2017/mar/01 pass: 1,390; fail: 5 Build 6: aarch64/2017/mar/02 pass: 1,390; fail: 5 Build 7: aarch64/2017/mar/03 pass: 1,390; fail: 5 Build 8: aarch64/2017/mar/08 pass: 1,391; fail: 6 Build 9: aarch64/2017/mar/11 pass: 1,392; fail: 5 Build 10: aarch64/2017/mar/13 pass: 1,392; fail: 5 Build 11: aarch64/2017/mar/15 pass: 1,392; fail: 5 Build 12: aarch64/2017/mar/17 pass: 1,395; fail: 5 Build 13: aarch64/2017/mar/19 pass: 1,395; fail: 5 Build 14: aarch64/2017/mar/21 pass: 1,394; fail: 6 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/02 pass: 7,282; fail: 641; error: 21 Build 1: aarch64/2017/feb/21 pass: 7,223; fail: 718; error: 18 Build 2: aarch64/2017/feb/22 pass: 7,235; fail: 707; error: 17 Build 3: aarch64/2017/feb/25 pass: 7,279; fail: 694; error: 18 Build 4: aarch64/2017/feb/28 pass: 7,265; fail: 708; error: 19 Build 5: aarch64/2017/mar/01 pass: 7,266; fail: 710; error: 16 Build 6: aarch64/2017/mar/02 pass: 7,284; fail: 689; error: 19 Build 7: aarch64/2017/mar/03 pass: 7,257; fail: 720; error: 16 Build 8: aarch64/2017/mar/08 pass: 7,296; fail: 679; error: 19 Build 9: aarch64/2017/mar/11 pass: 7,261; fail: 722; error: 16 Build 10: aarch64/2017/mar/13 pass: 7,290; fail: 687; error: 22 Build 11: aarch64/2017/mar/15 pass: 7,285; fail: 697; error: 19 Build 12: aarch64/2017/mar/17 pass: 7,278; fail: 703; error: 21 Build 13: aarch64/2017/mar/19 pass: 7,261; fail: 723; error: 20 Build 14: aarch64/2017/mar/21 pass: 7,271; fail: 712; error: 21 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/02 pass: 3,834; error: 8 Build 1: aarch64/2017/feb/21 pass: 3,859; error: 2 Build 2: aarch64/2017/feb/22 pass: 3,858; error: 3 Build 3: aarch64/2017/feb/25 pass: 3,860; error: 3 Build 4: aarch64/2017/feb/28 pass: 3,862; error: 1 Build 5: aarch64/2017/mar/01 pass: 3,860; error: 4 Build 6: aarch64/2017/mar/02 pass: 3,858; fail: 1; error: 5 Build 7: aarch64/2017/mar/03 pass: 3,863; fail: 1; error: 2 Build 8: aarch64/2017/mar/08 pass: 3,867 Build 9: aarch64/2017/mar/11 pass: 3,873 Build 10: aarch64/2017/mar/13 pass: 3,871; error: 2 Build 11: aarch64/2017/mar/15 pass: 3,878 Build 12: aarch64/2017/mar/17 pass: 3,876; error: 4 Build 13: aarch64/2017/mar/19 pass: 3,876; error: 4 Build 14: aarch64/2017/mar/21 pass: 3,879; error: 2 Previous results can be found here: http://openjdk.linaro.org/jdk9/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.82x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk9/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: 70.93, Server: 110.27 Client 70.93 / Client 2014-04-01 (43.00): 1.65x 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/jdk9/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2017-02-05 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/033/results/ 2017-02-22 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/052/results/ 2017-02-23 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/053/results/ 2017-02-26 pass rate: 6300/6302, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/056/results/ 2017-03-01 pass rate: 6300/6303, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/059/results/ 2017-03-02 pass rate: 10525/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/060/results/ 2017-03-03 pass rate: 10525/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/061/results/ 2017-03-05 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/062/results/ 2017-03-09 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/067/results/ 2017-03-12 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/070/results/ 2017-03-14 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/072/results/ 2017-03-16 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/074/results/ 2017-03-18 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/076/results/ 2017-03-20 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/078/results/ 2017-03-22 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/080/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/

2 1

AArch64 register usage questions
by White, Derek 21 Mar '17

21 Mar '17

Hi, I've been looking at the aarch64 port's register usage, and compared against Oracle's arm port, and have a few questions and observations: Comparing the enum in c1_defs_aarch54.hpp vs. the enum in the arm code (and doing some constant folding by hand), you get: ARM32/64 AArch64 Notes pd_nof_cpu_regs_frame_map 33 32 number of registers used during code emission pd_nof_caller_save_cpu_regs_frame_map 27 17 number of registers killed by calls pd_nof_cpu_regs_reg_alloc 27 17 number of registers that are visible to register allocator () pd_nof_cpu_regs_linearscan 33 32 number of registers visible to linear scan pd_nof_cpu_regs_processed_in_linearscan 28 -0 number of registers processed in linear scan; includes LR (in arm prt) pd_first_cpu_reg 0 0 pd_last_cpu_reg 32 16 pd_first_callee_saved_reg -0 17 pd_last_callee_saved_reg -0 24 pd_last_allocatable_cpu_reg -0 16 pd_first_byte_reg -0 0 unused! pd_last_byte_reg -0 16 unused, except by unused last_byte_reg(). pd_nof_fpu_regs_frame_map 32 32 number of float registers used during code emission pd_nof_caller_save_fpu_regs_frame_map 32 32 number of float registers killed by calls pd_nof_fpu_regs_reg_alloc 32 8 number of float registers that are visible to register allocator pd_nof_fpu_regs_linearscan 32 32 number of float registers visible to linear scan pd_first_fpu_reg 33 32 '= pd_nof_cpu_regs_frame_map, pd_last_fpu_reg 64 63 pd_first_callee_saved_fpu_reg -0 40 pd_last_callee_saved_fpu_reg -0 47 pd_nof_xmm_regs_linearscan 0 0 pd_nof_caller_save_xmm_regs 0 -0 pd_first_xmm_reg -1 -0 pd_last_xmm_reg -1 -0 I don't expect these values to match, but some items stand out: - AArch64 has fewer caller-saves registers, but more callee-saves registers defined above. o But the Aarch64 code has comments like: // FIXME: There are no callee-saved. o And C2 does not define any SOE registers. o Is C1 using few registers than it could? Than it should? o And/or is C2? o There are other comments, such as above generate_call_stub(), that says: ? // we don't need to save r16-18 because Java does not use them ? The comment says r16, but doesn't seem to match pd_first_callee_saved_reg. ? I don't see where r18 came from. - pd_first_byte_reg, pd_last_byte_reg and last_byte_reg() seem unused. Looking at the register definitions in aarch64.ad and other places: - Aarch64 always allocates r27 to use for compressed oops (rheapbase). Arm32/64 only allocates the register if CompressedOops is enabled. o In one sense the Aarch64 approach seems reasonable. I think the default setting for CompressedOops will be true until heap sizes get huge (e.g. somewhere past 256GB.), so there may not be much reason to optimize the non-CompressedOops path. o If we really wanted to use r27 for compiled code, we could probably only allocate r27 for rheapbase if (Universe::narrow_oop_base() != NULL). Thanks for any thoughts you might have... - Derek

2 2

JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64
by ci_notify＠linaro.org 20 Mar '17

20 Mar '17

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/jdk9/openjdk-jtreg-nightly-tests/summary/2017/078… ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/01 pass: 1,359; fail: 11; error: 7 Build 1: aarch64/2017/feb/02 pass: 1,358; fail: 10; error: 9 Build 2: aarch64/2017/feb/21 pass: 1,378; fail: 4 Build 3: aarch64/2017/feb/22 pass: 1,378; fail: 4 Build 4: aarch64/2017/feb/25 pass: 1,386; fail: 5 Build 5: aarch64/2017/feb/28 pass: 1,386; fail: 5 Build 6: aarch64/2017/mar/01 pass: 1,387; fail: 5 Build 7: aarch64/2017/mar/02 pass: 1,387; fail: 5 Build 8: aarch64/2017/mar/03 pass: 1,387; fail: 5 Build 9: aarch64/2017/mar/08 pass: 1,388; fail: 5 Build 10: aarch64/2017/mar/11 pass: 1,388; fail: 5 Build 11: aarch64/2017/mar/13 pass: 1,388; fail: 5 Build 12: aarch64/2017/mar/15 pass: 1,387; fail: 6 Build 13: aarch64/2017/mar/17 pass: 1,390; fail: 6 Build 14: aarch64/2017/mar/19 pass: 1,391; fail: 5 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/01 pass: 7,278; fail: 643; error: 23 Build 1: aarch64/2017/feb/02 pass: 7,294; fail: 622; error: 28 Build 2: aarch64/2017/feb/21 pass: 7,224; fail: 715; error: 20 Build 3: aarch64/2017/feb/22 pass: 7,226; fail: 714; error: 19 Build 4: aarch64/2017/feb/25 pass: 7,266; fail: 705; error: 20 Build 5: aarch64/2017/feb/28 pass: 7,274; fail: 695; error: 23 Build 6: aarch64/2017/mar/01 pass: 7,264; fail: 711; error: 17 Build 7: aarch64/2017/mar/02 pass: 7,272; fail: 705; error: 15 Build 8: aarch64/2017/mar/03 pass: 7,252; fail: 720; error: 21 Build 9: aarch64/2017/mar/08 pass: 7,251; fail: 720; error: 23 Build 10: aarch64/2017/mar/11 pass: 7,263; fail: 718; error: 18 Build 11: aarch64/2017/mar/13 pass: 7,268; fail: 710; error: 21 Build 12: aarch64/2017/mar/15 pass: 7,283; fail: 693; error: 25 Build 13: aarch64/2017/mar/17 pass: 7,273; fail: 709; error: 20 Build 14: aarch64/2017/mar/19 pass: 7,253; fail: 727; error: 24 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/01 pass: 3,825; fail: 6; error: 10 Build 1: aarch64/2017/feb/02 pass: 3,815; fail: 17; error: 10 Build 2: aarch64/2017/feb/21 pass: 3,861 Build 3: aarch64/2017/feb/22 pass: 3,859; error: 2 Build 4: aarch64/2017/feb/25 pass: 3,859; error: 4 Build 5: aarch64/2017/feb/28 pass: 3,861; error: 2 Build 6: aarch64/2017/mar/01 pass: 3,862; error: 2 Build 7: aarch64/2017/mar/02 pass: 3,862; error: 2 Build 8: aarch64/2017/mar/03 pass: 3,863; error: 2 Build 9: aarch64/2017/mar/08 pass: 3,866; error: 1 Build 10: aarch64/2017/mar/11 pass: 3,871; error: 2 Build 11: aarch64/2017/mar/13 pass: 3,872; error: 1 Build 12: aarch64/2017/mar/15 pass: 3,874; error: 4 Build 13: aarch64/2017/mar/17 pass: 3,878; error: 2 Build 14: aarch64/2017/mar/19 pass: 3,878; error: 2 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/01 pass: 1,358; fail: 13; error: 9 Build 1: aarch64/2017/feb/02 pass: 1,273; fail: 61; error: 9 Build 2: aarch64/2017/feb/21 pass: 1,380; fail: 5 Build 3: aarch64/2017/feb/22 pass: 1,378; fail: 6; error: 1 Build 4: aarch64/2017/feb/25 pass: 1,389; fail: 5 Build 5: aarch64/2017/feb/28 pass: 1,388; fail: 6 Build 6: aarch64/2017/mar/01 pass: 1,390; fail: 5 Build 7: aarch64/2017/mar/02 pass: 1,390; fail: 5 Build 8: aarch64/2017/mar/03 pass: 1,390; fail: 5 Build 9: aarch64/2017/mar/08 pass: 1,391; fail: 6 Build 10: aarch64/2017/mar/11 pass: 1,392; fail: 5 Build 11: aarch64/2017/mar/13 pass: 1,392; fail: 5 Build 12: aarch64/2017/mar/15 pass: 1,392; fail: 5 Build 13: aarch64/2017/mar/17 pass: 1,395; fail: 5 Build 14: aarch64/2017/mar/19 pass: 1,395; fail: 5 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/01 pass: 7,293; fail: 626; error: 25 Build 1: aarch64/2017/feb/02 pass: 7,282; fail: 641; error: 21 Build 2: aarch64/2017/feb/21 pass: 7,223; fail: 718; error: 18 Build 3: aarch64/2017/feb/22 pass: 7,235; fail: 707; error: 17 Build 4: aarch64/2017/feb/25 pass: 7,279; fail: 694; error: 18 Build 5: aarch64/2017/feb/28 pass: 7,265; fail: 708; error: 19 Build 6: aarch64/2017/mar/01 pass: 7,266; fail: 710; error: 16 Build 7: aarch64/2017/mar/02 pass: 7,284; fail: 689; error: 19 Build 8: aarch64/2017/mar/03 pass: 7,257; fail: 720; error: 16 Build 9: aarch64/2017/mar/08 pass: 7,296; fail: 679; error: 19 Build 10: aarch64/2017/mar/11 pass: 7,261; fail: 722; error: 16 Build 11: aarch64/2017/mar/13 pass: 7,290; fail: 687; error: 22 Build 12: aarch64/2017/mar/15 pass: 7,285; fail: 697; error: 19 Build 13: aarch64/2017/mar/17 pass: 7,278; fail: 703; error: 21 Build 14: aarch64/2017/mar/19 pass: 7,261; fail: 723; error: 20 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/01 pass: 3,826; fail: 6; error: 9 Build 1: aarch64/2017/feb/02 pass: 3,834; error: 8 Build 2: aarch64/2017/feb/21 pass: 3,859; error: 2 Build 3: aarch64/2017/feb/22 pass: 3,858; error: 3 Build 4: aarch64/2017/feb/25 pass: 3,860; error: 3 Build 5: aarch64/2017/feb/28 pass: 3,862; error: 1 Build 6: aarch64/2017/mar/01 pass: 3,860; error: 4 Build 7: aarch64/2017/mar/02 pass: 3,858; fail: 1; error: 5 Build 8: aarch64/2017/mar/03 pass: 3,863; fail: 1; error: 2 Build 9: aarch64/2017/mar/08 pass: 3,867 Build 10: aarch64/2017/mar/11 pass: 3,873 Build 11: aarch64/2017/mar/13 pass: 3,871; error: 2 Build 12: aarch64/2017/mar/15 pass: 3,878 Build 13: aarch64/2017/mar/17 pass: 3,876; error: 4 Build 14: aarch64/2017/mar/19 pass: 3,876; error: 4 Previous results can be found here: http://openjdk.linaro.org/jdk9/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.87x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk9/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: 72.38, Server: 104.56 Client 72.38 / Client 2014-04-01 (43.00): 1.68x Server 104.56 / Server 2014-04-01 (71.00): 1.47x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk9/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2017-02-03 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/032/results/ 2017-02-05 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/033/results/ 2017-02-22 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/052/results/ 2017-02-23 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/053/results/ 2017-02-26 pass rate: 6300/6302, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/056/results/ 2017-03-01 pass rate: 6300/6303, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/059/results/ 2017-03-02 pass rate: 10525/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/060/results/ 2017-03-03 pass rate: 10525/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/061/results/ 2017-03-05 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/062/results/ 2017-03-09 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/067/results/ 2017-03-12 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/070/results/ 2017-03-14 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/072/results/ 2017-03-16 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/074/results/ 2017-03-18 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/076/results/ 2017-03-20 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/078/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/

1 0

Fireside chat - Thursday
by Stuart Monteith 20 Mar '17

20 Mar '17

Hello, I has been a long time since our last fireside chat, so I'm proposing we have one this Thursday. This week we'll be having a fireside chat on Thursday at 1600 UTC, 1600 GMT, 1200 EDT, 0900 PDT. In order to join in, please join the chat at Bluejeans here: https://bluejeans.com/791239268 Alternatively you may dial in using one of the following numbers http://bluejeans.com/numbers and enter the Meeting ID: 791239268 Please do not use any of the 'freefone' numbers, because although they may be free for you they cost us $$$$. Best Regards, Stuart

1 0

Re: [aarch64-port-dev ] OpenJDK builds fails on AARCH64 with Ubuntu 1604
by White, Derek 20 Mar '17

20 Mar '17

Hi Andrew, I didn't see a code change here. Did the compiler change on Jenkins? Can you report the gcc version used? Could also be change in compiler warning maybe-uninitialized (but I couldn't find one). For reference, within this function we have C++ code: ... bool need_mem_bar; switch (kind) { case Relaxed: need_mem_bar = mismatched || can_access_non_heap; break; case Opaque: // Opaque uses CPUOrder membars for protection against code movement. case Acquire: case Release: case Volatile: need_mem_bar = true; break; default: ShouldNotReachHere(); // I thought this was a "noreturn" function, but it's not... } ... if (need_mem_bar) insert_mem_bar(Op_MemBarCPUOrder); - Derek From: Pinski, Andrew Sent: Friday, March 17, 2017 5:36 PM To: aarch64-port-dev(a)openjdk.java.net Cc: White, Derek <Derek.White(a)cavium.com> Subject: OpenJDK builds fails on AARCH64 with Ubuntu 1604 Hi, The current build of OpenJDK v9 fails on aarch64-linux-gnu. I don't know who else to write this to so I thought this is the correct place to report build failures. This started to fail on March 15, 2017. Thanks, Andrew Pinski Log: /home/jenkins/workspace/BuildOpenJDK/hs/hotspot/src/share/vm/opto/library_call.cpp: In member function 'bool LibraryCallKit::inline_unsafe_access(bool, BasicType, LibraryCallKit::AccessKind, bool)': /home/jenkins/workspace/BuildOpenJDK/hs/hotspot/src/share/vm/opto/library_call.cpp:2577:3: error: 'need_mem_bar' may be used uninitialized in this function [-Werror=maybe-uninitialized] if (need_mem_bar) insert_mem_bar(Op_MemBarCPUOrder); ^ Creating support/modules_libs/java.base/jrt-fs.jar Note: /home/jenkins/workspace/BuildOpenJDK/hs/corba/src/java.corba/share/classes/com/sun/tools/corba/se/idl/som/idlemit/MetaPragma.java uses or overrides a deprecated API. Note: Recompile with -Xlint:deprecation for details. Note: Some input files use unchecked or unsafe operations. Note: Recompile with -Xlint:unchecked for details. cc1plus: all warnings being treated as errors lib/CompileJvm.gmk:201: recipe for target '/home/jenkins/workspace/BuildOpenJDK/hs/build/linux-aarch64-normal-server-release/hotspot/variant-server/libjvm/objs/library_call.o' failed make[3]: *** [/home/jenkins/workspace/BuildOpenJDK/hs/build/linux-aarch64-normal-server-release/hotspot/variant-server/libjvm/objs/library_call.o] Error 1 make[3]: *** Waiting for unfinished jobs....

3 3

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

18 Mar '17

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/jdk9/openjdk-jtreg-nightly-tests/summary/2017/076… ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/31 pass: 1,364; fail: 5; error: 8 Build 1: aarch64/2017/feb/01 pass: 1,359; fail: 11; error: 7 Build 2: aarch64/2017/feb/02 pass: 1,358; fail: 10; error: 9 Build 3: aarch64/2017/feb/21 pass: 1,378; fail: 4 Build 4: aarch64/2017/feb/22 pass: 1,378; fail: 4 Build 5: aarch64/2017/feb/25 pass: 1,386; fail: 5 Build 6: aarch64/2017/feb/28 pass: 1,386; fail: 5 Build 7: aarch64/2017/mar/01 pass: 1,387; fail: 5 Build 8: aarch64/2017/mar/02 pass: 1,387; fail: 5 Build 9: aarch64/2017/mar/03 pass: 1,387; fail: 5 Build 10: aarch64/2017/mar/08 pass: 1,388; fail: 5 Build 11: aarch64/2017/mar/11 pass: 1,388; fail: 5 Build 12: aarch64/2017/mar/13 pass: 1,388; fail: 5 Build 13: aarch64/2017/mar/15 pass: 1,387; fail: 6 Build 14: aarch64/2017/mar/17 pass: 1,390; fail: 6 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/31 pass: 7,292; fail: 620; error: 29 Build 1: aarch64/2017/feb/01 pass: 7,278; fail: 643; error: 23 Build 2: aarch64/2017/feb/02 pass: 7,294; fail: 622; error: 28 Build 3: aarch64/2017/feb/21 pass: 7,224; fail: 715; error: 20 Build 4: aarch64/2017/feb/22 pass: 7,226; fail: 714; error: 19 Build 5: aarch64/2017/feb/25 pass: 7,266; fail: 705; error: 20 Build 6: aarch64/2017/feb/28 pass: 7,274; fail: 695; error: 23 Build 7: aarch64/2017/mar/01 pass: 7,264; fail: 711; error: 17 Build 8: aarch64/2017/mar/02 pass: 7,272; fail: 705; error: 15 Build 9: aarch64/2017/mar/03 pass: 7,252; fail: 720; error: 21 Build 10: aarch64/2017/mar/08 pass: 7,251; fail: 720; error: 23 Build 11: aarch64/2017/mar/11 pass: 7,263; fail: 718; error: 18 Build 12: aarch64/2017/mar/13 pass: 7,268; fail: 710; error: 21 Build 13: aarch64/2017/mar/15 pass: 7,283; fail: 693; error: 25 Build 14: aarch64/2017/mar/17 pass: 7,273; fail: 709; error: 20 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/31 pass: 3,827; fail: 2; error: 9 Build 1: aarch64/2017/feb/01 pass: 3,825; fail: 6; error: 10 Build 2: aarch64/2017/feb/02 pass: 3,815; fail: 17; error: 10 Build 3: aarch64/2017/feb/21 pass: 3,861 Build 4: aarch64/2017/feb/22 pass: 3,859; error: 2 Build 5: aarch64/2017/feb/25 pass: 3,859; error: 4 Build 6: aarch64/2017/feb/28 pass: 3,861; error: 2 Build 7: aarch64/2017/mar/01 pass: 3,862; error: 2 Build 8: aarch64/2017/mar/02 pass: 3,862; error: 2 Build 9: aarch64/2017/mar/03 pass: 3,863; error: 2 Build 10: aarch64/2017/mar/08 pass: 3,866; error: 1 Build 11: aarch64/2017/mar/11 pass: 3,871; error: 2 Build 12: aarch64/2017/mar/13 pass: 3,872; error: 1 Build 13: aarch64/2017/mar/15 pass: 3,874; error: 4 Build 14: aarch64/2017/mar/17 pass: 3,878; error: 2 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/31 pass: 1,364; fail: 7; error: 9 Build 1: aarch64/2017/feb/01 pass: 1,358; fail: 13; error: 9 Build 2: aarch64/2017/feb/02 pass: 1,273; fail: 61; error: 9 Build 3: aarch64/2017/feb/21 pass: 1,380; fail: 5 Build 4: aarch64/2017/feb/22 pass: 1,378; fail: 6; error: 1 Build 5: aarch64/2017/feb/25 pass: 1,389; fail: 5 Build 6: aarch64/2017/feb/28 pass: 1,388; fail: 6 Build 7: aarch64/2017/mar/01 pass: 1,390; fail: 5 Build 8: aarch64/2017/mar/02 pass: 1,390; fail: 5 Build 9: aarch64/2017/mar/03 pass: 1,390; fail: 5 Build 10: aarch64/2017/mar/08 pass: 1,391; fail: 6 Build 11: aarch64/2017/mar/11 pass: 1,392; fail: 5 Build 12: aarch64/2017/mar/13 pass: 1,392; fail: 5 Build 13: aarch64/2017/mar/15 pass: 1,392; fail: 5 Build 14: aarch64/2017/mar/17 pass: 1,395; fail: 5 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/31 pass: 7,258; fail: 613; error: 50 Build 1: aarch64/2017/feb/01 pass: 7,293; fail: 626; error: 25 Build 2: aarch64/2017/feb/02 pass: 7,282; fail: 641; error: 21 Build 3: aarch64/2017/feb/21 pass: 7,223; fail: 718; error: 18 Build 4: aarch64/2017/feb/22 pass: 7,235; fail: 707; error: 17 Build 5: aarch64/2017/feb/25 pass: 7,279; fail: 694; error: 18 Build 6: aarch64/2017/feb/28 pass: 7,265; fail: 708; error: 19 Build 7: aarch64/2017/mar/01 pass: 7,266; fail: 710; error: 16 Build 8: aarch64/2017/mar/02 pass: 7,284; fail: 689; error: 19 Build 9: aarch64/2017/mar/03 pass: 7,257; fail: 720; error: 16 Build 10: aarch64/2017/mar/08 pass: 7,296; fail: 679; error: 19 Build 11: aarch64/2017/mar/11 pass: 7,261; fail: 722; error: 16 Build 12: aarch64/2017/mar/13 pass: 7,290; fail: 687; error: 22 Build 13: aarch64/2017/mar/15 pass: 7,285; fail: 697; error: 19 Build 14: aarch64/2017/mar/17 pass: 7,278; fail: 703; error: 21 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/jan/31 pass: 3,830; fail: 1; error: 7 Build 1: aarch64/2017/feb/01 pass: 3,826; fail: 6; error: 9 Build 2: aarch64/2017/feb/02 pass: 3,834; error: 8 Build 3: aarch64/2017/feb/21 pass: 3,859; error: 2 Build 4: aarch64/2017/feb/22 pass: 3,858; error: 3 Build 5: aarch64/2017/feb/25 pass: 3,860; error: 3 Build 6: aarch64/2017/feb/28 pass: 3,862; error: 1 Build 7: aarch64/2017/mar/01 pass: 3,860; error: 4 Build 8: aarch64/2017/mar/02 pass: 3,858; fail: 1; error: 5 Build 9: aarch64/2017/mar/03 pass: 3,863; fail: 1; error: 2 Build 10: aarch64/2017/mar/08 pass: 3,867 Build 11: aarch64/2017/mar/11 pass: 3,873 Build 12: aarch64/2017/mar/13 pass: 3,871; error: 2 Build 13: aarch64/2017/mar/15 pass: 3,878 Build 14: aarch64/2017/mar/17 pass: 3,876; error: 4 Previous results can be found here: http://openjdk.linaro.org/jdk9/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.75x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk9/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: 70.93, Server: 106.93 Client 70.93 / Client 2014-04-01 (43.00): 1.65x Server 106.93 / Server 2014-04-01 (71.00): 1.51x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk9/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2017-02-02 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/031/results/ 2017-02-03 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/032/results/ 2017-02-05 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/033/results/ 2017-02-22 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/052/results/ 2017-02-23 pass rate: 6050/6050, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/053/results/ 2017-02-26 pass rate: 6300/6302, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/056/results/ 2017-03-01 pass rate: 6300/6303, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/059/results/ 2017-03-02 pass rate: 10525/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/060/results/ 2017-03-03 pass rate: 10525/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/061/results/ 2017-03-05 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/062/results/ 2017-03-09 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/067/results/ 2017-03-12 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/070/results/ 2017-03-14 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/072/results/ 2017-03-16 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/074/results/ 2017-03-18 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/076/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/

1 0