July 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

[11u] RFR 8228400: Remove built-in AArch64 simulator
by Aleksey Shipilev 07 Aug '19

07 Aug '19

Original change: https://bugs.openjdk.java.net/browse/JDK-8228400 https://hg.openjdk.java.net/jdk/jdk/rev/01bca26734bb This train goes all the way down to 8u-aarch64, this change is for 11u. This considerably shrinks the aarch64 code, making it more maintainable. I'll let the original change stew in jdk/jdk a little bit more, but we can start reviewing backports meanwhile. If there are follow-up issues from that removal, we would address them as separate backports (as usual). 11u webrev: https://cr.openjdk.java.net/~shade/8228400/webrev.11u.01/ There are several differences: - no shenandoahBarrierSetAssembler.hpp; we would discover the blrt removal during downstream Shenandoah merges (and build failures); - os_linux_aarch64.cpp is a bit different: has SPELL_REG_{SP,FP} and thus conflicts; - a few BUILTIN_SIM blocks removals were rejected due to context changes; Testing: aarch64 tier1, tier2; eyeballing differences against jdk/jdk changeset -- Thanks, -Aleksey

3 9

Re: [aarch64-port-dev ] The result of Math.log(3.0) is different on x86_64 and aarch64?
by Pengfei Li (Arm Technology China) 01 Aug '19

01 Aug '19

Hi Bo, Tianhua, Thanks for reporting this issue. You could CC aarch64-port-dev(a)openjdk.java.net if you find something strange on AArch64 server next time. > >> Sorry to disturb you again, I took some tests of java.lang.Math.log > >> function on aarch64 server, I met a strange case, the result of > >> Math.log(3.0) is different with x86_64: > >> on x86_64: > >> scala> Math.log(3.0) res50: Double = 1.0986122886681098 > >> > >> but on aarch64: > >> scala> Math.log(3.0) res19: Double = 1.0986122886681096 I've reproduced this on both JDK12 and latest JDK master (14) with below Java code. public class Test { public static void main(String[] args) { double d = Math.log(3.0); String hex = Long.toHexString(Double.doubleToRawLongBits(d)); System.out.println(d + "(0x" + hex + ")"); } } (x86_64)~$ java Test 1.0986122886681098(0x3ff193ea7aad030b) (aarch64)~$ java Test 1.0986122886681096(0x3ff193ea7aad030a) From above results we see the least significant bit differs on aarch64 from that on x86_64. So which one is more accurate? By exploring HotSpot code, we could see a method "__ieee754_log(double x)"[1] in shared (architecture independent) code which computes the log(double). But this SharedRuntime method is called only if the architecture specific "StubRoutine::dlog()" is NULL. See [2] for this logic in the C2 compiler but there is no big difference in C1 or the interpreter. I.e. The Math.log(3.0) actually calls into some hand-crafted assembly code if it's generated. By looking into the cpu-specific stuff, we could found that the log() routine is generated on x86_64[3], but disable on aarch64[4] due to issues found before. In another word, the Math.log() call is optimized by HotSpot intrinsics located at [5] on x86_64 but just uses __ieee_754_log() on aarch64. To prove what I've seen is right, I tested my above Java code with VM options "-XX:+UnlockDiagnosticVMOptions -XX:-InlineMathNatives" on both x86_64 and aarch64. (x86_64)~$ java -XX:+UnlockDiagnosticVMOptions -XX:-InlineMathNatives Test 1.0986122886681096(0x3ff193ea7aad030a) (x86_64)~$ java Test 1.0986122886681098(0x3ff193ea7aad030b) DIFFERENT! (aarch64)~$ java -XX:+UnlockDiagnosticVMOptions -XX:-InlineMathNatives Test 1.0986122886681096(0x3ff193ea7aad030a) (aarch64)~$ java Test 1.0986122886681096(0x3ff193ea7aad030a) SAME! From the results we see that, if we have the assumption shared method __ieee754_log(double) is correct, there should be nothing wrong in aarch64 HotSpot. Instead, the x86_64 log intrinsics may have done some optimization that destroys the accuracy. We need an Intel engineer (maybe ~vdeshpande) to look at the code. [1] http://hg.openjdk.java.net/jdk/jdk/file/2116221e2dde/src/hotspot/share/runt… [2] http://hg.openjdk.java.net/jdk/jdk/file/2116221e2dde/src/hotspot/share/opto… [3] http://hg.openjdk.java.net/jdk/jdk/file/2116221e2dde/src/hotspot/cpu/x86/st… [4] http://hg.openjdk.java.net/jdk/jdk/file/2116221e2dde/src/hotspot/cpu/aarch6… [5] http://hg.openjdk.java.net/jdk/jdk/file/2116221e2dde/src/hotspot/cpu/x86/ma… -- Thanks, Pengfei

