April 2019 - aarch64-port-dev

RFR: 8218748: AARCH64: String::compareTo intrinsic documentation and maintenance improvement
by Dmitrij Pochepko 18 Nov '19

18 Nov '19

Hi all. Please review an enhancement change "8218748: AARCH64: String::compareTo intrinsic documentation and maintenance improvement". RFE: https://bugs.openjdk.java.net/browse/JDK-8218748 webrev: http://cr.openjdk.java.net/~dpochepk/8218748/webrev/ Changes: - Added documentation for compareTo implementation. - Removed duplicated code and using existing code instead. -- compare_string_16_bytes_same is used for tail handling in generate_compare_long_string_same_encoding . -- DIFF block code is reused for DIFF2 block in generate_compare_long_string_same_encoding. - Registers and labels are partially renamed to better reflect code actions. This patch is dependent on JDK-8218966 and should be applied on top of it. Testing: - jck - hotspot jtreg compiler/*, runtime/* and gc/* tests. Including AARCH64-implementation-specific compareTo tests introduced in JDK-8218966 fix - jdk jtreg tier1-3 tests No regressions were found. I'd like to thank Pengfei Li (Pengfei.Li(a)arm.com) for pre-review and additional testing. Thanks, Dmitrij

5 10

AARCH64 support for lworld
by Dmitry Samersoff 08 Sep '19

08 Sep '19

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

6 28

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

24 May '19

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

7 43

8218966: AArch64: String.compareTo() can read memory after string
by Dmitrij Pochepko 20 May '19

20 May '19

Hi all, Please review a fix for "8218966: AArch64: String.compareTo() can read memory after string". bug: https://bugs.openjdk.java.net/browse/JDK-8218966 webrev: http://cr.openjdk.java.net/~dpochepk/8218966/webrev/ Intrinsic implementation returns wrong value in rare cases for strings longer than 72 characters. Changes: - Different encodings case. Small 16-characters loop and post-loop code are re-organized to stop at string end. Post-loop now also uses compare_string_16_x_LU() to avoid code duplication. - Changed calculation of prefetchLoopExitCondition. It might be incorrect in case when SoftwarePrefetchHintDistance was set to non-default small value. - Same encoding case. Moved loop counter update out of prefetch block. It might miss end-of-string check when prefetch is disabled, with memory after string being read. - Added 2 tests. They are quite similar but TestStringCompareToSameLength compares strings of same length, and TestStringCompareToDifferentLength is for different lengths. Tests cover 8218966 case. And also they cover different parts of intrinsic, taking into account conditions in the implementation and possible SoftwarePrefetchHintDistance values. Testing: Existing jtreg and jck tests were not able to detect 8218966 case. But they pass with the fix applied. Newly added jtreg tests can detect the issue and potential problems in case of changes in the implementation. The following testing was performed: - jck with default vm flags - jck with -Xcomp -XX:-TieredCompilation - hotspot jtreg tests (including new tests): compiler/*, runtime/*, gc/* with default vm flags - hotspot jtreg tests (including new tests): compiler/*, runtime/*, gc/* with -Xcomp -XX:-TieredCompilation - jdk jtreg tier1-3 tests with default vm flags - jdk jtreg tier1-3 tests with -Xcomp -XX:-TieredCompilation No regressions were found. I'd like to thank Pengfei Li (Pengfei.Li(a)arm.com) for pre-review and additional testing. I'm also about to send separate additional webrev with compareTo intrinsic documentation and maintenance-related improvements as separate enhancement. Thanks, Dmitrij

2 1

Re: [aarch64-port-dev ] RFR(S): 8215792: AArch64: String.indexOf generates incorrect result
by Pengfei Li (Arm Technology China) 19 May '19

19 May '19