5 6

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

31 Jul '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/21… ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/feb/03 pass: 800; fail: 9; error: 2 Build 1: aarch64/2019/feb/14 pass: 799; fail: 9; error: 3 Build 2: aarch64/2019/feb/26 pass: 799; fail: 9; error: 3 Build 3: aarch64/2019/feb/28 pass: 803; fail: 9; error: 2 Build 4: aarch64/2019/mar/26 pass: 799; fail: 13; error: 2 Build 5: aarch64/2019/apr/09 pass: 807; fail: 9; error: 2 Build 6: aarch64/2019/apr/18 pass: 815; fail: 10 Build 7: aarch64/2019/apr/30 pass: 797; fail: 23; error: 9 Build 8: aarch64/2019/may/02 pass: 814; fail: 14; error: 2 Build 9: aarch64/2019/jun/15 pass: 815; fail: 22; error: 1 Build 10: aarch64/2019/jun/20 pass: 820; fail: 16; error: 2 Build 11: aarch64/2019/jun/29 pass: 807; fail: 25; error: 6 Build 12: aarch64/2019/jul/19 pass: 814; fail: 20; error: 4 Build 13: aarch64/2019/jul/25 pass: 802; fail: 25; error: 11 Build 14: aarch64/2019/jul/30 pass: 787; fail: 40; error: 11 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/feb/03 pass: 5,756; fail: 261; error: 25 Build 1: aarch64/2019/feb/14 pass: 5,761; fail: 257; error: 24 Build 2: aarch64/2019/feb/26 pass: 5,756; fail: 259; error: 27 Build 3: aarch64/2019/feb/28 pass: 5,749; fail: 268; error: 26 Build 4: aarch64/2019/mar/26 pass: 5,768; fail: 246; error: 29 Build 5: aarch64/2019/apr/09 pass: 5,763; fail: 267; error: 24 Build 6: aarch64/2019/apr/18 pass: 5,784; fail: 259; error: 25 Build 7: aarch64/2019/apr/30 pass: 5,779; fail: 262; error: 27 Build 8: aarch64/2019/may/02 pass: 5,784; fail: 262; error: 22 Build 9: aarch64/2019/jun/15 pass: 5,827; fail: 242; error: 22 Build 10: aarch64/2019/jun/20 pass: 5,821; fail: 244; error: 26 Build 11: aarch64/2019/jun/29 pass: 5,799; fail: 265; error: 27 Build 12: aarch64/2019/jul/19 pass: 5,940; fail: 278; error: 22 Build 13: aarch64/2019/jul/25 pass: 5,938; fail: 276; error: 26 Build 14: aarch64/2019/jul/30 pass: 5,942; fail: 273; error: 25 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/feb/03 pass: 3,114; fail: 2 Build 1: aarch64/2019/feb/14 pass: 3,114; fail: 2 Build 2: aarch64/2019/feb/26 pass: 3,114; fail: 2 Build 3: aarch64/2019/feb/28 pass: 3,114; fail: 2 Build 4: aarch64/2019/mar/26 pass: 3,114; fail: 2 Build 5: aarch64/2019/apr/09 pass: 3,115; fail: 2 Build 6: aarch64/2019/apr/18 pass: 3,115; fail: 2 Build 7: aarch64/2019/apr/30 pass: 3,115; fail: 2 Build 8: aarch64/2019/may/02 pass: 3,115; fail: 2 Build 9: aarch64/2019/jun/15 pass: 3,116; fail: 2 Build 10: aarch64/2019/jun/20 pass: 3,116; fail: 2 Build 11: aarch64/2019/jun/29 pass: 3,116; fail: 2 Build 12: aarch64/2019/jul/19 pass: 3,116; fail: 2 Build 13: aarch64/2019/jul/25 pass: 3,116; fail: 2 Build 14: aarch64/2019/jul/30 pass: 3,116; 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): 6.17x Relative performance: Server critical-jOPS (nc): 7.44x 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: 170.06 Server 170.06 / Server 2014-04-01 (71.00): 2.40x 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/ 2019-05-02 pass rate: 8490/8490, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/122/results/ 2019-06-16 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/166/results/ 2019-06-21 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/171/results/ 2019-06-30 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/180/results/ 2019-07-20 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/200/results/ 2019-07-26 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/211/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/

1 0

JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 13 on AArch64
by ci_notify＠linaro.org 31 Jul '19

31 Jul '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/jdk13/openjdk-jtreg-nightly-tests/summary/2019/21… ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/18 pass: 5,646; fail: 3 Build 1: aarch64/2019/jun/20 pass: 5,645; fail: 2; error: 1 Build 2: aarch64/2019/jun/22 pass: 5,645; fail: 3 Build 3: aarch64/2019/jun/25 pass: 5,644; fail: 2; error: 1 Build 4: aarch64/2019/jun/27 pass: 5,645; fail: 2 Build 5: aarch64/2019/jun/29 pass: 5,644; fail: 3 Build 6: aarch64/2019/jul/02 pass: 5,645; fail: 2 Build 7: aarch64/2019/jul/04 pass: 5,644; fail: 2; error: 1 Build 8: aarch64/2019/jul/09 pass: 5,643; fail: 4 Build 9: aarch64/2019/jul/16 pass: 5,646; fail: 1 Build 10: aarch64/2019/jul/18 pass: 5,644; fail: 2; error: 1 Build 11: aarch64/2019/jul/20 pass: 5,645; fail: 1; error: 1 Build 12: aarch64/2019/jul/23 pass: 5,644; fail: 3 Build 13: aarch64/2019/jul/25 pass: 5,644; fail: 3 Build 14: aarch64/2019/jul/30 pass: 5,645; fail: 2 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/18 pass: 8,594; fail: 526; error: 25 Build 1: aarch64/2019/jun/20 pass: 8,592; fail: 524; error: 30 Build 2: aarch64/2019/jun/22 pass: 8,599; fail: 523; error: 24 Build 3: aarch64/2019/jun/25 pass: 8,603; fail: 525; error: 18 Build 4: aarch64/2019/jun/27 pass: 8,609; fail: 512; error: 26 Build 5: aarch64/2019/jun/29 pass: 8,601; fail: 520; error: 29 Build 6: aarch64/2019/jul/02 pass: 8,604; fail: 521; error: 25 Build 7: aarch64/2019/jul/04 pass: 8,601; fail: 523; error: 26 Build 8: aarch64/2019/jul/09 pass: 8,606; fail: 515; error: 29 Build 9: aarch64/2019/jul/16 pass: 8,593; fail: 531; error: 30 Build 10: aarch64/2019/jul/18 pass: 8,618; fail: 527; error: 26 Build 11: aarch64/2019/jul/20 pass: 8,619; fail: 519; error: 33 Build 12: aarch64/2019/jul/23 pass: 8,616; fail: 525; error: 30 Build 13: aarch64/2019/jul/25 pass: 8,620; fail: 528; error: 23 Build 14: aarch64/2019/jul/30 pass: 8,610; fail: 529; error: 32 3 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/18 pass: 3,962 Build 1: aarch64/2019/jun/20 pass: 3,962 Build 2: aarch64/2019/jun/22 pass: 3,962 Build 3: aarch64/2019/jun/25 pass: 3,962 Build 4: aarch64/2019/jun/27 pass: 3,962 Build 5: aarch64/2019/jun/29 pass: 3,962 Build 6: aarch64/2019/jul/02 pass: 3,962 Build 7: aarch64/2019/jul/04 pass: 3,962 Build 8: aarch64/2019/jul/09 pass: 3,962 Build 9: aarch64/2019/jul/16 pass: 3,963 Build 10: aarch64/2019/jul/18 pass: 3,964 Build 11: aarch64/2019/jul/20 pass: 3,964 Build 12: aarch64/2019/jul/23 pass: 3,964 Build 13: aarch64/2019/jul/25 pass: 3,964 Build 14: aarch64/2019/jul/30 pass: 3,964 Previous results can be found here: http://openjdk.linaro.org/jdk13/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.63x Relative performance: Server critical-jOPS (nc): 9.40x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk13/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/jdk13/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-06-19 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/169/results/ 2019-06-21 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/171/results/ 2019-06-23 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/173/results/ 2019-06-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/176/results/ 2019-06-28 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/178/results/ 2019-06-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/180/results/ 2019-07-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/183/results/ 2019-07-04 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/185/results/ 2019-07-10 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/190/results/ 2019-07-16 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/197/results/ 2019-07-19 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/199/results/ 2019-07-21 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/201/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/204/results/ 2019-07-26 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/211/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/