Hi Dmitrij, Thanks a lot for your reply. > since cnt2 is used as counter, wouldn't it be easier and shorter just to substract cnt1 from cnt2 at the beginning of this code. Total (cnt2 - cnt1 +1) combinations must be checked. That is why first sustraction is by (wordSize/str2_chr_size - 1). > Then whole fix will be probably just 1 line at the beginning: sub(cnt2, cnt2, cnt1); I don't think the whole fix could be as easy as "sub(cnt2, cnt2, cnt1)" because cnt2 is the counter which counts number of bytes not processed. It could be different from the number of bytes after current first-character-match index. But this is just my thought. Perhaps I didn't understand your idea and code thoroughly. So could you post your shorter fix and let's test if it's right? -- Thanks, Pengfei

6 14

hg: aarch64-port/jdk8u-shenandoah/hotspot: 23 new changesets
by rkennke＠redhat.com 30 Apr '19

30 Apr '19

Changeset: f88f428c5b00 Author: zgu Date: 2018-12-14 08:20 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/f88f42… [backport] Simplify Shenandoah task termination in aborted paths ! src/share/vm/gc_implementation/shenandoah/shenandoahConcurrentMark.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahTaskqueue.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahTaskqueue.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahTaskqueue.inline.hpp Changeset: 734bb53cd077 Author: rkennke Date: 2019-01-08 20:12 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/734bb5… [backport] Remove obsolete code snippet related to barriers on constants ! src/share/vm/opto/subnode.cpp Changeset: 68ad1c5de505 Author: zgu Date: 2019-01-17 08:48 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/68ad1c… [backport] 8217213: shenandoahTaskQueue.hpp includes .inline.hpp file Reviewed-by: shade, tschatzl ! src/share/vm/gc_implementation/shenandoah/shenandoahTaskqueue.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahTaskqueue.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahTaskqueue.inline.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahVerifier.cpp Changeset: c45ac5fae20d Author: vlivanov Date: 2019-01-18 17:34 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/c45ac5… [backport] 8217400: Optimized build is broken by Shenandoah changes Reviewed-by: shade ! src/share/vm/gc_implementation/shenandoah/shenandoahCodeRoots.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahFreeSet.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.hpp Changeset: 25256c6edbcc Author: rkennke Date: 2019-01-14 12:49 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/25256c… [backport] 8216973: Kick up cleanup phases in the right places Reviewed-by: shade ! src/share/vm/gc_implementation/shenandoah/shenandoahControlThread.cpp Changeset: 7e1766d511ae Author: zgu Date: 2019-01-18 09:10 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/7e1766… [backport] 8217319: Cleanup Shenandoah includes Reviewed-by: shade ! src/share/vm/gc_implementation/shenandoah/shenandoahAsserts.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahCodeRoots.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahConcurrentMark.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeapRegion.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeapRegionSet.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahMarkCompact.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahMetrics.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahPacer.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahStrDedupQueue.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahStringDedup.cpp Changeset: dc4d64c2a7d3 Author: shade Date: 2019-01-19 11:20 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/dc4d64… [backport] 8217343: Shenandoah control thread should be able to run at critical priority Reviewed-by: rkennke ! src/share/vm/gc_implementation/shenandoah/shenandoahControlThread.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoah_globals.hpp + test/gc/shenandoah/options/TestCriticalControlThreadPriority.java Changeset: a3173f8cefae Author: shade Date: 2019-02-21 15:52 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/a3173f… [backport] 8219524: Shenandoah misreports "committed" size in MemoryMXBean Reviewed-by: rkennke, zgu ! src/share/vm/services/shenandoahMemoryPool.cpp ! test/gc/shenandoah/mxbeans/TestMemoryMXBeans.java Changeset: 159c0cd584cb Author: zgu Date: 2019-02-28 08:44 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/159c0c… [backport] 8219857: Shenandoah GC may initialize thread's gclab twice Reviewed-by: rkennke ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.cpp Changeset: f7e2278f2263 Author: zgu Date: 2019-03-02 08:33 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/f7e227… [backport] 8219976: GarbageCollectionNotificationInfo always says "No GC" when running Shenandoah Reviewed-by: rkennke ! src/share/vm/gc_implementation/shenandoah/shenandoahUtils.cpp Changeset: 736ef07969c8 Author: shade Date: 2019-03-07 10:22 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/736ef0… [backport] 8220228: Improve Shenandoah pacing histogram message Reviewed-by: rkennke ! src/share/vm/gc_implementation/shenandoah/shenandoahPacer.cpp Changeset: 663a8edad534 Author: zgu Date: 2018-09-19 16:51 -0400 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/663a8e… [backport] 8210879: ClassLoaderStatsClosure does raw oop comparison Summary: Uses oopDesc::equals() for comparing oop equality Reviewed-by: shade ! src/share/vm/classfile/classLoaderStats.hpp Changeset: 2f67708cdbce Author: shade Date: 2019-03-11 00:06 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/2f6770… [backport] 8220350: Refactor ShenandoahHeap::initialize Reviewed-by: rkennke, zgu ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.cpp ! 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 Changeset: 19e598acff42 Author: shade Date: 2019-03-11 00:06 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/19e598… [backport] 8220153: Shenandoah does not work with TransparentHugePages properly Reviewed-by: rkennke, zgu ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.cpp Changeset: 725f4730612f Author: shade Date: 2019-03-11 00:06 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/725f47… [backport] 8220162: Shenandoah should not commit HugeTLBFS memory Reviewed-by: rkennke, zgu ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeapRegion.cpp Changeset: 73181b310302 Author: roland Date: 2019-01-14 13:53 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/73181b… [backport] 8217043: Shenandoah: SIGSEGV in Type::meet_helper() at barrier expansion time Reviewed-by: shade, rkennke, thartmann ! src/share/vm/opto/shenandoahSupport.cpp Changeset: 42351e128f78 Author: shade Date: 2019-04-24 11:39 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/42351e… [backport] 8222843: Print Shenandoah cset map addresses in hs_err Reviewed-by: rkennke ! src/share/vm/gc_implementation/shenandoah/shenandoahCollectionSet.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.cpp Changeset: cc73766570a0 Author: shade Date: 2019-04-24 11:40 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/cc7376… [backport] 8222838: Shenandoah: SEGV on accessing cset bitmap for NULL ptr Reviewed-by: rkennke ! src/share/vm/gc_implementation/shenandoah/shenandoahCollectionSet.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahCollectionSet.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.cpp Changeset: b92498447739 Author: shade Date: 2019-03-15 13:01 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/b92498… [backport] 8220712: [TESTBUG] gc/shenandoah/compiler/TestMaybeNullUnsafeAccess should run with Shenandoah enabled Reviewed-by: rkennke, roland ! test/gc/shenandoah/compiler/TestMaybeNullUnsafeAccess.java Changeset: 33f04536427e Author: shade Date: 2019-04-08 19:43 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/33f045… [backport] 8222130: Shenandoah should verify roots after pre-evacuation Reviewed-by: rkennke, zgu ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahVerifier.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahVerifier.hpp Changeset: 6b8ee2a228e8 Author: shade Date: 2019-04-09 21:20 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/6b8ee2… [backport] 8222185: Shenandoah should report "committed" as capacity Reviewed-by: zgu, rkennke ! src/share/vm/gc_implementation/shenandoah/heuristics/shenandoahAdaptiveHeuristics.cpp ! src/share/vm/gc_implementation/shenandoah/heuristics/shenandoahCompactHeuristics.cpp ! src/share/vm/gc_implementation/shenandoah/heuristics/shenandoahPassiveHeuristics.cpp ! src/share/vm/gc_implementation/shenandoah/heuristics/shenandoahStaticHeuristics.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahFreeSet.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahMonitoringSupport.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahPacer.cpp Changeset: 74bafacd2f75 Author: shade Date: 2019-04-09 21:20 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/74bafa… [backport] 8222186: Shenandoah should not uncommit below minimum heap size Reviewed-by: zgu, rkennke ! src/share/vm/gc_implementation/shenandoah/shenandoahControlThread.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeap.hpp ! src/share/vm/runtime/arguments.cpp ! test/gc/shenandoah/mxbeans/TestMemoryMXBeans.java Changeset: 94a8fbf1b6a3 Author: shade Date: 2019-04-28 01:42 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/94a8fb… Prettify Shenandoah JDK 8 logging ! src/share/vm/gc_implementation/shenandoah/shenandoahGCTraceTime.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahGCTraceTime.hpp + src/share/vm/gc_implementation/shenandoah/shenandoahLogging.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahLogging.hpp