1 0

hg: aarch64-port/jdk8u-shenandoah/hotspot: 8228770: Revert development hsdis changes
by shade＠redhat.com 30 Jul '19

30 Jul '19

Changeset: 7570e7d49957 Author: shade Date: 2019-07-30 18:06 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/7570e… 8228770: Revert development hsdis changes Reviewed-by: adinn ! src/share/tools/hsdis/Makefile ! src/share/tools/hsdis/hsdis.c

1 0

RFR (S) 8228770: Revert development hsdis changes
by Aleksey Shipilev 30 Jul '19

30 Jul '19

RFE: https://bugs.openjdk.java.net/browse/JDK-8228770 Current 8u aarch64-port has changes in hsdis code/config: https://builds.shipilev.net/patch-openjdk-jdk8-aarch64/hotspot/src/share/to… https://builds.shipilev.net/patch-openjdk-jdk8-aarch64/hotspot/src/share/to… I believe these are not needed anymore. We just want to bring the change from staging repo: http://hg.openjdk.java.net/aarch64-port/stage/hotspot/rev/ef43f5719e95 Full patch: http://cr.openjdk.java.net/~shade/8228770/webrev.01/ This would leaves us with this change against 8u upstream: $ hg diff -r f6fa131b5f40 src/share/tools/ diff -r f6fa131b5f40 src/share/tools/hsdis/hsdis.c --- a/src/share/tools/hsdis/hsdis.c Thu Jul 11 00:03:29 2019 +0100 +++ b/src/share/tools/hsdis/hsdis.c Tue Jul 30 13:02:43 2019 +0200 @@ -489,10 +489,13 @@ res = "sparc:v9b"; #endif #if defined(LIBARCH_ppc64) || defined(LIBARCH_ppc64le) res = "powerpc:common64"; #endif +#ifdef LIBARCH_aarch64 + res = "aarch64"; +#endif if (res == NULL) res = "architecture not set in Makefile!"; return res; } While most hsdis builds would be with jdk/jdk code, that contains most up-to-date hsdis source, I still tried to build it from the 8u aarch64-port tree after this change. It works fine on RHEL with binutils 2.32, tested with JMH perfasm and newly built hsdis binary. Testing: building hsdis on aarch64, x86_64; adhoc hsdis tests; eyeballing diff against upstream -- Thanks, -Aleksey

2 1

RFR (M) 8228400: Remove built-in AArch64 simulator
by Aleksey Shipilev 30 Jul '19

30 Jul '19

RFE: https://bugs.openjdk.java.net/browse/JDK-8228400 There is a lot of code in AArch64 port that hooks up to the built-in simulator. That simulator was used to bootstrap/develop the port when hardware was not available. This simulator is not needed now, and we should remove it to unclutter the code. Removal webrev: https://cr.openjdk.java.net/~shade/8228400/webrev.02/ The only thing that feels risky for me is removal of call_VM_leaf_base1 in templateTable_aarch64.cpp, please take a thorough look. I am planning to backport it to 11u and 8u-aarch64 too. Testing: linux-aarch64-fastdebug tier1, tier2; linux-x86_64-fastdebug builds; jdk-submit (running) -- Thanks, -Aleksey

3 9

hg: aarch64-port/jdk8u-shenandoah/hotspot: 8228767: Revert ResourceMark additions
by shade＠redhat.com 30 Jul '19

30 Jul '19

Changeset: 8086f8906cec Author: shade Date: 2019-07-30 12:09 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/8086f… 8228767: Revert ResourceMark additions Reviewed-by: adinn ! src/share/vm/oops/method.cpp

1 0