1 0

Tracking aarch64 downstream backports
by Aleksey Shipilev 30 Apr '19

30 Apr '19

Hi, We have the backports monitor [1] that tracks the status for the patches across the repositories. For example, for AArch64-specific problems it currently prints this: > JDK-8219698: aarch64: SIGILL triggered when specifying unsupported hardware features > > Original Bug: > URL: https://bugs.openjdk.java.net/browse/JDK-8219698 > Reporter: Felix Yang > Assignee: Felix Yang > Priority: P4 > Components: hotspot/runtime > > Original Fix: > 13: JDK-8219698, http://hg.openjdk.java.net/jdk/jdk/rev/72ce7dd54939, 57 day(s) ago > > Backports and Forwardports: > 12: 12.0.2, JDK-8220537, http://hg.openjdk.java.net/jdk-updates/jdk12u/rev/bc3f5be06d88, 44 day(s) ago > 11: 11.0.4, JDK-8220535, http://hg.openjdk.java.net/jdk-updates/jdk11u-dev/rev/e0d47c058971, 44 day(s) ago > 8: MISSING > 7: Not affected Notice "8: MISSING" -- it says that while the issue has the "Affected Versions: 8", and there is no corresponding backport in 8u. Which stands to reason, as aarch64-port is not in mainline 8u. We have the same issue with Shenandoah 8u and 11u development forests: Shenandoah is not in mainline there. So, we got ourselves a workaround: the backport monitor parses the Mercurial repositories, and looks for the matching bug ID lines, if the issue has the "Affected Versions" either "8-shenandoah" or "11-shenandoah", like this: > JDK-8220712: [TESTBUG] gc/shenandoah/compiler/TestMaybeNullUnsafeAccess should run with Shenandoah enabled > > Original Bug: > URL: https://bugs.openjdk.java.net/browse/JDK-8220712 > Reporter: Aleksey Shipilev > Assignee: Aleksey Shipilev > Priority: P4 > Components: hotspot/gc > > Original Fix: > 13: JDK-8220712, http://hg.openjdk.java.net/jdk/jdk/rev/6f14d52d5e10, 41 day(s) ago > > Backports and Forwardports: > 12: 12.0.2, JDK-8221572, http://hg.openjdk.java.net/jdk-updates/jdk12u/rev/8e7e0aa6882b, 29 day(s) ago > 11: Not affected > 8: Not affected > 7: Not affected > > Shenandoah Backports: > 11: shenandoah-jdk-11.0.3+6, https://hg.openjdk.java.net/shenandoah/jdk11//rev/5cf51abddfbe > 8: MISSING Notice the "Shenandoah Backports" section. We can do the same for AArch64-port. To do this, we need Project Lead to ask ops@ for a special version tag (e.g. "8-aarch64" or something) in JIRA, and then we put this new version tag instead of plain "8" on issues that affect only the downstream aarch64-8u code. (Then I'll do some adjustments to backport monitor to handle that new thing). -- Thanks, -Aleksey [1] https://builds.shipilev.net/backports-monitor/label-actionable-redhat-openj…

2 11

JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64
by ci_notify＠linaro.org 30 Apr '19

30 Apr '19

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/jdk8u/openjdk-jtreg-nightly-tests/summary/2019/12… ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 792; fail: 16; error: 3 Build 1: aarch64/2019/feb/03 pass: 800; fail: 9; error: 2 Build 2: aarch64/2019/feb/14 pass: 799; fail: 9; error: 3 Build 3: aarch64/2019/feb/26 pass: 799; fail: 9; error: 3 Build 4: aarch64/2019/feb/28 pass: 803; fail: 9; error: 2 Build 5: aarch64/2019/mar/26 pass: 799; fail: 13; error: 2 Build 6: aarch64/2019/apr/09 pass: 807; fail: 9; error: 2 Build 7: aarch64/2019/apr/18 pass: 815; fail: 10 Build 8: aarch64/2019/apr/30 pass: 797; fail: 23; error: 9 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 5,778; fail: 236; error: 28 Build 1: aarch64/2019/feb/03 pass: 5,756; fail: 261; error: 25 Build 2: aarch64/2019/feb/14 pass: 5,761; fail: 257; error: 24 Build 3: aarch64/2019/feb/26 pass: 5,756; fail: 259; error: 27 Build 4: aarch64/2019/feb/28 pass: 5,749; fail: 268; error: 26 Build 5: aarch64/2019/mar/26 pass: 5,768; fail: 246; error: 29 Build 6: aarch64/2019/apr/09 pass: 5,763; fail: 267; error: 24 Build 7: aarch64/2019/apr/18 pass: 5,784; fail: 259; error: 25 Build 8: aarch64/2019/apr/30 pass: 5,779; fail: 262; error: 27 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 3,114; fail: 2 Build 1: aarch64/2019/feb/03 pass: 3,114; fail: 2 Build 2: aarch64/2019/feb/14 pass: 3,114; fail: 2 Build 3: aarch64/2019/feb/26 pass: 3,114; fail: 2 Build 4: aarch64/2019/feb/28 pass: 3,114; fail: 2 Build 5: aarch64/2019/mar/26 pass: 3,114; fail: 2 Build 6: aarch64/2019/apr/09 pass: 3,115; fail: 2 Build 7: aarch64/2019/apr/18 pass: 3,115; fail: 2 Build 8: aarch64/2019/apr/30 pass: 3,115; fail: 2 Previous results can be found here: http://openjdk.linaro.org/jdk8u/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): 2.80x Relative performance: Server critical-jOPS (nc): 7.88x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 176.44 Server 176.44 / Server 2014-04-01 (71.00): 2.49x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-02-04 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/034/results/ 2019-02-14 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/045/results/ 2019-02-27 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/057/results/ 2019-02-28 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/059/results/ 2019-03-26 pass rate: 8490/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/085/results/ 2019-04-09 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/099/results/ 2019-04-19 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/108/results/ 2019-04-30 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/120/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/

1 0

RFR: 8223020: aarch64: expand minI_rReg and maxI_rReg patterns into separate instructions
by Yangfei (Felix) 30 Apr '19

30 Apr '19

Hi, Please review: JBS: https://bugs.openjdk.java.net/browse/JDK-8223020 Webrev: http://cr.openjdk.java.net/~fyang/8223020/webrev.00 Currently, two instructions will be emitted for minI_rReg/maxI_rReg patterns: cmpw + cselw. As these two instructions are always emitted together, the GCM (Global Code Motion) phase will not be able to schedule them independently. Patch expands minI_rReg and maxI_rReg patterns into separate instructions. For the small test case on the JBS, GCM can do a better schedule with this change. Jtreg tested with a fastdebug aarch64 build. The test also reveals another issue: minI_rReg and maxI_rReg patterns are not taking advantage of the aarch64 zero register, so for maxI_rReg pattern we see code like this: 0x0000ffffa34148f0: mov w12, wzr <======== 0x0000ffffa34148f4: cmp w10, w12 <======== 0x0000ffffa34148f8: csel w10, w10, w12, gt <======== which can be further simplified into: 0x0000ffffa34148f4: cmp w10, wzr <======== 0x0000ffffa34148f8: csel w10, w10, wzr, gt <======== But looks like it's hard to find a test case to trigger this issue for minI_rReg pattern. I can fix this for maxI_rReg pattern with another patch if necessary. Thanks, Felix

2 3

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

29 Apr '19

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/2019/119… ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/18 pass: 5,568; fail: 3; not run: 93 Build 1: aarch64/2019/mar/20 pass: 5,568; fail: 3; not run: 93 Build 2: aarch64/2019/mar/29 pass: 5,572; fail: 3; not run: 93 Build 3: aarch64/2019/apr/03 pass: 5,576; fail: 2; not run: 96 Build 4: aarch64/2019/apr/05 pass: 5,576; fail: 2; error: 1; not run: 96 Build 5: aarch64/2019/apr/08 pass: 5,577; fail: 2; not run: 96 Build 6: aarch64/2019/apr/10 pass: 5,577; fail: 5; error: 1; not run: 96 Build 7: aarch64/2019/apr/12 pass: 5,581; fail: 3; not run: 96 Build 8: aarch64/2019/apr/15 pass: 5,582; fail: 2; not run: 96 Build 9: aarch64/2019/apr/17 pass: 5,579; fail: 2; not run: 96 Build 10: aarch64/2019/apr/19 pass: 5,579; fail: 2; not run: 96 Build 11: aarch64/2019/apr/22 pass: 5,580; fail: 2; not run: 96 Build 12: aarch64/2019/apr/24 pass: 5,579; fail: 3; not run: 96 Build 13: aarch64/2019/apr/26 pass: 5,579; fail: 3; error: 1; not run: 96 Build 14: aarch64/2019/apr/29 pass: 5,601; fail: 2; not run: 96 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/18 pass: 8,510; fail: 523; error: 24 Build 1: aarch64/2019/mar/20 pass: 8,513; fail: 522; error: 25 Build 2: aarch64/2019/mar/29 pass: 8,519; fail: 532; error: 22 Build 3: aarch64/2019/apr/03 pass: 8,523; fail: 530; error: 23 Build 4: aarch64/2019/apr/05 pass: 8,514; fail: 539; error: 28 Build 5: aarch64/2019/apr/08 pass: 8,513; fail: 540; error: 29 Build 6: aarch64/2019/apr/10 pass: 8,502; fail: 552; error: 30 Build 7: aarch64/2019/apr/12 pass: 8,525; fail: 530; error: 24 Build 8: aarch64/2019/apr/15 pass: 8,515; fail: 537; error: 27 Build 9: aarch64/2019/apr/17 pass: 8,543; fail: 524; error: 17 Build 10: aarch64/2019/apr/19 pass: 8,535; fail: 530; error: 19 Build 11: aarch64/2019/apr/22 pass: 8,533; fail: 526; error: 25 Build 12: aarch64/2019/apr/24 pass: 8,521; fail: 531; error: 28 Build 13: aarch64/2019/apr/26 pass: 8,521; fail: 531; error: 28 Build 14: aarch64/2019/apr/29 pass: 8,527; fail: 527; error: 26 4 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/18 pass: 3,932 Build 1: aarch64/2019/mar/20 pass: 3,933 Build 2: aarch64/2019/mar/29 pass: 3,935 Build 3: aarch64/2019/apr/03 pass: 3,931 Build 4: aarch64/2019/apr/05 pass: 3,931 Build 5: aarch64/2019/apr/08 pass: 3,931 Build 6: aarch64/2019/apr/10 pass: 3,931 Build 7: aarch64/2019/apr/12 pass: 3,934 Build 8: aarch64/2019/apr/15 pass: 3,934 Build 9: aarch64/2019/apr/17 pass: 3,936 Build 10: aarch64/2019/apr/19 pass: 3,936 Build 11: aarch64/2019/apr/22 pass: 3,936 Build 12: aarch64/2019/apr/24 pass: 3,937 Build 13: aarch64/2019/apr/26 pass: 3,938 Build 14: aarch64/2019/apr/29 pass: 3,938 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.75x Relative performance: Server critical-jOPS (nc): 9.33x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 207.57 Server 207.57 / Server 2014-04-01 (71.00): 2.92x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-03-18 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/077/results/ 2019-03-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/079/results/ 2019-03-29 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/088/results/ 2019-04-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/093/results/ 2019-04-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/095/results/ 2019-04-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/098/results/ 2019-04-11 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/100/results/ 2019-04-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/102/results/ 2019-04-15 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/105/results/ 2019-04-17 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/107/results/ 2019-04-19 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/109/results/ 2019-04-22 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/112/results/ 2019-04-24 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/114/results/ 2019-04-26 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/116/results/ 2019-04-29 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/119/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/

1 0