From ci_notify at linaro.org Sun Apr 2 16:17:39 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sun, 2 Apr 2017 16:17:39 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <719470833.3614.1491149860435.JavaMail.jenkins@ci.linaro.org> 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/091/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/28 pass: 1,386; fail: 5 Build 1: aarch64/2017/mar/01 pass: 1,387; fail: 5 Build 2: aarch64/2017/mar/02 pass: 1,387; fail: 5 Build 3: aarch64/2017/mar/03 pass: 1,387; fail: 5 Build 4: aarch64/2017/mar/08 pass: 1,388; fail: 5 Build 5: aarch64/2017/mar/11 pass: 1,388; fail: 5 Build 6: aarch64/2017/mar/13 pass: 1,388; fail: 5 Build 7: aarch64/2017/mar/15 pass: 1,387; fail: 6 Build 8: aarch64/2017/mar/17 pass: 1,390; fail: 6 Build 9: aarch64/2017/mar/19 pass: 1,391; fail: 5 Build 10: aarch64/2017/mar/21 pass: 1,391; fail: 5 Build 11: aarch64/2017/mar/25 pass: 1,393; fail: 4 Build 12: aarch64/2017/mar/27 pass: 1,393; fail: 4 Build 13: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 14: aarch64/2017/apr/01 pass: 1,396; fail: 4 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/28 pass: 7,274; fail: 695; error: 23 Build 1: aarch64/2017/mar/01 pass: 7,264; fail: 711; error: 17 Build 2: aarch64/2017/mar/02 pass: 7,272; fail: 705; error: 15 Build 3: aarch64/2017/mar/03 pass: 7,252; fail: 720; error: 21 Build 4: aarch64/2017/mar/08 pass: 7,251; fail: 720; error: 23 Build 5: aarch64/2017/mar/11 pass: 7,263; fail: 718; error: 18 Build 6: aarch64/2017/mar/13 pass: 7,268; fail: 710; error: 21 Build 7: aarch64/2017/mar/15 pass: 7,283; fail: 693; error: 25 Build 8: aarch64/2017/mar/17 pass: 7,273; fail: 709; error: 20 Build 9: aarch64/2017/mar/19 pass: 7,253; fail: 727; error: 24 Build 10: aarch64/2017/mar/21 pass: 7,294; fail: 689; error: 21 Build 11: aarch64/2017/mar/25 pass: 7,278; fail: 713; error: 23 Build 12: aarch64/2017/mar/27 pass: 7,304; fail: 690; error: 20 Build 13: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 14: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/28 pass: 3,861; error: 2 Build 1: aarch64/2017/mar/01 pass: 3,862; error: 2 Build 2: aarch64/2017/mar/02 pass: 3,862; error: 2 Build 3: aarch64/2017/mar/03 pass: 3,863; error: 2 Build 4: aarch64/2017/mar/08 pass: 3,866; error: 1 Build 5: aarch64/2017/mar/11 pass: 3,871; error: 2 Build 6: aarch64/2017/mar/13 pass: 3,872; error: 1 Build 7: aarch64/2017/mar/15 pass: 3,874; error: 4 Build 8: aarch64/2017/mar/17 pass: 3,878; error: 2 Build 9: aarch64/2017/mar/19 pass: 3,878; error: 2 Build 10: aarch64/2017/mar/21 pass: 3,876; error: 5 Build 11: aarch64/2017/mar/25 pass: 3,886; fail: 1 Build 12: aarch64/2017/mar/27 pass: 3,883; error: 4 Build 13: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 14: aarch64/2017/apr/01 pass: 3,885; fail: 3 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/28 pass: 1,388; fail: 6 Build 1: aarch64/2017/mar/01 pass: 1,390; fail: 5 Build 2: aarch64/2017/mar/02 pass: 1,390; fail: 5 Build 3: aarch64/2017/mar/03 pass: 1,390; fail: 5 Build 4: aarch64/2017/mar/08 pass: 1,391; fail: 6 Build 5: aarch64/2017/mar/11 pass: 1,392; fail: 5 Build 6: aarch64/2017/mar/13 pass: 1,392; fail: 5 Build 7: aarch64/2017/mar/15 pass: 1,392; fail: 5 Build 8: aarch64/2017/mar/17 pass: 1,395; fail: 5 Build 9: aarch64/2017/mar/19 pass: 1,395; fail: 5 Build 10: aarch64/2017/mar/21 pass: 1,394; fail: 6 Build 11: aarch64/2017/mar/25 pass: 1,397; fail: 4 Build 12: aarch64/2017/mar/27 pass: 1,396; fail: 5 Build 13: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 14: aarch64/2017/apr/01 pass: 1,400; fail: 4 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/28 pass: 7,265; fail: 708; error: 19 Build 1: aarch64/2017/mar/01 pass: 7,266; fail: 710; error: 16 Build 2: aarch64/2017/mar/02 pass: 7,284; fail: 689; error: 19 Build 3: aarch64/2017/mar/03 pass: 7,257; fail: 720; error: 16 Build 4: aarch64/2017/mar/08 pass: 7,296; fail: 679; error: 19 Build 5: aarch64/2017/mar/11 pass: 7,261; fail: 722; error: 16 Build 6: aarch64/2017/mar/13 pass: 7,290; fail: 687; error: 22 Build 7: aarch64/2017/mar/15 pass: 7,285; fail: 697; error: 19 Build 8: aarch64/2017/mar/17 pass: 7,278; fail: 703; error: 21 Build 9: aarch64/2017/mar/19 pass: 7,261; fail: 723; error: 20 Build 10: aarch64/2017/mar/21 pass: 7,271; fail: 712; error: 21 Build 11: aarch64/2017/mar/25 pass: 7,284; fail: 708; error: 22 Build 12: aarch64/2017/mar/27 pass: 7,297; fail: 695; error: 22 Build 13: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 14: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/feb/28 pass: 3,862; error: 1 Build 1: aarch64/2017/mar/01 pass: 3,860; error: 4 Build 2: aarch64/2017/mar/02 pass: 3,858; fail: 1; error: 5 Build 3: aarch64/2017/mar/03 pass: 3,863; fail: 1; error: 2 Build 4: aarch64/2017/mar/08 pass: 3,867 Build 5: aarch64/2017/mar/11 pass: 3,873 Build 6: aarch64/2017/mar/13 pass: 3,871; error: 2 Build 7: aarch64/2017/mar/15 pass: 3,878 Build 8: aarch64/2017/mar/17 pass: 3,876; error: 4 Build 9: aarch64/2017/mar/19 pass: 3,876; error: 4 Build 10: aarch64/2017/mar/21 pass: 3,879; error: 2 Build 11: aarch64/2017/mar/25 pass: 3,885; error: 2 Build 12: aarch64/2017/mar/27 pass: 3,881; error: 6 Build 13: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 14: aarch64/2017/apr/01 pass: 3,884; fail: 2; 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): 0.99x Relative performance: Server critical-jOPS (nc): 0.81x 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.02, Server: 117.63 Client 72.02 / Client 2014-04-01 (43.00): 1.67x Server 117.63 / Server 2014-04-01 (71.00): 1.66x 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-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/ 2017-03-26 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/084/results/ 2017-03-28 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/086/results/ 2017-03-31 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/089/results/ 2017-04-02 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/091/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/ From bob.vandette at oracle.com Mon Apr 3 15:57:41 2017 From: bob.vandette at oracle.com (Bob Vandette) Date: Mon, 3 Apr 2017 11:57:41 -0400 Subject: [aarch64-port-dev ] SUN_ARCH_ABI property not set or in release file for aarch64 builds Message-ID: I?m inclined to not fix this bug but thought I?d bring it to your attention just in case. I assume that OpenJDK ARM builds never set this property anyway, right? https://bugs.openjdk.java.net/browse/JDK-8177976 Bob. From aph at redhat.com Mon Apr 3 16:04:46 2017 From: aph at redhat.com (Andrew Haley) Date: Mon, 3 Apr 2017 17:04:46 +0100 Subject: [aarch64-port-dev ] SUN_ARCH_ABI property not set or in release file for aarch64 builds In-Reply-To: References: Message-ID: <69b51ae0-66c5-1697-392b-eb2f380e9f0a@redhat.com> On 03/04/17 16:57, Bob Vandette wrote: > I?m inclined to not fix this bug but thought I?d bring it to your attention just in case. > > I assume that OpenJDK ARM builds never set this property anyway, right? > > https://bugs.openjdk.java.net/browse/JDK-8177976 At the present time there's only one ABI for AArch64, so the issue doesn't arise there. (Well, there is ILP32, and that is a different ABI, but I don't know if anyone implements it, so I'm going to ignore the possibility.) Andrew. From stuart.monteith at linaro.org Mon Apr 3 16:39:19 2017 From: stuart.monteith at linaro.org (Stuart Monteith) Date: Mon, 3 Apr 2017 17:39:19 +0100 Subject: [aarch64-port-dev ] Backports from jdk9 to aarch64-port/jdk8u Message-ID: Hi, I've been working on some aarch64 patches that should be backported from jdk9 to aarch64-prot/jdk8u. I've backported the following stack of patches, and I'm currently testing with them. Do these look sensible? Are there other I should consider, that are not specifically AArch64? I've put in 8175887 as it obviously affects JCStress. I've excluded patches that are obviously not applicable to JDK8u - Graal, for example. 8175887: C1 value numbering handling of Unsafe.get*Volatile is incorrect https://bugs.openjdk.java.net/browse/JDK-8175887 http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/2ff05d967fb2 This isn't strictly an aarch64 issue, but is causing JCStress to fail. 8173472: AArch64: C1 comparisons with null only use 32-bit instructions https://bugs.openjdk.java.net/browse/JDK-8173472 http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/b53b0251e250 This is a fix for a serious bug that was causing spurious failures. 8172881: AArch64: assertion failure: the int pressure is incorrect https://bugs.openjdk.java.net/browse/JDK-8172881 http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/bfa8e4b0d4e2 Was causing a SIGSEGV. 8171537: aarch64: compiler/c1/Test6849574.java generates guarantee failure in C1 https://bugs.openjdk.java.net/browse/JDK-8171537 http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/a3bd5804b4be 8171410: aarch64: long multiplyExact shifts by 31 instead of 63 https://bugs.openjdk.java.net/browse/JDK-8171410 http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/da52f1047024 Fixes a bug that was causing a slow path to be executed by mistake. Effectively a performance improvement. 8171129: [aarch64] hs_err logs do not print register mappings https://bugs.openjdk.java.net/browse/JDK-8171129 http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/f3a31c992164 This is a nice-to-have and could be excluded. 8169177: AArch64: SIGSEGV when "-XX:+ZeroTLAB" is specified along with GC options https://bugs.openjdk.java.net/browse/JDK-8169177 http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/9831cd4dd428 8170100: AArch64: Crash in C1-compiled code accessing References https://bugs.openjdk.java.net/browse/JDK-8170100 http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/52d18f20804b 8169901: AArch64: CompareAndExchange intrinsics clobber address register https://bugs.openjdk.java.net/browse/JDK-8169901 http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/f5689e544d44 8169497: Aarch64: Improve internal array handling https://bugs.openjdk.java.net/browse/JDK-8169497 http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/824a8dcba48b I'm currently testing the stack of patches. Shall I post an email with the patch series? It is 800 lines in length. There was a little fixup required for some of the patches. BR, Stuart From aph at redhat.com Mon Apr 3 16:55:33 2017 From: aph at redhat.com (Andrew Haley) Date: Mon, 3 Apr 2017 17:55:33 +0100 Subject: [aarch64-port-dev ] Backports from jdk9 to aarch64-port/jdk8u In-Reply-To: References: Message-ID: <4d7d3ec8-4fc5-8a30-7f64-e9ee9ad3abc0@redhat.com> On 03/04/17 17:39, Stuart Monteith wrote: > Hi, > I've been working on some aarch64 patches that should be backported > from jdk9 to aarch64-prot/jdk8u. I've backported the following stack > of patches, and I'm currently testing with them. > > Do these look sensible? Are there other I should consider, that are > not specifically AArch64? I've put in 8175887 as it obviously affects > JCStress. I've excluded patches that are obviously not applicable to > JDK8u - Graal, for example. Let's triage these into category 3, 2, 1: 1: Critical. Must go in now. 2: Important. 3: Leave it until later. > 8175887: C1 value numbering handling of Unsafe.get*Volatile is incorrect > https://bugs.openjdk.java.net/browse/JDK-8175887 > http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/2ff05d967fb2 > > This isn't strictly an aarch64 issue, but is causing JCStress to fail. 2 > 8173472: AArch64: C1 comparisons with null only use 32-bit instructions > https://bugs.openjdk.java.net/browse/JDK-8173472 > http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/b53b0251e250 > > This is a fix for a serious bug that was causing spurious failures. 1 > 8172881: AArch64: assertion failure: the int pressure is incorrect > https://bugs.openjdk.java.net/browse/JDK-8172881 > http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/bfa8e4b0d4e2 > > Was causing a SIGSEGV. 1 > 8171537: aarch64: compiler/c1/Test6849574.java generates guarantee failure in C1 > https://bugs.openjdk.java.net/browse/JDK-8171537 > http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/a3bd5804b4be 2 > 8171410: aarch64: long multiplyExact shifts by 31 instead of 63 > https://bugs.openjdk.java.net/browse/JDK-8171410 > http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/da52f1047024 2 > Fixes a bug that was causing a slow path to be executed by > mistake. Effectively a performance improvement. > > 8171129: [aarch64] hs_err logs do not print register mappings > https://bugs.openjdk.java.net/browse/JDK-8171129 > http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/f3a31c992164 > > This is a nice-to-have and could be excluded. 3 > 8169177: AArch64: SIGSEGV when "-XX:+ZeroTLAB" is specified along with > GC options > https://bugs.openjdk.java.net/browse/JDK-8169177 > http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/9831cd4dd428 2 > 8170100: AArch64: Crash in C1-compiled code accessing References > https://bugs.openjdk.java.net/browse/JDK-8170100 > http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/52d18f20804b 1 > 8169901: AArch64: CompareAndExchange intrinsics clobber address register > https://bugs.openjdk.java.net/browse/JDK-8169901 > http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/f5689e544d44 1 > 8169497: Aarch64: Improve internal array handling > https://bugs.openjdk.java.net/browse/JDK-8169497 > http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/824a8dcba48b 2 Please bundle all the Category 1 bugs ASAP. Test cases don't really need to be backported. I'll try to get all this pushed soon. Thanks, Andrew. From bob.vandette at oracle.com Mon Apr 3 16:58:55 2017 From: bob.vandette at oracle.com (Bob Vandette) Date: Mon, 3 Apr 2017 12:58:55 -0400 Subject: [aarch64-port-dev ] SUN_ARCH_ABI property not set or in release file for aarch64 builds In-Reply-To: <58E27DFF.6010007@cjnash.com> References: <58E27DFF.6010007@cjnash.com> Message-ID: <52B351FD-BC1A-4B0D-8E4D-16CD72BCA0E3@oracle.com> The Oracle binaries for JDK 8 and JDK 9 Linux arm already include this property for the 32-bit ARM binaries. The only release that in question is the 64-bit aarch64 Linux distribution. There?s really no need for this property since there?s only 1 ABI that?s widely used today on that architecture. Bob. > On Apr 3, 2017, at 12:53 PM, Simon Nash wrote: > > Hi Bob, > I would find such a property very useful. > > My application is mostly written in Java but also uses a native library > that is loaded dynamically by the Java code. In order to distribute > fewer versions of the application and make things simpler for users, > I have recently started packaging multiple versions of the native library > (for example, Intel x86 and Intel x64) in a single version of the > application and using Java runtime properties to determine which of > these native libraries to load. > > I would like to do this for gnueabi and gnueabihf if I could find a > reliable way to determine at runtime which of these native libraries > is needed. It sounds like this property would be an ideal solution. > > Best regards, > Simon > > On 03/04/2017 16:57, Bob Vandette wrote: >> I?m inclined to not fix this bug but thought I?d bring it to your attention just in case. >> I assume that OpenJDK ARM builds never set this property anyway, right? >> https://bugs.openjdk.java.net/browse/JDK-8177976 >> Bob. > From stuart.monteith at linaro.org Mon Apr 3 17:50:05 2017 From: stuart.monteith at linaro.org (Stuart Monteith) Date: Mon, 3 Apr 2017 18:50:05 +0100 Subject: [aarch64-port-dev ] Backports from jdk9 to aarch64-port/jdk8u In-Reply-To: <4d7d3ec8-4fc5-8a30-7f64-e9ee9ad3abc0@redhat.com> References: <4d7d3ec8-4fc5-8a30-7f64-e9ee9ad3abc0@redhat.com> Message-ID: Hi, Thanks for that. There was one error - 8169901 does not apply and I shouldn't have included it on the list. Those intrinsics are generated by cas.m4, and aren't meaningful for jdk8u. The patchset compiles cleanly against the current tip of aarch64-port/jdk8u . A sniff test runs ok (a short SPECjbb2015 run) - I'll kick off a JCStress/JTReg run too. For clarity, the patchset is: 8173472: AArch64: C1 comparisons with null only use 32-bit instructions https://bugs.openjdk.java.net/browse/JDK-8173472 http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/b53b0251e250 8172881: AArch64: assertion failure: the int pressure is incorrect https://bugs.openjdk.java.net/browse/JDK-8172881 http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/bfa8e4b0d4e2 8170100: AArch64: Crash in C1-compiled code accessing References https://bugs.openjdk.java.net/browse/JDK-8170100 http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/52d18f20804b BR, Stuart # HG changeset patch # User aph # Date 1479749893 0 # Mon Nov 21 17:38:13 2016 +0000 # Node ID 67dfa7ba19e65e69526b940a422345eafba44dec # Parent 64d241247b0662f0f77e7eda2d1ea09a5b63a524 8170100: AArch64: Crash in C1-compiled code accessing References Reviewed-by: roland diff -r 64d241247b06 -r 67dfa7ba19e6 src/cpu/aarch64/vm/templateInterpreter_aarch64.cpp --- a/src/cpu/aarch64/vm/templateInterpreter_aarch64.cpp Fri Oct 07 15:59:38 2016 +0200 +++ b/src/cpu/aarch64/vm/templateInterpreter_aarch64.cpp Mon Nov 21 17:38:13 2016 +0000 @@ -694,7 +694,7 @@ // and so we don't need to call the G1 pre-barrier. Thus we can use the // regular method entry code to generate the NPE. // - // This code is based on generate_accessor_enty. + // This code is based on generate_accessor_entry. // // rmethod: Method* // r13: senderSP must preserve for slow path, set SP to it on fast path @@ -712,11 +712,11 @@ __ ldr(local_0, Address(esp, 0)); __ cbz(local_0, slow_path); - // Load the value of the referent field. const Address field_address(local_0, referent_offset); __ load_heap_oop(local_0, field_address); + __ mov(r19, r13); // Move senderSP to a callee-saved register // Generate the G1 pre-barrier code to log the value of // the referent field in an SATB buffer. __ enter(); // g1_write may call runtime @@ -728,7 +728,7 @@ true /* expand_call */); __ leave(); // areturn - __ andr(sp, r13, -16); // done with stack + __ andr(sp, r19, -16); // done with stack __ ret(lr); // generate a vanilla interpreter entry as the slow path # HG changeset patch # User njian # Date 1485074034 -28800 # Sun Jan 22 16:33:54 2017 +0800 # Node ID ee08f247222da94981c3c8ff4e0ff0e713b168fd # Parent 35600737c103f09e399697f6f3cf22fc4c862b7e 8172881: AArch64: assertion failure: the int pressure is incorrect Summary: Change the dst register type of get_and_setI/L/N/P from any register to non-special register. Reviewed-by: aph Contributed-by: yang.zhang at linaro.org diff -r 35600737c103 -r ee08f247222d src/cpu/aarch64/vm/aarch64.ad --- a/src/cpu/aarch64/vm/aarch64.ad Tue Dec 20 15:49:30 2016 -0500 +++ b/src/cpu/aarch64/vm/aarch64.ad Sun Jan 22 16:33:54 2017 +0800 @@ -9677,7 +9677,7 @@ %} -instruct get_and_setI(indirect mem, iRegINoSp newv, iRegI prev) %{ +instruct get_and_setI(indirect mem, iRegI newv, iRegINoSp prev) %{ match(Set prev (GetAndSetI mem newv)); format %{ "atomic_xchgw $prev, $newv, [$mem]" %} ins_encode %{ @@ -9686,7 +9686,7 @@ ins_pipe(pipe_serial); %} -instruct get_and_setL(indirect mem, iRegLNoSp newv, iRegL prev) %{ +instruct get_and_setL(indirect mem, iRegL newv, iRegLNoSp prev) %{ match(Set prev (GetAndSetL mem newv)); format %{ "atomic_xchg $prev, $newv, [$mem]" %} ins_encode %{ @@ -9695,7 +9695,7 @@ ins_pipe(pipe_serial); %} -instruct get_and_setN(indirect mem, iRegNNoSp newv, iRegI prev) %{ +instruct get_and_setN(indirect mem, iRegN newv, iRegINoSp prev) %{ match(Set prev (GetAndSetN mem newv)); format %{ "atomic_xchgw $prev, $newv, [$mem]" %} ins_encode %{ @@ -9704,7 +9704,7 @@ ins_pipe(pipe_serial); %} -instruct get_and_setP(indirect mem, iRegPNoSp newv, iRegP prev) %{ +instruct get_and_setP(indirect mem, iRegP newv, iRegPNoSp prev) %{ match(Set prev (GetAndSetP mem newv)); format %{ "atomic_xchg $prev, $newv, [$mem]" %} ins_encode %{ # HG changeset patch # User aph # Date 1485510615 0 # Fri Jan 27 09:50:15 2017 +0000 # Node ID a2c49092763aa13f0c64e6ad14e50052b6131190 # Parent ee08f247222da94981c3c8ff4e0ff0e713b168fd 8173472: AArch64: C1 comparisons with null only use 32-bit instructions Reviewed-by: roland diff -r bfa8e4b0d4e2 -r b53b0251e250 src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp diff -r ee08f247222d -r a2c49092763a src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp --- a/src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp Sun Jan 22 16:33:54 2017 +0800 +++ b/src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp Fri Jan 27 09:50:15 2017 +0000 @@ -1982,12 +1982,17 @@ } if (opr2->is_constant()) { + bool is_32bit = false; // width of register operand jlong imm; + switch(opr2->type()) { - case T_LONG: + case T_INT: + imm = opr2->as_constant_ptr()->as_jint(); + is_32bit = true; + break; + case T_LONG: imm = opr2->as_constant_ptr()->as_jlong(); break; - case T_INT: case T_ADDRESS: imm = opr2->as_constant_ptr()->as_jint(); break; @@ -2001,14 +2006,14 @@ } if (Assembler::operand_valid_for_add_sub_immediate(imm)) { - if (type2aelembytes(opr1->type()) <= 4) + if (is_32bit) __ cmpw(reg1, imm); else __ cmp(reg1, imm); return; } else { __ mov(rscratch1, imm); - if (type2aelembytes(opr1->type()) <= 4) + if (is_32bit) __ cmpw(reg1, rscratch1); else __ cmp(reg1, rscratch1); From aph at redhat.com Mon Apr 3 17:51:40 2017 From: aph at redhat.com (Andrew Haley) Date: Mon, 3 Apr 2017 18:51:40 +0100 Subject: [aarch64-port-dev ] Backports from jdk9 to aarch64-port/jdk8u In-Reply-To: References: <4d7d3ec8-4fc5-8a30-7f64-e9ee9ad3abc0@redhat.com> Message-ID: <44ab5b3a-3547-2882-2aec-9cea4662c64b@redhat.com> On 03/04/17 18:50, Stuart Monteith wrote: > For clarity, the patchset is: > > 8173472: AArch64: C1 comparisons with null only use 32-bit instructions > https://bugs.openjdk.java.net/browse/JDK-8173472 > http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/b53b0251e250 > > 8172881: AArch64: assertion failure: the int pressure is incorrect > https://bugs.openjdk.java.net/browse/JDK-8172881 > http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/bfa8e4b0d4e2 > > > 8170100: AArch64: Crash in C1-compiled code accessing References > https://bugs.openjdk.java.net/browse/JDK-8170100 > http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/52d18f20804b That looks great. These are all very low-risk to apply, and obviously fix real bugs. Andrew. From stuart.monteith at linaro.org Mon Apr 3 18:06:44 2017 From: stuart.monteith at linaro.org (Stuart Monteith) Date: Mon, 3 Apr 2017 19:06:44 +0100 Subject: [aarch64-port-dev ] Backports from jdk9 to aarch64-port/jdk8u In-Reply-To: <44ab5b3a-3547-2882-2aec-9cea4662c64b@redhat.com> References: <4d7d3ec8-4fc5-8a30-7f64-e9ee9ad3abc0@redhat.com> <44ab5b3a-3547-2882-2aec-9cea4662c64b@redhat.com> Message-ID: Excellent. As this is the first time I've done this here, I'll show my working I thought a good start would be to list everything that changed aarch64 code: hg log "grep('aarch64')" and then narrowed now by removing anything that was obviously not going to apply to aarch64-jdk8u, such as graal, s390 support. There have been changes to the stack processing, but they've been applied on top of JEP270, which doesn't apply to JDK8u. I included "8175887: C1 value numbering handling of Unsafe.get*Volatile is incorrect" even though it was CPU agnostic as I was aware of it, and could test for it. This is the initial list I drew up: Patches with aarch64 changes: N 8176054: [BACKOUT][REDO] G1 Needs pre barrier on dereference of weak JNI handles N 8175085: [REDO] G1 Needs pre barrier on dereference of weak JNI handles XN 8174879: Rename jdk.vm.ci to jdk.internal.vm.ci N 8175086: [BACKOUT] fix for JDK-8166188 N 8166188: G1 Needs pre barrier on dereference of weak JNI handles NA 8173472: AArch64: C1 comparisons with null only use 32-bit instructions ^^^^^^^ NA 8172881: AArch64: assertion failure: the int pressure is incorrect ^^^^^^^ N 8173195: [BACKOUT] 8087341: C2 doesn't optimize redundant memory operations with G1 N 8172844: Assert fails in deoptimization due to original PC at the end of code section N 8140588: Internal Error: gc/g1/ptrQueue.hpp:126 assert(_index == _sz) failed: invariant: queues are empty when activated X A 8172721: Fix for 8172144 breaks AArch64 build X A 8172144: AArch64: Implement "JEP 270: Reserved Stack Areas for Critical Sections" XNA 8173474: AArch64: fix reported -Xss minimum XNA 8173339: AArch64: Fix minimum stack size computations NA 8171537: aarch64: compiler/c1/Test6849574.java generates guarantee failure in C1 ^^^^^^^ NA 8171410: aarch64: long multiplyExact shifts by 31 instead of 63 ^^^^^^^ N 8170655: [posix] Fix minimum stack size computations N 8169373: Work around linux NPTL stack guard error. NA 8171129: [aarch64] hs_err logs do not print register mappings ^^^^^^^ XN 8170761: Buffer overrun in sharedRuntime_x86_64.cpp:477 NA 8169177: AArch64: SIGSEGV when "-XX:+ZeroTLAB" is specified along with GC options ^^^^^^^ XNA 8162338: AArch64: Intrinsify fused mac operations ^^^^^^^ Depends on previous enhancement. XN 8171008: Integrate AOT compiler into JDK XN 8166417: Integrate Graal-core into JDK for AOT compiler XN 8170106: AArch64: Multiple JVMCI issues NA 8170100: AArch64: Crash in C1-compiled code accessing References ^^^^^^^ XN 8170098: AArch64: VM is extremely slow with JVMTI debugging enabled N 8169711: CDS does not patch entry trampoline if intrinsic method is disabled XNA 8169901: AArch64: CompareAndExchange intrinsics clobber address register NA 8169529: AArch64: Revert old JDK-8167595 changes after JDK-8159035 fix is pushed ^^^^^^^ NA 8169497: Aarch64: Improve internal array handling ^^^^^^^ N 8167578: C1: compiler.escapeAnalysis.TestArrayCopy fails to throw ArrayStoreException XN 8166561: [s390] Adaptions needed for s390 port in C1 and C2. XN 8166560: [s390] Basic enablement of s390 port. XNA 8168567: Fix for 8166972 breaks aarch64 build XN 8166679: JNI AsyncGetCallTrace replaces topmost frame name with starting with Java 9 b133 N 8160411: SIGSEGV in frame::safe_for_sender on incomplete DeoptimizationBlob frame -- Event Horizon -- P 8167421: AArch64: in one core system, fatal error: Illegal threadstate encountered X 8166972: [JVMCI] reduce size of interpreter when JVMCI is enabled P 8167595: AArch64: SEGV in stub code cipherBlockChaining_decryptAESCrypt X 8168086: 8166869 broke jvmci build on aarch64 P 8165673: AArch64: Fix JNI floating point argument handling A 8167200: AArch64: Broken stack pointer adjustment in interpreter N 8155729: C2: Skip transformation of LoadConP for heap-based compressed oops A 8157708: aarch64: StrIndexOfChar intrinsic is not implemented N 8166140: C1: Possible integer overflow in LIRGenerator::generate_address on several platforms N 8154122: Intrinsify fused mac operations N 8166433: AArch64: Fix for JDK-8163014 broke AArch64 build N 8164086: Checked JNI pending exception check should be cleared when returning to Java frame N 8163014: Mysterious/wrong value for "long" frame local variable on 64-bit 8140520: segfault on solaris-amd64 with "-XX:VMThreadStackSize=1" option jdk-9+135 \/ 8157907: Incorrect inclusion of atomic.hpp instead of atomic.inline.hpp AN 8164113: AArch64: follow-up the fix for 8161598 8037138: x86: problem with JVMTI breakpoint 8159284: bigapps/Jetty - assert(jfa->last_Java_sp() > sp()) failed with JFR in use AN 8161190: AArch64: Fix overflow in immediate cmp instruction N 8160245: C1: Clean up platform #defines in c1_LIR.hpp. N 8161598: Kitchensink fails: assert(nm->insts_contains(original_pc)) failed: original PC must be in nmethod/CompiledMethod A=AAarch64 specific. X=Doesn't apply to JDK8u N=Not backported to aarch64-port/jdk8u M=Not in jdk8u P=Ported On 3 April 2017 at 18:51, Andrew Haley wrote: > On 03/04/17 18:50, Stuart Monteith wrote: >> For clarity, the patchset is: >> >> 8173472: AArch64: C1 comparisons with null only use 32-bit instructions >> https://bugs.openjdk.java.net/browse/JDK-8173472 >> http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/b53b0251e250 >> >> 8172881: AArch64: assertion failure: the int pressure is incorrect >> https://bugs.openjdk.java.net/browse/JDK-8172881 >> http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/bfa8e4b0d4e2 >> >> >> 8170100: AArch64: Crash in C1-compiled code accessing References >> https://bugs.openjdk.java.net/browse/JDK-8170100 >> http://hg.openjdk.java.net/jdk9/dev/hotspot/rev/52d18f20804b > > That looks great. These are all very low-risk to apply, and obviously > fix real bugs. > > Andrew. > From andrey.petushkov at gmail.com Mon Apr 3 20:45:25 2017 From: andrey.petushkov at gmail.com (Andrey Petushkov) Date: Mon, 03 Apr 2017 20:45:25 +0000 Subject: [aarch64-port-dev ] SUN_ARCH_ABI property not set or in release file for aarch64 builds In-Reply-To: <58E2AE03.1010309@cjnash.com> References: <58E27DFF.6010007@cjnash.com> <52B351FD-BC1A-4B0D-8E4D-16CD72BCA0E3@oracle.com> <58E2AE03.1010309@cjnash.com> Message-ID: Hi Simon, from the first glance it's set with the command line when the binary is built. so there is no code change is required but rather build system setup. we can ensure Azul is building with it so it will propagate into any downstream distribution taking our binaries. yet it might help you or might not depending on what you call the "openjdk build" Regards, Andrey On Mon, Apr 3, 2017, 23:18 Simon Nash wrote: > On 03/04/2017 17:58, Bob Vandette wrote: > > The Oracle binaries for JDK 8 and JDK 9 Linux arm already include this > property for the > > 32-bit ARM binaries. > > > > The only release that in question is the 64-bit aarch64 Linux > distribution. There?s really > > no need for this property since there?s only 1 ABI that?s widely used > today on that > > architecture. > > > > Bob. > > > > My comment was about the OpenJDK aarch32 builds. From your original post, > I have the impression that the OpenJDK aarch32 builds don't set this > property. > If it could be added for the OpenJDK aarch32 builds, this would be very > useful > for my application. > > I understand that this is not needed for aarch64 builds. > > Simon > > >> On Apr 3, 2017, at 12:53 PM, Simon Nash wrote: > >> > >> Hi Bob, > >> I would find such a property very useful. > >> > >> My application is mostly written in Java but also uses a native library > >> that is loaded dynamically by the Java code. In order to distribute > >> fewer versions of the application and make things simpler for users, > >> I have recently started packaging multiple versions of the native > library > >> (for example, Intel x86 and Intel x64) in a single version of the > >> application and using Java runtime properties to determine which of > >> these native libraries to load. > >> > >> I would like to do this for gnueabi and gnueabihf if I could find a > >> reliable way to determine at runtime which of these native libraries > >> is needed. It sounds like this property would be an ideal solution. > >> > >> Best regards, > >> Simon > >> > >> On 03/04/2017 16:57, Bob Vandette wrote: > >>> I?m inclined to not fix this bug but thought I?d bring it to your > attention just in case. > >>> I assume that OpenJDK ARM builds never set this property anyway, right? > >>> https://bugs.openjdk.java.net/browse/JDK-8177976 < > https://bugs.openjdk.java.net/browse/JDK-8177976> > >>> Bob. > > > > > > From magnus.ihse.bursie at oracle.com Tue Apr 4 08:04:22 2017 From: magnus.ihse.bursie at oracle.com (Magnus Ihse Bursie) Date: Tue, 4 Apr 2017 10:04:22 +0200 Subject: [aarch64-port-dev ] Review Request JDK-8175819: OS name and arch in JMOD files should match the values as in the bundle name In-Reply-To: <5AD5D871-1673-4D4C-89CC-CEB1B76FDA75@oracle.com> References: <20170403131552.834209932@eggemoggin.niobe.net> <58E2B212.6080605@cjnash.com> <20170403143925.120730340@eggemoggin.niobe.net> <5AD5D871-1673-4D4C-89CC-CEB1B76FDA75@oracle.com> Message-ID: <35c8724e-f371-b213-1582-027bcafe3af4@oracle.com> On 2017-04-03 23:50, Mandy Chung wrote: >> On Apr 3, 2017, at 2:39 PM, mark.reinhold at oracle.com wrote: >> >> 2017/4/3 13:35:30 -0700, simon at cjnash.com: >>> On 03/04/2017 21:15, mark.reinhold at oracle.com wrote: >>>> 2017/4/3 11:41:03 -0700, mandy.chung at oracle.com: >>>>> Webrev: >>>>> http://cr.openjdk.java.net/~mchung/jdk9/webrevs/8175819/webrev.00/ >>>>> >>>>> ... >>>>> >>>>> This shows the old and new value of OS_NAME/OS_ARCH properties >>>>> in the `release` file: >>>>> >>>>> JDK 8 JDK 9 >>>>> ----- ----- >>>>> OS_NAME Linux linux >>>>> SunOS solaris >>>>> Darwin osx >>>>> Windows windows >>>>> >>>>> OS_ARCH i386,x86 x86 >>>>> i586,amd64,x86_64 x64 >>>>> sparcv9 sparcv9 >>>>> arm arm32 >>>>> aarch64 arm64 >>> I am not sure why we would change to osx for Mac when the Mac developers >>> have recently dropped the Mac OS X terminology and changed it to macOS. >> Agreed -- we should change OS_NAME from "Darwin" to "macos?. > OK. Should the bundle names be updated to reflect this change? > In any case, it is a separate issue. > > JDK 8 JDK 9 > ----- ----- > OS_NAME Linux linux > SunOS solaris > Darwin macos > Windows windows > > OS_ARCH i386,x86 x86 > i586,amd64,x86_64 amd64 > sparcv9 sparcv9 > arm arm32 > aarch64 arm64 If we are making changes to the original proposal from JDK-8175819, then I just want to add my few cents: Why change from the well-established "aarch64" to the virtually unused "arm64"? As far as I know, using the name "arm64" for the aarch64 platform is something that has only been done in the (recently opened) closed Oracle port. This change, however, proposes to change the value in the release file even for the open aarch64 port, which has always been known by that name. /Magnus > > Mandy > From aph at redhat.com Tue Apr 4 08:39:00 2017 From: aph at redhat.com (Andrew Haley) Date: Tue, 4 Apr 2017 09:39:00 +0100 Subject: [aarch64-port-dev ] Review Request JDK-8175819: OS name and arch in JMOD files should match the values as in the bundle name In-Reply-To: <35c8724e-f371-b213-1582-027bcafe3af4@oracle.com> References: <20170403131552.834209932@eggemoggin.niobe.net> <58E2B212.6080605@cjnash.com> <20170403143925.120730340@eggemoggin.niobe.net> <5AD5D871-1673-4D4C-89CC-CEB1B76FDA75@oracle.com> <35c8724e-f371-b213-1582-027bcafe3af4@oracle.com> Message-ID: On 04/04/17 09:04, Magnus Ihse Bursie wrote: > Why change from the well-established "aarch64" to the virtually unused > "arm64"? As far as I know, using the name "arm64" for the aarch64 > platform is something that has only been done in the (recently opened) > closed Oracle port. This change, however, proposes to change the value > in the release file even for the open aarch64 port, which has always > been known by that name. That's definitely wrong. The name of the architecture is "aarch64". "arm64" is not a thing. Andrew. From stuart.monteith at linaro.org Tue Apr 4 09:55:47 2017 From: stuart.monteith at linaro.org (Stuart Monteith) Date: Tue, 4 Apr 2017 10:55:47 +0100 Subject: [aarch64-port-dev ] Review Request JDK-8175819: OS name and arch in JMOD files should match the values as in the bundle name In-Reply-To: References: <20170403131552.834209932@eggemoggin.niobe.net> <58E2B212.6080605@cjnash.com> <20170403143925.120730340@eggemoggin.niobe.net> <5AD5D871-1673-4D4C-89CC-CEB1B76FDA75@oracle.com> <35c8724e-f371-b213-1582-027bcafe3af4@oracle.com> Message-ID: ARMv8-A introduced the AArch64 execution state and the A64 instruction set. The AArch32 execution state was created with the T32 and A32 instruction sets (that are almost identical to the ARMv7 instruction sets). Officially, "arm64" has no meaning. Unfortunately, adoption of this terminology hasn't been consistent, but I believe it is fitting that OpenJDK is consistent with the GNU triples, which do use aarch64. "arm64", at best, seems to mean machines/kernels that support ARMv8-A, which may or may not have AArch64 support. BR, Stuart On 4 April 2017 at 09:39, Andrew Haley wrote: > On 04/04/17 09:04, Magnus Ihse Bursie wrote: >> Why change from the well-established "aarch64" to the virtually unused >> "arm64"? As far as I know, using the name "arm64" for the aarch64 >> platform is something that has only been done in the (recently opened) >> closed Oracle port. This change, however, proposes to change the value >> in the release file even for the open aarch64 port, which has always >> been known by that name. > > That's definitely wrong. The name of the architecture is "aarch64". > "arm64" is not a thing. > > Andrew. > From aph at redhat.com Tue Apr 4 13:06:25 2017 From: aph at redhat.com (Andrew Haley) Date: Tue, 4 Apr 2017 14:06:25 +0100 Subject: [aarch64-port-dev ] Review Request JDK-8175819: OS name and arch in JMOD files should match the values as in the bundle name In-Reply-To: References: <20170403131552.834209932@eggemoggin.niobe.net> <58E2B212.6080605@cjnash.com> <20170403143925.120730340@eggemoggin.niobe.net> <5AD5D871-1673-4D4C-89CC-CEB1B76FDA75@oracle.com> <35c8724e-f371-b213-1582-027bcafe3af4@oracle.com> Message-ID: On 04/04/17 10:55, Stuart Monteith wrote: > "arm64", at best, seems to mean machines/kernels that support ARMv8-A, > which may or may not have AArch64 support. TL/DR: Linus really didn't like "aach64" as a name, so the kernel had to be named "arm64". Thankfully, nobody else had to pay attention to this decision. https://lkml.org/lkml/2012/7/15/133 Andrew. From mark.reinhold at oracle.com Tue Apr 4 15:12:15 2017 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Tue, 04 Apr 2017 08:12:15 -0700 Subject: [aarch64-port-dev ] Review Request JDK-8175819: OS name and arch in JMOD files should match the values as in the bundle name In-Reply-To: <35c8724e-f371-b213-1582-027bcafe3af4@oracle.com> References: <20170403131552.834209932@eggemoggin.niobe.net> <58E2B212.6080605@cjnash.com> <20170403143925.120730340@eggemoggin.niobe.net> <5AD5D871-1673-4D4C-89CC-CEB1B76FDA75@oracle.com> <35c8724e-f371-b213-1582-027bcafe3af4@oracle.com> Message-ID: <20170404081215.364493885@eggemoggin.niobe.net> 2017/4/4 1:04:22 -0700, magnus.ihse.bursie at oracle.com: > On 2017-04-03 23:50, Mandy Chung wrote: >> ... >> >> JDK 8 JDK 9 >> ----- ----- >> OS_NAME Linux linux >> SunOS solaris >> Darwin macos >> Windows windows >> >> OS_ARCH i386,x86 x86 >> i586,amd64,x86_64 amd64 >> sparcv9 sparcv9 >> arm arm32 >> aarch64 arm64 > > If we are making changes to the original proposal from JDK-8175819, then > I just want to add my few cents: > > Why change from the well-established "aarch64" to the virtually unused > "arm64"? As far as I know, using the name "arm64" for the aarch64 > platform is something that has only been done in the (recently opened) > closed Oracle port. This change, however, proposes to change the value > in the release file even for the open aarch64 port, which has always > been known by that name. The trouble here is that "arm64" and "aarch64" are effectively synonyms for the ISA, but in the JDK we've wound up using them as the names of two different ports. A JMOD file built for the 64-bit ARM architecture will (one hopes) run equally well on either port. Which name should we use in JMOD files, "arm64" or "aarch64"? My sense is that "arm64" is more immediately understood by developers at large even if "aarch64" is more correct in the eyes of ARM Holdings plc, but I could be wrong. For what it's worth, the Linux distros aren't consistent: Debian-based distros use "arm64", while Red Hat / Fedora seem to prefer "aarch64". - Mark From aph at redhat.com Tue Apr 4 15:22:50 2017 From: aph at redhat.com (Andrew Haley) Date: Tue, 4 Apr 2017 16:22:50 +0100 Subject: [aarch64-port-dev ] Review Request JDK-8175819: OS name and arch in JMOD files should match the values as in the bundle name In-Reply-To: <20170404081215.364493885@eggemoggin.niobe.net> References: <20170403131552.834209932@eggemoggin.niobe.net> <58E2B212.6080605@cjnash.com> <20170403143925.120730340@eggemoggin.niobe.net> <5AD5D871-1673-4D4C-89CC-CEB1B76FDA75@oracle.com> <35c8724e-f371-b213-1582-027bcafe3af4@oracle.com> <20170404081215.364493885@eggemoggin.niobe.net> Message-ID: On 04/04/17 16:12, mark.reinhold at oracle.com wrote: > The trouble here is that "arm64" and "aarch64" are effectively synonyms > for the ISA, but in the JDK we've wound up using them as the names of > two different ports. > > A JMOD file built for the 64-bit ARM architecture will (one hopes) run > equally well on either port. Which name should we use in JMOD files, > "arm64" or "aarch64"? My sense is that "arm64" is more immediately > understood by developers at large even if "aarch64" is more correct > in the eyes of ARM Holdings plc, but I could be wrong. I think that you are wrong. > For what it's worth, the Linux distros aren't consistent: Debian-based > distros use "arm64", while Red Hat / Fedora seem to prefer "aarch64". The name of the processor architecture is "AArch64". The name of the Linux kernel architecture is "arm64"; the name of all of userspace is "aarch64", on all distros. The kernel is out of step here, for no better reason than Linus Torvalds didn't like "aarch64". Andrew. From bob.vandette at oracle.com Tue Apr 4 16:03:41 2017 From: bob.vandette at oracle.com (Bob Vandette) Date: Tue, 4 Apr 2017 12:03:41 -0400 Subject: [aarch64-port-dev ] Review Request JDK-8175819: OS name and arch in JMOD files should match the values as in the bundle name In-Reply-To: <20170404081215.364493885@eggemoggin.niobe.net> References: <20170403131552.834209932@eggemoggin.niobe.net> <58E2B212.6080605@cjnash.com> <20170403143925.120730340@eggemoggin.niobe.net> <5AD5D871-1673-4D4C-89CC-CEB1B76FDA75@oracle.com> <35c8724e-f371-b213-1582-027bcafe3af4@oracle.com> <20170404081215.364493885@eggemoggin.niobe.net> Message-ID: > On Apr 4, 2017, at 11:12 AM, mark.reinhold at oracle.com wrote: > > 2017/4/4 1:04:22 -0700, magnus.ihse.bursie at oracle.com: >> On 2017-04-03 23:50, Mandy Chung wrote: >>> ... >>> >>> JDK 8 JDK 9 >>> ----- ----- >>> OS_NAME Linux linux >>> SunOS solaris >>> Darwin macos >>> Windows windows >>> >>> OS_ARCH i386,x86 x86 >>> i586,amd64,x86_64 amd64 >>> sparcv9 sparcv9 >>> arm arm32 >>> aarch64 arm64 >> >> If we are making changes to the original proposal from JDK-8175819, then >> I just want to add my few cents: >> >> Why change from the well-established "aarch64" to the virtually unused >> "arm64"? As far as I know, using the name "arm64" for the aarch64 >> platform is something that has only been done in the (recently opened) >> closed Oracle port. This change, however, proposes to change the value >> in the release file even for the open aarch64 port, which has always >> been known by that name. > > The trouble here is that "arm64" and "aarch64" are effectively synonyms > for the ISA, but in the JDK we've wound up using them as the names of > two different ports. Well sort of ? We are only using arm64 as a configure option to enable building the unified ARM32/64 port and a label in Jira to identify which port a bug or RFE is related to. Both 64-bit ARM ports have been using aarch64 for the os.name property since day one and I think we should stick to this name in the release file to avoid any confusion. Bob. > > A JMOD file built for the 64-bit ARM architecture will (one hopes) run > equally well on either port. Which name should we use in JMOD files, > "arm64" or "aarch64"? My sense is that "arm64" is more immediately > understood by developers at large even if "aarch64" is more correct > in the eyes of ARM Holdings plc, but I could be wrong. > > For what it's worth, the Linux distros aren't consistent: Debian-based > distros use "arm64", while Red Hat / Fedora seem to prefer "aarch64". > > - Mark From ci_notify at linaro.org Tue Apr 4 16:23:52 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Tue, 4 Apr 2017 16:23:52 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <1843228896.250.1491323032791.JavaMail.jenkins@ci.linaro.org> 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/093/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/01 pass: 1,387; fail: 5 Build 1: aarch64/2017/mar/02 pass: 1,387; fail: 5 Build 2: aarch64/2017/mar/03 pass: 1,387; fail: 5 Build 3: aarch64/2017/mar/08 pass: 1,388; fail: 5 Build 4: aarch64/2017/mar/11 pass: 1,388; fail: 5 Build 5: aarch64/2017/mar/13 pass: 1,388; fail: 5 Build 6: aarch64/2017/mar/15 pass: 1,387; fail: 6 Build 7: aarch64/2017/mar/17 pass: 1,390; fail: 6 Build 8: aarch64/2017/mar/19 pass: 1,391; fail: 5 Build 9: aarch64/2017/mar/21 pass: 1,391; fail: 5 Build 10: aarch64/2017/mar/25 pass: 1,393; fail: 4 Build 11: aarch64/2017/mar/27 pass: 1,393; fail: 4 Build 12: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 13: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 14: aarch64/2017/apr/03 pass: 1,396; fail: 4 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/01 pass: 7,264; fail: 711; error: 17 Build 1: aarch64/2017/mar/02 pass: 7,272; fail: 705; error: 15 Build 2: aarch64/2017/mar/03 pass: 7,252; fail: 720; error: 21 Build 3: aarch64/2017/mar/08 pass: 7,251; fail: 720; error: 23 Build 4: aarch64/2017/mar/11 pass: 7,263; fail: 718; error: 18 Build 5: aarch64/2017/mar/13 pass: 7,268; fail: 710; error: 21 Build 6: aarch64/2017/mar/15 pass: 7,283; fail: 693; error: 25 Build 7: aarch64/2017/mar/17 pass: 7,273; fail: 709; error: 20 Build 8: aarch64/2017/mar/19 pass: 7,253; fail: 727; error: 24 Build 9: aarch64/2017/mar/21 pass: 7,294; fail: 689; error: 21 Build 10: aarch64/2017/mar/25 pass: 7,278; fail: 713; error: 23 Build 11: aarch64/2017/mar/27 pass: 7,304; fail: 690; error: 20 Build 12: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 13: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 14: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/01 pass: 3,862; error: 2 Build 1: aarch64/2017/mar/02 pass: 3,862; error: 2 Build 2: aarch64/2017/mar/03 pass: 3,863; error: 2 Build 3: aarch64/2017/mar/08 pass: 3,866; error: 1 Build 4: aarch64/2017/mar/11 pass: 3,871; error: 2 Build 5: aarch64/2017/mar/13 pass: 3,872; error: 1 Build 6: aarch64/2017/mar/15 pass: 3,874; error: 4 Build 7: aarch64/2017/mar/17 pass: 3,878; error: 2 Build 8: aarch64/2017/mar/19 pass: 3,878; error: 2 Build 9: aarch64/2017/mar/21 pass: 3,876; error: 5 Build 10: aarch64/2017/mar/25 pass: 3,886; fail: 1 Build 11: aarch64/2017/mar/27 pass: 3,883; error: 4 Build 12: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 13: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 14: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/01 pass: 1,390; fail: 5 Build 1: aarch64/2017/mar/02 pass: 1,390; fail: 5 Build 2: aarch64/2017/mar/03 pass: 1,390; fail: 5 Build 3: aarch64/2017/mar/08 pass: 1,391; fail: 6 Build 4: aarch64/2017/mar/11 pass: 1,392; fail: 5 Build 5: aarch64/2017/mar/13 pass: 1,392; fail: 5 Build 6: aarch64/2017/mar/15 pass: 1,392; fail: 5 Build 7: aarch64/2017/mar/17 pass: 1,395; fail: 5 Build 8: aarch64/2017/mar/19 pass: 1,395; fail: 5 Build 9: aarch64/2017/mar/21 pass: 1,394; fail: 6 Build 10: aarch64/2017/mar/25 pass: 1,397; fail: 4 Build 11: aarch64/2017/mar/27 pass: 1,396; fail: 5 Build 12: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 13: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 14: aarch64/2017/apr/03 pass: 1,400; fail: 4 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/01 pass: 7,266; fail: 710; error: 16 Build 1: aarch64/2017/mar/02 pass: 7,284; fail: 689; error: 19 Build 2: aarch64/2017/mar/03 pass: 7,257; fail: 720; error: 16 Build 3: aarch64/2017/mar/08 pass: 7,296; fail: 679; error: 19 Build 4: aarch64/2017/mar/11 pass: 7,261; fail: 722; error: 16 Build 5: aarch64/2017/mar/13 pass: 7,290; fail: 687; error: 22 Build 6: aarch64/2017/mar/15 pass: 7,285; fail: 697; error: 19 Build 7: aarch64/2017/mar/17 pass: 7,278; fail: 703; error: 21 Build 8: aarch64/2017/mar/19 pass: 7,261; fail: 723; error: 20 Build 9: aarch64/2017/mar/21 pass: 7,271; fail: 712; error: 21 Build 10: aarch64/2017/mar/25 pass: 7,284; fail: 708; error: 22 Build 11: aarch64/2017/mar/27 pass: 7,297; fail: 695; error: 22 Build 12: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 13: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 14: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/01 pass: 3,860; error: 4 Build 1: aarch64/2017/mar/02 pass: 3,858; fail: 1; error: 5 Build 2: aarch64/2017/mar/03 pass: 3,863; fail: 1; error: 2 Build 3: aarch64/2017/mar/08 pass: 3,867 Build 4: aarch64/2017/mar/11 pass: 3,873 Build 5: aarch64/2017/mar/13 pass: 3,871; error: 2 Build 6: aarch64/2017/mar/15 pass: 3,878 Build 7: aarch64/2017/mar/17 pass: 3,876; error: 4 Build 8: aarch64/2017/mar/19 pass: 3,876; error: 4 Build 9: aarch64/2017/mar/21 pass: 3,879; error: 2 Build 10: aarch64/2017/mar/25 pass: 3,885; error: 2 Build 11: aarch64/2017/mar/27 pass: 3,881; error: 6 Build 12: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 13: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 14: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 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.89x 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: 117.63 Client 72.38 / Client 2014-04-01 (43.00): 1.68x Server 117.63 / Server 2014-04-01 (71.00): 1.66x 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-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/ 2017-03-26 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/084/results/ 2017-03-28 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/086/results/ 2017-03-31 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/089/results/ 2017-04-02 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/091/results/ 2017-04-04 pass rate: 11550/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/093/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/ From mark.reinhold at oracle.com Tue Apr 4 16:35:57 2017 From: mark.reinhold at oracle.com (mark.reinhold at oracle.com) Date: Tue, 04 Apr 2017 09:35:57 -0700 Subject: [aarch64-port-dev ] Review Request JDK-8175819: OS name and arch in JMOD files should match the values as in the bundle name In-Reply-To: References: <20170403131552.834209932@eggemoggin.niobe.net> <58E2B212.6080605@cjnash.com> <20170403143925.120730340@eggemoggin.niobe.net> <5AD5D871-1673-4D4C-89CC-CEB1B76FDA75@oracle.com> <35c8724e-f371-b213-1582-027bcafe3af4@oracle.com> <20170404081215.364493885@eggemoggin.niobe.net> Message-ID: <20170404093557.376393610@eggemoggin.niobe.net> 2017/4/4 8:22:50 -0700, aph at redhat.com: > On 04/04/17 16:12, mark.reinhold at oracle.com wrote: >> The trouble here is that "arm64" and "aarch64" are effectively synonyms >> for the ISA, but in the JDK we've wound up using them as the names of >> two different ports. >> >> A JMOD file built for the 64-bit ARM architecture will (one hopes) run >> equally well on either port. Which name should we use in JMOD files, >> "arm64" or "aarch64"? My sense is that "arm64" is more immediately >> understood by developers at large even if "aarch64" is more correct >> in the eyes of ARM Holdings plc, but I could be wrong. > > I think that you are wrong. > >> For what it's worth, the Linux distros aren't consistent: Debian-based >> distros use "arm64", while Red Hat / Fedora seem to prefer "aarch64". > > The name of the processor architecture is "AArch64". The name of the > Linux kernel architecture is "arm64"; the name of all of userspace is > "aarch64", on all distros. The kernel is out of step here, for no > better reason than Linus Torvalds didn't like "aarch64". Thanks for the background -- I wasn't aware of that. Given that "os.arch" is "aarch64" for both ports, as Bob points out, then we should use "aarch64" in JMOD files as well. This does raise another question, though: Should we use "aarch32" instead of "arm32" for the 32-bit ARM architecture? - Mark From aph at redhat.com Tue Apr 4 16:38:04 2017 From: aph at redhat.com (aph at redhat.com) Date: Tue, 04 Apr 2017 16:38:04 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/hotspot: 3 new changesets Message-ID: <201704041638.v34Gc4Tg012593@aojmv0008.oracle.com> Changeset: f2330cb3af9f Author: aph Date: 2017-04-04 14:49 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/f2330cb3af9f 8173472: AArch64: C1 comparisons with null only use 32-bit instructions Reviewed-by: roland ! src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp Changeset: 089205f7bfd2 Author: njian Date: 2017-01-22 16:33 +0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/089205f7bfd2 8172881: AArch64: assertion failure: the int pressure is incorrect Summary: Change the dst register type of get_and_setI/L/N/P from any register to non-special register. Reviewed-by: aph Contributed-by: yang.zhang at linaro.org ! src/cpu/aarch64/vm/aarch64.ad Changeset: e5d7f637919f Author: aph Date: 2017-04-04 14:59 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/e5d7f637919f 8170100: AArch64: Crash in C1-compiled code accessing References Reviewed-by: roland ! src/cpu/aarch64/vm/templateInterpreter_aarch64.cpp From aph at redhat.com Tue Apr 4 16:39:17 2017 From: aph at redhat.com (Andrew Haley) Date: Tue, 4 Apr 2017 17:39:17 +0100 Subject: [aarch64-port-dev ] Review Request JDK-8175819: OS name and arch in JMOD files should match the values as in the bundle name In-Reply-To: <20170404093557.376393610@eggemoggin.niobe.net> References: <20170403131552.834209932@eggemoggin.niobe.net> <58E2B212.6080605@cjnash.com> <20170403143925.120730340@eggemoggin.niobe.net> <5AD5D871-1673-4D4C-89CC-CEB1B76FDA75@oracle.com> <35c8724e-f371-b213-1582-027bcafe3af4@oracle.com> <20170404081215.364493885@eggemoggin.niobe.net> <20170404093557.376393610@eggemoggin.niobe.net> Message-ID: <921dba93-4497-55b4-3ac4-dd3c6c559deb@redhat.com> On 04/04/17 17:35, mark.reinhold at oracle.com wrote: > This does raise another question, though: Should we use "aarch32" > instead of "arm32" for the 32-bit ARM architecture? Probably not. I believe that "aarch32" is historical revisionism coming from ARM: it didn't exist as a name before AArch64 came out. AFAICR... Andrew. From bob.vandette at oracle.com Tue Apr 4 16:47:50 2017 From: bob.vandette at oracle.com (Bob Vandette) Date: Tue, 4 Apr 2017 12:47:50 -0400 Subject: [aarch64-port-dev ] Review Request JDK-8175819: OS name and arch in JMOD files should match the values as in the bundle name In-Reply-To: <20170404093557.376393610@eggemoggin.niobe.net> References: <20170403131552.834209932@eggemoggin.niobe.net> <58E2B212.6080605@cjnash.com> <20170403143925.120730340@eggemoggin.niobe.net> <5AD5D871-1673-4D4C-89CC-CEB1B76FDA75@oracle.com> <35c8724e-f371-b213-1582-027bcafe3af4@oracle.com> <20170404081215.364493885@eggemoggin.niobe.net> <20170404093557.376393610@eggemoggin.niobe.net> Message-ID: <963C74B3-377C-40C4-8D0A-73CF506D035C@oracle.com> > On Apr 4, 2017, at 12:35 PM, mark.reinhold at oracle.com wrote: > > 2017/4/4 8:22:50 -0700, aph at redhat.com: >> On 04/04/17 16:12, mark.reinhold at oracle.com wrote: >>> The trouble here is that "arm64" and "aarch64" are effectively synonyms >>> for the ISA, but in the JDK we've wound up using them as the names of >>> two different ports. >>> >>> A JMOD file built for the 64-bit ARM architecture will (one hopes) run >>> equally well on either port. Which name should we use in JMOD files, >>> "arm64" or "aarch64"? My sense is that "arm64" is more immediately >>> understood by developers at large even if "aarch64" is more correct >>> in the eyes of ARM Holdings plc, but I could be wrong. >> >> I think that you are wrong. >> >>> For what it's worth, the Linux distros aren't consistent: Debian-based >>> distros use "arm64", while Red Hat / Fedora seem to prefer "aarch64". >> >> The name of the processor architecture is "AArch64". The name of the >> Linux kernel architecture is "arm64"; the name of all of userspace is >> "aarch64", on all distros. The kernel is out of step here, for no >> better reason than Linus Torvalds didn't like "aarch64". > > Thanks for the background -- I wasn't aware of that. > > Given that "os.arch" is "aarch64" for both ports, as Bob points out, > then we should use "aarch64" in JMOD files as well. > > This does raise another question, though: Should we use "aarch32" > instead of "arm32" for the 32-bit ARM architecture? 32 bit ARM is a bit more challenging since OS vendors sometime encode the architecture version (armv5, armv6, armv7) and endianess into the uname -p output. aarch32 has special meaning (it?s the arch for running 32-bit arm instructions on an armv8 processor.) and I haven?t seen any use of arm32. I suggest we stick with arm. Bob. > > - Mark From stuart.monteith at linaro.org Wed Apr 5 08:37:32 2017 From: stuart.monteith at linaro.org (Stuart Monteith) Date: Wed, 5 Apr 2017 09:37:32 +0100 Subject: [aarch64-port-dev ] Review Request JDK-8175819: OS name and arch in JMOD files should match the values as in the bundle name In-Reply-To: <921dba93-4497-55b4-3ac4-dd3c6c559deb@redhat.com> References: <20170403131552.834209932@eggemoggin.niobe.net> <58E2B212.6080605@cjnash.com> <20170403143925.120730340@eggemoggin.niobe.net> <5AD5D871-1673-4D4C-89CC-CEB1B76FDA75@oracle.com> <35c8724e-f371-b213-1582-027bcafe3af4@oracle.com> <20170404081215.364493885@eggemoggin.niobe.net> <20170404093557.376393610@eggemoggin.niobe.net> <921dba93-4497-55b4-3ac4-dd3c6c559deb@redhat.com> Message-ID: It is historical revisionism. AArch32 was introduced with ARMv8, before there was no need to distinguish between 32-bit and 64-bit execution states. If people are selecting, say, JNI libraries, based on os.arch, then there is every reason to be consistent. On 4 April 2017 at 17:39, Andrew Haley wrote: > On 04/04/17 17:35, mark.reinhold at oracle.com wrote: >> This does raise another question, though: Should we use "aarch32" >> instead of "arm32" for the 32-bit ARM architecture? > > Probably not. I believe that "aarch32" is historical revisionism > coming from ARM: it didn't exist as a name before AArch64 came out. > AFAICR... > > Andrew. From andrey.petushkov at gmail.com Wed Apr 5 13:43:17 2017 From: andrey.petushkov at gmail.com (Andrey Petushkov) Date: Wed, 5 Apr 2017 16:43:17 +0300 Subject: [aarch64-port-dev ] SUN_ARCH_ABI property not set or in release file for aarch64 builds In-Reply-To: <58E2B73C.5010004@cjnash.com> References: <58E27DFF.6010007@cjnash.com> <52B351FD-BC1A-4B0D-8E4D-16CD72BCA0E3@oracle.com> <58E2AE03.1010309@cjnash.com> <58E2B73C.5010004@cjnash.com> Message-ID: Dear Simon, Sorry for the delay. I was trying to build the code so that it has the property, but apparently the necessary piece of magic is missing. The location for that piece is only present in the Oracle?s arm port repos, not anywhere else, including stock OpenJDK 8u and 9. I doubt we want to integrate it just because of this property. So we will think how to play around it.. > 03 Apr 2017, at 23:57, Simon Nash wrote: > > Hi Andrey, > I am using the OpenJDK sources in the aarch32-port repository to build > a JRE for my application, so it will help to have this property set by > this JRE. I will try my current binary to see whether this property > is already available. If you?re building from Oracle?s port I believe Bob should be able to tell how to bring the magic over. Otherwise please stay tuned, we?ll work on bringing it into the rest of aarch32 repos > > I have sucessfully built the aarch32-port sources for gnueabihf but I > could not build them for gnueabi becaise there appear to be some missing > files in the aarch32-port sources that are neeeded for softfp support. > Is this correct? If so, are there any plans to support a softfp version? Could you please indicate what repos are you building from: 8u, 9 or 9-arm3264 (aka Oracle) Thanks, Andrey > > Best regards, > Simon > > On 03/04/2017 21:45, Andrey Petushkov wrote: >> Hi Simon, >> from the first glance it's set with the command line when the binary is built. so there is no code change is required but rather build system setup. we can ensure Azul is building with it so it will propagate into any downstream distribution taking our binaries. yet it might help you or might not depending on what you call the "openjdk build" >> Regards, >> Andrey >> On Mon, Apr 3, 2017, 23:18 Simon Nash > wrote: >> On 03/04/2017 17:58, Bob Vandette wrote: >> > The Oracle binaries for JDK 8 and JDK 9 Linux arm already include >> this property for the >> > 32-bit ARM binaries. >> > >> > The only release that in question is the 64-bit aarch64 Linux >> distribution. There?s really >> > no need for this property since there?s only 1 ABI that?s widely >> used today on that >> > architecture. >> > >> > Bob. >> > >> My comment was about the OpenJDK aarch32 builds. From your original >> post, >> I have the impression that the OpenJDK aarch32 builds don't set this >> property. >> If it could be added for the OpenJDK aarch32 builds, this would be >> very useful >> for my application. >> I understand that this is not needed for aarch64 builds. >> Simon >> >> On Apr 3, 2017, at 12:53 PM, Simon Nash > > wrote: >> >> >> >> Hi Bob, >> >> I would find such a property very useful. >> >> >> >> My application is mostly written in Java but also uses a native >> library >> >> that is loaded dynamically by the Java code. In order to distribute >> >> fewer versions of the application and make things simpler for users, >> >> I have recently started packaging multiple versions of the >> native library >> >> (for example, Intel x86 and Intel x64) in a single version of the >> >> application and using Java runtime properties to determine which of >> >> these native libraries to load. >> >> >> >> I would like to do this for gnueabi and gnueabihf if I could find a >> >> reliable way to determine at runtime which of these native libraries >> >> is needed. It sounds like this property would be an ideal solution. >> >> >> >> Best regards, >> >> Simon >> >> >> >> On 03/04/2017 16:57, Bob Vandette wrote: >> >>> I?m inclined to not fix this bug but thought I?d bring it to >> your attention just in case. >> >>> I assume that OpenJDK ARM builds never set this property >> anyway, right? >> >>> https://bugs.openjdk.java.net/browse/JDK-8177976 >> >> >>> Bob. >> > >> > > From bob.vandette at oracle.com Wed Apr 5 14:24:00 2017 From: bob.vandette at oracle.com (Bob Vandette) Date: Wed, 5 Apr 2017 10:24:00 -0400 Subject: [aarch64-port-dev ] SUN_ARCH_ABI property not set or in release file for aarch64 builds In-Reply-To: References: <58E27DFF.6010007@cjnash.com> <52B351FD-BC1A-4B0D-8E4D-16CD72BCA0E3@oracle.com> <58E2AE03.1010309@cjnash.com> <58E2B73C.5010004@cjnash.com> Message-ID: <725A44EC-002E-4510-9C68-30AF42249FFC@oracle.com> > On Apr 5, 2017, at 9:43 AM, Andrey Petushkov wrote: > > Dear Simon, > > Sorry for the delay. I was trying to build the code so that it has the property, but apparently the necessary piece of magic is missing. The location for that piece is only present in the Oracle?s arm port repos, not anywhere else, including stock OpenJDK 8u and 9. I doubt we want to integrate it just because of this property. So we will think how to play around it.. > >> 03 Apr 2017, at 23:57, Simon Nash wrote: >> >> Hi Andrey, >> I am using the OpenJDK sources in the aarch32-port repository to build >> a JRE for my application, so it will help to have this property set by >> this JRE. I will try my current binary to see whether this property >> is already available. > If you?re building from Oracle?s port I believe Bob should be able to tell how to bring the magic over. Otherwise please stay tuned, we?ll work on bringing it into the rest of aarch32 repos The magic in jdk9 is pretty straight forward and should work for you. jdk9/common/autoconf/flags.m4 has this logic which is enabled if you use ?with-abi-profile # Now set JDK_ARCH_ABI_PROP_NAME. This is equivalent to the last part of the # autoconf target triplet. [ JDK_ARCH_ABI_PROP_NAME=`$ECHO $OPENJDK_TARGET_AUTOCONF_NAME | $SED -e 's/.*-\([^-]*\)$/\1/'` ] # Sanity check that it is a known ABI. if test "x$JDK_ARCH_ABI_PROP_NAME" != xgnu && \ test "x$JDK_ARCH_ABI_PROP_NAME" != xgnueabi && \ test "x$JDK_ARCH_ABI_PROP_NAME" != xgnueabihf; then AC_MSG_WARN([Unknown autoconf target triplet ABI: "$JDK_ARCH_ABI_PROP_NAME"]) fi The jdk sources use JDK_ARCH_ABI_PROP_NAME here: jdk9/jdk/src/java.base/share/native/libjava/java_props.h:#ifdef JDK_ARCH_ABI_PROP_NAME jdk9/jdk/src/java.base/share/native/libjava/System.c:#ifdef JDK_ARCH_ABI_PROP_NAME jdk9/jdk/src/java.base/unix/native/libjava/java_props_md.c:#ifdef JDK_ARCH_ABI_PROP_NAME jdk9/jdk/src/java.base/unix/native/libjava/java_props_md.c: sprops.sun_arch_abi = JDK_ARCH_ABI_PROP_NAME; jdk9/make/ReleaseFile.gmk: $(if $(JDK_ARCH_ABI_PROP_NAME), \ jdk9/make/ReleaseFile.gmk: $(call info-file-item, "SUN_ARCH_ABI", "$(JDK_ARCH_ABI_PROP_NAME)?)) The only difference in jdk8 is that you have to explicitly set the architecture and JDK_ARCH_ABI_PROP_NAME using ?with-extra-cflags. Here are some configurations that we use: --with-extra-cflags="-mthumb -march=armv7-a -mfloat-abi=hard -mfpu=vfp -DFLOAT_ARCH=-vfp-hflt -DJDK_ARCH_ABI_PROP_NAME=\\"gnueabihf\\"" --with-extra-cflags="-marm -march=armv6 -mfloat-abi=softfp -mfpu=vfp -DFLOAT_ARCH=-vfp-sflt -DJDK_ARCH_ABI_PROP_NAME=\\"gnueabi\\"? --with-extra-cflags="-marm -march=armv5t -msoft-float -mfpu=vfp -DJDK_ARCH_ABI_PROP_NAME=\\"gnueabi\\?" Bob. >> >> I have sucessfully built the aarch32-port sources for gnueabihf but I >> could not build them for gnueabi becaise there appear to be some missing >> files in the aarch32-port sources that are neeeded for softfp support. >> Is this correct? If so, are there any plans to support a softfp version? > Could you please indicate what repos are you building from: 8u, 9 or 9-arm3264 (aka Oracle) > > Thanks, > Andrey >> >> Best regards, >> Simon >> >> On 03/04/2017 21:45, Andrey Petushkov wrote: >>> Hi Simon, >>> from the first glance it's set with the command line when the binary is built. so there is no code change is required but rather build system setup. we can ensure Azul is building with it so it will propagate into any downstream distribution taking our binaries. yet it might help you or might not depending on what you call the "openjdk build" >>> Regards, >>> Andrey >>> On Mon, Apr 3, 2017, 23:18 Simon Nash > wrote: >>> On 03/04/2017 17:58, Bob Vandette wrote: >>>> The Oracle binaries for JDK 8 and JDK 9 Linux arm already include >>> this property for the >>>> 32-bit ARM binaries. >>>> >>>> The only release that in question is the 64-bit aarch64 Linux >>> distribution. There?s really >>>> no need for this property since there?s only 1 ABI that?s widely >>> used today on that >>>> architecture. >>>> >>>> Bob. >>>> >>> My comment was about the OpenJDK aarch32 builds. From your original >>> post, >>> I have the impression that the OpenJDK aarch32 builds don't set this >>> property. >>> If it could be added for the OpenJDK aarch32 builds, this would be >>> very useful >>> for my application. >>> I understand that this is not needed for aarch64 builds. >>> Simon >>>>> On Apr 3, 2017, at 12:53 PM, Simon Nash >> > wrote: >>>>> >>>>> Hi Bob, >>>>> I would find such a property very useful. >>>>> >>>>> My application is mostly written in Java but also uses a native >>> library >>>>> that is loaded dynamically by the Java code. In order to distribute >>>>> fewer versions of the application and make things simpler for users, >>>>> I have recently started packaging multiple versions of the >>> native library >>>>> (for example, Intel x86 and Intel x64) in a single version of the >>>>> application and using Java runtime properties to determine which of >>>>> these native libraries to load. >>>>> >>>>> I would like to do this for gnueabi and gnueabihf if I could find a >>>>> reliable way to determine at runtime which of these native libraries >>>>> is needed. It sounds like this property would be an ideal solution. >>>>> >>>>> Best regards, >>>>> Simon >>>>> >>>>> On 03/04/2017 16:57, Bob Vandette wrote: >>>>>> I?m inclined to not fix this bug but thought I?d bring it to >>> your attention just in case. >>>>>> I assume that OpenJDK ARM builds never set this property >>> anyway, right? >>>>>> https://bugs.openjdk.java.net/browse/JDK-8177976 >>> >>>>>> Bob. >>>> >>>> >> > From andrey.petushkov at gmail.com Wed Apr 5 14:50:21 2017 From: andrey.petushkov at gmail.com (Andrey Petushkov) Date: Wed, 5 Apr 2017 17:50:21 +0300 Subject: [aarch64-port-dev ] SUN_ARCH_ABI property not set or in release file for aarch64 builds In-Reply-To: <58E4FFB3.1050505@cjnash.com> References: <58E27DFF.6010007@cjnash.com> <52B351FD-BC1A-4B0D-8E4D-16CD72BCA0E3@oracle.com> <58E2AE03.1010309@cjnash.com> <58E2B73C.5010004@cjnash.com> <58E4FFB3.1050505@cjnash.com> Message-ID: <178965FE-E30F-46CE-A864-BC62F644B86A@gmail.com> > On 05 Apr 2017, at 17:31, Simon Nash wrote: > > On 05/04/2017 14:43, Andrey Petushkov wrote: >> Dear Simon, >> Sorry for the delay. I was trying to build the code so that it has the property, but apparently the necessary piece of magic is missing. The location for that piece is only present in the Oracle?s arm port repos, not anywhere else, including stock OpenJDK 8u and 9. I doubt we want to integrate it just because of this property. So we will think how to play around it.. > > Thanks for this information. This is turning out to be more difficult > than I expected. The instructions from Bob should not be hard to follow. Although I?m not quite sure the ?with-extra-cflags is the best implementation it should be good for you > >>> 03 Apr 2017, at 23:57, Simon Nash wrote: >>> >>> Hi Andrey, >>> I am using the OpenJDK sources in the aarch32-port repository to build >>> a JRE for my application, so it will help to have this property set by >>> this JRE. I will try my current binary to see whether this property >>> is already available. >> If you?re building from Oracle?s port I believe Bob should be able to tell how to bring the magic over. Otherwise please stay tuned, we?ll work on bringing it into the rest of aarch32 repos > > For JDK 8, I am building aarch32-port/jdk8u. For JDK 9, I was building > aarch32-port/arm-3264. Since this has been merged into jdk9/jdk9 I am > now building jdk9/jdk9 instead. > >>> I have sucessfully built the aarch32-port sources for gnueabihf but I >>> could not build them for gnueabi becaise there appear to be some missing >>> files in the aarch32-port sources that are neeeded for softfp support. >>> Is this correct? If so, are there any plans to support a softfp version? >> Could you please indicate what repos are you building from: 8u, 9 or 9-arm3264 (aka Oracle) > See above. I have got softfp working with 9-arm3264 but I wasn't able > to build 8u with softfp because of missing files. What files are you missing? Could you please elaborate a bit? One more question, is softfp is mandatory for you? The reason why I?m asking is that we?re regularly building 8u in soft-float configuration with VFP support in hotspot compiler. It should give almost the same performance as softfp. As what to softfp itself it might be broken, we?re not testing it Thanks, Andrey > > Simon > >> Thanks, >> Andrey >>> Best regards, >>> Simon >>> >>> On 03/04/2017 21:45, Andrey Petushkov wrote: >>>> Hi Simon, >>>> from the first glance it's set with the command line when the binary is built. so there is no code change is required but rather build system setup. we can ensure Azul is building with it so it will propagate into any downstream distribution taking our binaries. yet it might help you or might not depending on what you call the "openjdk build" >>>> Regards, >>>> Andrey >>>> On Mon, Apr 3, 2017, 23:18 Simon Nash > wrote: >>>> On 03/04/2017 17:58, Bob Vandette wrote: >>>> > The Oracle binaries for JDK 8 and JDK 9 Linux arm already include >>>> this property for the >>>> > 32-bit ARM binaries. >>>> > >>>> > The only release that in question is the 64-bit aarch64 Linux >>>> distribution. There?s really >>>> > no need for this property since there?s only 1 ABI that?s widely >>>> used today on that >>>> > architecture. >>>> > >>>> > Bob. >>>> > >>>> My comment was about the OpenJDK aarch32 builds. From your original >>>> post, >>>> I have the impression that the OpenJDK aarch32 builds don't set this >>>> property. >>>> If it could be added for the OpenJDK aarch32 builds, this would be >>>> very useful >>>> for my application. >>>> I understand that this is not needed for aarch64 builds. >>>> Simon >>>> >> On Apr 3, 2017, at 12:53 PM, Simon Nash >>> > wrote: >>>> >> >>>> >> Hi Bob, >>>> >> I would find such a property very useful. >>>> >> >>>> >> My application is mostly written in Java but also uses a native >>>> library >>>> >> that is loaded dynamically by the Java code. In order to distribute >>>> >> fewer versions of the application and make things simpler for users, >>>> >> I have recently started packaging multiple versions of the >>>> native library >>>> >> (for example, Intel x86 and Intel x64) in a single version of the >>>> >> application and using Java runtime properties to determine which of >>>> >> these native libraries to load. >>>> >> >>>> >> I would like to do this for gnueabi and gnueabihf if I could find a >>>> >> reliable way to determine at runtime which of these native libraries >>>> >> is needed. It sounds like this property would be an ideal solution. >>>> >> >>>> >> Best regards, >>>> >> Simon >>>> >> >>>> >> On 03/04/2017 16:57, Bob Vandette wrote: >>>> >>> I?m inclined to not fix this bug but thought I?d bring it to >>>> your attention just in case. >>>> >>> I assume that OpenJDK ARM builds never set this property >>>> anyway, right? >>>> >>> https://bugs.openjdk.java.net/browse/JDK-8177976 >>>> >>>> >>> Bob. >>>> > >>>> > > From ci_notify at linaro.org Wed Apr 5 15:26:41 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Wed, 5 Apr 2017 15:26:41 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <961140023.425.1491406002243.JavaMail.jenkins@ci.linaro.org> 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/2017/095/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2016/dec/01 pass: 668; fail: 44; error: 6 Build 1: aarch64/2016/dec/21 pass: 668; fail: 44; error: 6 Build 2: aarch64/2017/jan/18 pass: 672; fail: 44; error: 3 Build 3: aarch64/2017/feb/04 pass: 672; fail: 44; error: 3 Build 4: aarch64/2017/feb/24 pass: 672; fail: 44; error: 3 Build 5: aarch64/2017/mar/29 pass: 672; fail: 44; error: 3 Build 6: aarch64/2017/apr/05 pass: 672; fail: 44; error: 3 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2016/dec/21 pass: 5,621; fail: 219; error: 45 Build 1: aarch64/2017/jan/18 pass: 5,683; fail: 213; error: 36 Build 2: aarch64/2017/feb/04 pass: 5,667; fail: 234; error: 41 Build 3: aarch64/2017/feb/24 pass: 5,701; fail: 217; error: 27 Build 4: aarch64/2017/mar/29 pass: 5,686; fail: 225; error: 34 Build 5: aarch64/2017/apr/05 pass: 5,677; fail: 235; error: 33 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2016/dec/01 pass: 3,091; error: 16 Build 1: aarch64/2016/dec/21 pass: 3,096; error: 11 Build 2: aarch64/2017/jan/18 pass: 3,098; error: 13 Build 3: aarch64/2017/feb/04 pass: 3,094; error: 17 Build 4: aarch64/2017/feb/24 pass: 3,106; error: 6 Build 5: aarch64/2017/mar/29 pass: 3,105; fail: 2; error: 5 Build 6: aarch64/2017/apr/05 pass: 3,104; fail: 2; error: 6 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2016/nov/03 pass: 664; fail: 44; error: 6 Build 1: aarch64/2016/nov/08 pass: 664; fail: 44; error: 6 Build 2: aarch64/2016/nov/09 pass: 664; fail: 44; error: 6 Build 3: aarch64/2016/nov/21 pass: 668; fail: 44; error: 6 Build 4: aarch64/2016/dec/01 pass: 669; fail: 43; error: 6 Build 5: aarch64/2016/dec/21 pass: 668; fail: 44; error: 6 Build 6: aarch64/2017/jan/18 pass: 673; fail: 43; error: 3 Build 7: aarch64/2017/feb/04 pass: 673; fail: 43; error: 3 Build 8: aarch64/2017/feb/24 pass: 673; fail: 43; error: 3 Build 9: aarch64/2017/mar/29 pass: 673; fail: 43; error: 3 Build 10: aarch64/2017/apr/05 pass: 673; fail: 43; error: 3 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2016/dec/21 pass: 5,618; fail: 226; error: 41 Build 1: aarch64/2017/jan/18 pass: 5,690; fail: 206; error: 36 Build 2: aarch64/2017/feb/04 pass: 5,669; fail: 214; error: 59 Build 3: aarch64/2017/feb/24 pass: 5,701; fail: 221; error: 23 Build 4: aarch64/2017/mar/29 pass: 5,696; fail: 222; error: 27 Build 5: aarch64/2017/apr/05 pass: 5,692; fail: 229; error: 24 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2016/nov/03 pass: 3,092; error: 15 Build 1: aarch64/2016/nov/08 pass: 3,092; error: 15 Build 2: aarch64/2016/nov/09 pass: 3,091; error: 16 Build 3: aarch64/2016/nov/21 pass: 3,095; error: 12 Build 4: aarch64/2016/dec/01 pass: 3,095; error: 12 Build 5: aarch64/2016/dec/21 pass: 3,092; error: 15 Build 6: aarch64/2017/jan/18 pass: 3,102; error: 9 Build 7: aarch64/2017/feb/04 pass: 3,099; error: 12 Build 8: aarch64/2017/feb/24 pass: 3,109; error: 3 Build 9: aarch64/2017/mar/29 pass: 3,104; fail: 2; error: 6 Build 10: aarch64/2017/apr/05 pass: 3,105; fail: 2; error: 5 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): 0.96x Relative performance: Server critical-jOPS (nc): 0.85x 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 client and server compilers on 2014-04-01. Relative performance: Zero: 1.0, Client: 56.92, Server: 110.27 Client 56.92 / Client 2014-04-01 (43.00): 1.32x 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/jdk8u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2016-11-03 pass rate: 5140/5140, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2016/308/results/ 2016-11-21 pass rate: 5140/5140, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2016/326/results/ 2016-12-01 pass rate: 5140/5140, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2016/336/results/ 2016-12-22 pass rate: 5140/5140, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2016/356/results/ 2017-01-18 pass rate: 5140/5140, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2017/018/results/ 2017-02-06 pass rate: 5140/5140, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2017/035/results/ 2017-02-25 pass rate: 5176/5176, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2017/055/results/ 2017-03-29 pass rate: 8484/8485, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2017/088/results/ 2017-04-05 pass rate: 8484/8485, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2017/095/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From andrey.petushkov at gmail.com Thu Apr 6 12:25:57 2017 From: andrey.petushkov at gmail.com (Andrey Petushkov) Date: Thu, 6 Apr 2017 15:25:57 +0300 Subject: [aarch64-port-dev ] SUN_ARCH_ABI property not set or in release file for aarch64 builds In-Reply-To: <58E539EB.8080801@cjnash.com> References: <58E27DFF.6010007@cjnash.com> <52B351FD-BC1A-4B0D-8E4D-16CD72BCA0E3@oracle.com> <58E2AE03.1010309@cjnash.com> <58E2B73C.5010004@cjnash.com> <58E4FFB3.1050505@cjnash.com> <178965FE-E30F-46CE-A864-BC62F644B86A@gmail.com> <58E539EB.8080801@cjnash.com> Message-ID: > On 05 Apr 2017, at 21:39, Simon Nash wrote: > > On 05/04/2017 15:50, Andrey Petushkov wrote: >>> On 05 Apr 2017, at 17:31, Simon Nash > wrote: >>> >>> On 05/04/2017 14:43, Andrey Petushkov wrote: >>>> Dear Simon, >>>> Sorry for the delay. I was trying to build the code so that it has the property, but apparently the necessary piece of magic is missing. The location for that piece is only present in the Oracle?s arm port repos, not anywhere else, including stock OpenJDK 8u and 9. I doubt we want to integrate it just because of this property. So we will think how to play around it.. >>> Thanks for this information. This is turning out to be more difficult >>> than I expected. >> The instructions from Bob should not be hard to follow. Although I?m not quite sure the ?with-extra-cflags is the best implementation it should be good for you > > Are you suggesting that I should create and test a patch for 8u based on > Bob's instructions and submit it for merging into the 8u codebase? No, not in any way. And indeed, Bob?s instructions for 8u cannot make any patch since they are for the entity which runs configure script. Which is user. Which is not a part of the repos :) > >>>>> 03 Apr 2017, at 23:57, Simon Nash wrote: >>>>> >>>>> Hi Andrey, >>>>> I am using the OpenJDK sources in the aarch32-port repository to build >>>>> a JRE for my application, so it will help to have this property set by >>>>> this JRE. I will try my current binary to see whether this property >>>>> is already available. >>>> If you?re building from Oracle?s port I believe Bob should be able to tell how to bring the magic over. Otherwise please stay tuned, we?ll work on bringing it into the rest of aarch32 repos >>> For JDK 8, I am building aarch32-port/jdk8u. For JDK 9, I was building >>> aarch32-port/arm-3264. Since this has been merged into jdk9/jdk9 I am >>> now building jdk9/jdk9 instead. >>> >>>>> I have sucessfully built the aarch32-port sources for gnueabihf but I >>>>> could not build them for gnueabi becaise there appear to be some missing >>>>> files in the aarch32-port sources that are neeeded for softfp support. >>>>> Is this correct? If so, are there any plans to support a softfp version? >>>> Could you please indicate what repos are you building from: 8u, 9 or 9-arm3264 (aka Oracle) >>> See above. I have got softfp working with 9-arm3264 but I wasn't able >>> to build 8u with softfp because of missing files. >> What files are you missing? Could you please elaborate a bit? > > I will go back and recheck on the details and post here when I have them. > >> One more question, is softfp is mandatory for you? The reason why I?m asking is that we?re regularly building 8u in soft-float configuration with VFP support in hotspot compiler. It should give almost the same performance as softfp. As what to softfp itself it might be broken, we?re not testing it > > I would like to run 8u on ARMv5 machines that only support gnueabi and > don't have hardware floating-point support. I have built a JDK9 runtime > for this from the 9-arm3264 sources and I have verified that it works. A-ha, then the problem should be not in VP but rather in ARMv5. Sorry to say but aarch32-8u codebase does not support any ARM core lower than v6k. (Although it should be pretty easy to make interpreter work on v5 and even below) Andrey > > Simon > >> Thanks, >> Andrey >>> Simon >>> >>>> Thanks, >>>> Andrey >>>>> Best regards, >>>>> Simon >>>>> >>>>> On 03/04/2017 21:45, Andrey Petushkov wrote: >>>>>> Hi Simon, >>>>>> from the first glance it's set with the command line when the binary is built. so there is no code change is required but rather build system setup. we can ensure Azul is building with it so it will propagate into any downstream distribution taking our binaries. yet it might help you or might not depending on what you call the "openjdk build" >>>>>> Regards, >>>>>> Andrey >>>>>> On Mon, Apr 3, 2017, 23:18 Simon Nash > wrote: >>>>>> On 03/04/2017 17:58, Bob Vandette wrote: >>>>>> > The Oracle binaries for JDK 8 and JDK 9 Linux arm already include >>>>>> this property for the >>>>>> > 32-bit ARM binaries. >>>>>> > >>>>>> > The only release that in question is the 64-bit aarch64 Linux >>>>>> distribution. There?s really >>>>>> > no need for this property since there?s only 1 ABI that?s widely >>>>>> used today on that >>>>>> > architecture. >>>>>> > >>>>>> > Bob. >>>>>> > >>>>>> My comment was about the OpenJDK aarch32 builds. From your original >>>>>> post, >>>>>> I have the impression that the OpenJDK aarch32 builds don't set this >>>>>> property. >>>>>> If it could be added for the OpenJDK aarch32 builds, this would be >>>>>> very useful >>>>>> for my application. >>>>>> I understand that this is not needed for aarch64 builds. >>>>>> Simon >>>>>> >> On Apr 3, 2017, at 12:53 PM, Simon Nash >>>>> > wrote: >>>>>> >> >>>>>> >> Hi Bob, >>>>>> >> I would find such a property very useful. >>>>>> >> >>>>>> >> My application is mostly written in Java but also uses a native >>>>>> library >>>>>> >> that is loaded dynamically by the Java code. In order to distribute >>>>>> >> fewer versions of the application and make things simpler for users, >>>>>> >> I have recently started packaging multiple versions of the >>>>>> native library >>>>>> >> (for example, Intel x86 and Intel x64) in a single version of the >>>>>> >> application and using Java runtime properties to determine which of >>>>>> >> these native libraries to load. >>>>>> >> >>>>>> >> I would like to do this for gnueabi and gnueabihf if I could find a >>>>>> >> reliable way to determine at runtime which of these native libraries >>>>>> >> is needed. It sounds like this property would be an ideal solution. >>>>>> >> >>>>>> >> Best regards, >>>>>> >> Simon >>>>>> >> >>>>>> >> On 03/04/2017 16:57, Bob Vandette wrote: >>>>>> >>> I?m inclined to not fix this bug but thought I?d bring it to >>>>>> your attention just in case. >>>>>> >>> I assume that OpenJDK ARM builds never set this property >>>>>> anyway, right? >>>>>> >>> https://bugs.openjdk.java.net/browse/JDK-8177976 >>>>>> >>>>>> >>> Bob. >>>>>> > >>>>>> > From andrey.petushkov at gmail.com Fri Apr 7 12:54:44 2017 From: andrey.petushkov at gmail.com (Andrey Petushkov) Date: Fri, 7 Apr 2017 15:54:44 +0300 Subject: [aarch64-port-dev ] [aarch32-8u] RFR: 8178318: SUN_ARCH_ABI property not set or in release file for aarch32 builds In-Reply-To: <58E666BF.50900@cjnash.com> References: <58E27DFF.6010007@cjnash.com> <52B351FD-BC1A-4B0D-8E4D-16CD72BCA0E3@oracle.com> <58E2AE03.1010309@cjnash.com> <58E2B73C.5010004@cjnash.com> <58E4FFB3.1050505@cjnash.com> <178965FE-E30F-46CE-A864-BC62F644B86A@gmail.com> <58E539EB.8080801@cjnash.com> <58E666BF.50900@cjnash.com> Message-ID: <1D54B81D-481E-4CB9-B2A1-F666C8B3FC90@gmail.com> Dear All, I?ve made relevant changes into our internal repos to account for this property. If you?d like I?ve prepared a webrev for integration of those into aarch32-8u repos. the root of the forest http://cr.openjdk.java.net/~apetushkov/8178318/webrev/ the jdk repo http://cr.openjdk.java.net/~apetushkov/8178318/jdk/webrev/ I see no point in integration the whole Oracle?s files.m4 machinery. At the same time requirement to pass the value with ?with-extra-flags seem to be too loose to ensure the mechanism continues to function in time. So I?ve created a (mandatory) ?with-abi-name parameter to configure script Regards, Andrey > On 06 Apr 2017, at 19:03, Simon Nash wrote: > > On 06/04/2017 13:25, Andrey Petushkov wrote: >>> On 05 Apr 2017, at 21:39, Simon Nash > wrote: >>> >>> On 05/04/2017 15:50, Andrey Petushkov wrote: >>>>> On 05 Apr 2017, at 17:31, Simon Nash > wrote: >>>>> >>>>> On 05/04/2017 14:43, Andrey Petushkov wrote: >>>>>> Dear Simon, >>>>>> Sorry for the delay. I was trying to build the code so that it has the property, but apparently the necessary piece of magic is missing. The location for that piece is only present in the Oracle?s arm port repos, not anywhere else, including stock OpenJDK 8u and 9. I doubt we want to integrate it just because of this property. So we will think how to play around it.. >>>>> Thanks for this information. This is turning out to be more difficult >>>>> than I expected. >>>> The instructions from Bob should not be hard to follow. Although I?m not quite sure the ?with-extra-cflags is the best implementation it should be good for you >>> >>> Are you suggesting that I should create and test a patch for 8u based on >>> Bob's instructions and submit it for merging into the 8u codebase? >> No, not in any way. And indeed, Bob?s instructions for 8u cannot make any patch since they are for the entity which runs configure script. Which is user. Which is not a part of the repos :) > > Thanks, I see now that the #ifdefs that Bob mentioned are present in the > jdk8u sources but in different files. I will give this a try. > >>> >>>>>>> 03 Apr 2017, at 23:57, Simon Nash > wrote: >>>>>>> >>>>>>> Hi Andrey, >>>>>>> I am using the OpenJDK sources in the aarch32-port repository to build >>>>>>> a JRE for my application, so it will help to have this property set by >>>>>>> this JRE. I will try my current binary to see whether this property >>>>>>> is already available. >>>>>> If you?re building from Oracle?s port I believe Bob should be able to tell how to bring the magic over. Otherwise please stay tuned, we?ll work on bringing it into the rest of aarch32 repos >>>>> For JDK 8, I am building aarch32-port/jdk8u. For JDK 9, I was building >>>>> aarch32-port/arm-3264. Since this has been merged into jdk9/jdk9 I am >>>>> now building jdk9/jdk9 instead. >>>>> >>>>>>> I have sucessfully built the aarch32-port sources for gnueabihf but I >>>>>>> could not build them for gnueabi becaise there appear to be some missing >>>>>>> files in the aarch32-port sources that are neeeded for softfp support. >>>>>>> Is this correct? If so, are there any plans to support a softfp version? >>>>>> Could you please indicate what repos are you building from: 8u, 9 or 9-arm3264 (aka Oracle) >>>>> See above. I have got softfp working with 9-arm3264 but I wasn't able >>>>> to build 8u with softfp because of missing files. >>>> What files are you missing? Could you please elaborate a bit? >>> >>> I will go back and recheck on the details and post here when I have them. >>> >>>> One more question, is softfp is mandatory for you? The reason why I?m asking is that we?re regularly building 8u in soft-float configuration with VFP support in hotspot compiler. It should give almost the same performance as softfp. As what to softfp itself it might be broken, we?re not testing it >>> >>> I would like to run 8u on ARMv5 machines that only support gnueabi and >>> don't have hardware floating-point support. I have built a JDK9 runtime >>> for this from the 9-arm3264 sources and I have verified that it works. >> A-ha, then the problem should be not in VP but rather in ARMv5. Sorry to say but aarch32-8u codebase does not support any ARM core lower than v6k. (Although it should be pretty easy to make interpreter work on v5 and even below) > > Thanks for the clarification. > > Simon > >> Andrey >>> >>> Simon >>> >>>> Thanks, >>>> Andrey >>>>> Simon >>>>> >>>>>> Thanks, >>>>>> Andrey >>>>>>> Best regards, >>>>>>> Simon >>>>>>> >>>>>>> On 03/04/2017 21:45, Andrey Petushkov wrote: >>>>>>>> Hi Simon, >>>>>>>> from the first glance it's set with the command line when the binary is built. so there is no code change is required but rather build system setup. we can ensure Azul is building with it so it will propagate into any downstream distribution taking our binaries. yet it might help you or might not depending on what you call the "openjdk build" >>>>>>>> Regards, >>>>>>>> Andrey >>>>>>>> On Mon, Apr 3, 2017, 23:18 Simon Nash > wrote: >>>>>>>> On 03/04/2017 17:58, Bob Vandette wrote: >>>>>>>> > The Oracle binaries for JDK 8 and JDK 9 Linux arm already include >>>>>>>> this property for the >>>>>>>> > 32-bit ARM binaries. >>>>>>>> > >>>>>>>> > The only release that in question is the 64-bit aarch64 Linux >>>>>>>> distribution. There?s really >>>>>>>> > no need for this property since there?s only 1 ABI that?s widely >>>>>>>> used today on that >>>>>>>> > architecture. >>>>>>>> > >>>>>>>> > Bob. >>>>>>>> > >>>>>>>> My comment was about the OpenJDK aarch32 builds. From your original >>>>>>>> post, >>>>>>>> I have the impression that the OpenJDK aarch32 builds don't set this >>>>>>>> property. >>>>>>>> If it could be added for the OpenJDK aarch32 builds, this would be >>>>>>>> very useful >>>>>>>> for my application. >>>>>>>> I understand that this is not needed for aarch64 builds. >>>>>>>> Simon >>>>>>>> >> On Apr 3, 2017, at 12:53 PM, Simon Nash >>>>>>>> > wrote: >>>>>>>> >> >>>>>>>> >> Hi Bob, >>>>>>>> >> I would find such a property very useful. >>>>>>>> >> >>>>>>>> >> My application is mostly written in Java but also uses a native >>>>>>>> library >>>>>>>> >> that is loaded dynamically by the Java code. In order to distribute >>>>>>>> >> fewer versions of the application and make things simpler for users, >>>>>>>> >> I have recently started packaging multiple versions of the >>>>>>>> native library >>>>>>>> >> (for example, Intel x86 and Intel x64) in a single version of the >>>>>>>> >> application and using Java runtime properties to determine which of >>>>>>>> >> these native libraries to load. >>>>>>>> >> >>>>>>>> >> I would like to do this for gnueabi and gnueabihf if I could find a >>>>>>>> >> reliable way to determine at runtime which of these native libraries >>>>>>>> >> is needed. It sounds like this property would be an ideal solution. >>>>>>>> >> >>>>>>>> >> Best regards, >>>>>>>> >> Simon >>>>>>>> >> >>>>>>>> >> On 03/04/2017 16:57, Bob Vandette wrote: >>>>>>>> >>> I?m inclined to not fix this bug but thought I?d bring it to >>>>>>>> your attention just in case. >>>>>>>> >>> I assume that OpenJDK ARM builds never set this property >>>>>>>> anyway, right? >>>>>>>> >>> https://bugs.openjdk.java.net/browse/JDK-8177976 >>>>>>>> >>>>>>>> >>> Bob. >>>>>>>> > >>>>>>>> > > From bob.vandette at oracle.com Fri Apr 7 13:25:25 2017 From: bob.vandette at oracle.com (Bob Vandette) Date: Fri, 7 Apr 2017 09:25:25 -0400 Subject: [aarch64-port-dev ] [aarch32-8u] RFR: 8178318: SUN_ARCH_ABI property not set or in release file for aarch32 builds In-Reply-To: <1D54B81D-481E-4CB9-B2A1-F666C8B3FC90@gmail.com> References: <58E27DFF.6010007@cjnash.com> <52B351FD-BC1A-4B0D-8E4D-16CD72BCA0E3@oracle.com> <58E2AE03.1010309@cjnash.com> <58E2B73C.5010004@cjnash.com> <58E4FFB3.1050505@cjnash.com> <178965FE-E30F-46CE-A864-BC62F644B86A@gmail.com> <58E539EB.8080801@cjnash.com> <58E666BF.50900@cjnash.com> <1D54B81D-481E-4CB9-B2A1-F666C8B3FC90@gmail.com> Message-ID: Andrey, I haven?t looked at any of your other files related to compiler flags for ARM but I don?t think you should add a new configure option when one already exists in JDK 9. The ABI name is very much dependent on the compiler flags used to build the native binaries. Simply specifying the abi name can cause incorrect builds to be produced. I suggest that you use ?with-abi-profile so that when you transition to JDK9, you won?t have to revisit this issue. Bob. > On Apr 7, 2017, at 8:54 AM, Andrey Petushkov wrote: > > Dear All, > > I?ve made relevant changes into our internal repos to account for this property. If you?d like I?ve prepared a webrev for integration of those into aarch32-8u repos. > the root of the forest http://cr.openjdk.java.net/~apetushkov/8178318/webrev/ > the jdk repo http://cr.openjdk.java.net/~apetushkov/8178318/jdk/webrev/ > > I see no point in integration the whole Oracle?s files.m4 machinery. At the same time requirement to pass the value with ?with-extra-flags seem to be too loose to ensure the mechanism continues to function in time. So I?ve created a (mandatory) ?with-abi-name parameter to configure script > > Regards, > Andrey > >> On 06 Apr 2017, at 19:03, Simon Nash > wrote: >> >> On 06/04/2017 13:25, Andrey Petushkov wrote: >>>> On 05 Apr 2017, at 21:39, Simon Nash >> wrote: >>>> >>>> On 05/04/2017 15:50, Andrey Petushkov wrote: >>>>>> On 05 Apr 2017, at 17:31, Simon Nash >> wrote: >>>>>> >>>>>> On 05/04/2017 14:43, Andrey Petushkov wrote: >>>>>>> Dear Simon, >>>>>>> Sorry for the delay. I was trying to build the code so that it has the property, but apparently the necessary piece of magic is missing. The location for that piece is only present in the Oracle?s arm port repos, not anywhere else, including stock OpenJDK 8u and 9. I doubt we want to integrate it just because of this property. So we will think how to play around it.. >>>>>> Thanks for this information. This is turning out to be more difficult >>>>>> than I expected. >>>>> The instructions from Bob should not be hard to follow. Although I?m not quite sure the ?with-extra-cflags is the best implementation it should be good for you >>>> >>>> Are you suggesting that I should create and test a patch for 8u based on >>>> Bob's instructions and submit it for merging into the 8u codebase? >>> No, not in any way. And indeed, Bob?s instructions for 8u cannot make any patch since they are for the entity which runs configure script. Which is user. Which is not a part of the repos :) >> >> Thanks, I see now that the #ifdefs that Bob mentioned are present in the >> jdk8u sources but in different files. I will give this a try. >> >>>> >>>>>>>> 03 Apr 2017, at 23:57, Simon Nash >> wrote: >>>>>>>> >>>>>>>> Hi Andrey, >>>>>>>> I am using the OpenJDK sources in the aarch32-port repository to build >>>>>>>> a JRE for my application, so it will help to have this property set by >>>>>>>> this JRE. I will try my current binary to see whether this property >>>>>>>> is already available. >>>>>>> If you?re building from Oracle?s port I believe Bob should be able to tell how to bring the magic over. Otherwise please stay tuned, we?ll work on bringing it into the rest of aarch32 repos >>>>>> For JDK 8, I am building aarch32-port/jdk8u. For JDK 9, I was building >>>>>> aarch32-port/arm-3264. Since this has been merged into jdk9/jdk9 I am >>>>>> now building jdk9/jdk9 instead. >>>>>> >>>>>>>> I have sucessfully built the aarch32-port sources for gnueabihf but I >>>>>>>> could not build them for gnueabi becaise there appear to be some missing >>>>>>>> files in the aarch32-port sources that are neeeded for softfp support. >>>>>>>> Is this correct? If so, are there any plans to support a softfp version? >>>>>>> Could you please indicate what repos are you building from: 8u, 9 or 9-arm3264 (aka Oracle) >>>>>> See above. I have got softfp working with 9-arm3264 but I wasn't able >>>>>> to build 8u with softfp because of missing files. >>>>> What files are you missing? Could you please elaborate a bit? >>>> >>>> I will go back and recheck on the details and post here when I have them. >>>> >>>>> One more question, is softfp is mandatory for you? The reason why I?m asking is that we?re regularly building 8u in soft-float configuration with VFP support in hotspot compiler. It should give almost the same performance as softfp. As what to softfp itself it might be broken, we?re not testing it >>>> >>>> I would like to run 8u on ARMv5 machines that only support gnueabi and >>>> don't have hardware floating-point support. I have built a JDK9 runtime >>>> for this from the 9-arm3264 sources and I have verified that it works. >>> A-ha, then the problem should be not in VP but rather in ARMv5. Sorry to say but aarch32-8u codebase does not support any ARM core lower than v6k. (Although it should be pretty easy to make interpreter work on v5 and even below) >> >> Thanks for the clarification. >> >> Simon >> >>> Andrey >>>> >>>> Simon >>>> >>>>> Thanks, >>>>> Andrey >>>>>> Simon >>>>>> >>>>>>> Thanks, >>>>>>> Andrey >>>>>>>> Best regards, >>>>>>>> Simon >>>>>>>> >>>>>>>> On 03/04/2017 21:45, Andrey Petushkov wrote: >>>>>>>>> Hi Simon, >>>>>>>>> from the first glance it's set with the command line when the binary is built. so there is no code change is required but rather build system setup. we can ensure Azul is building with it so it will propagate into any downstream distribution taking our binaries. yet it might help you or might not depending on what you call the "openjdk build" >>>>>>>>> Regards, >>>>>>>>> Andrey >>>>>>>>> On Mon, Apr 3, 2017, 23:18 Simon Nash > >> wrote: >>>>>>>>> On 03/04/2017 17:58, Bob Vandette wrote: >>>>>>>>> > The Oracle binaries for JDK 8 and JDK 9 Linux arm already include >>>>>>>>> this property for the >>>>>>>>> > 32-bit ARM binaries. >>>>>>>>> > >>>>>>>>> > The only release that in question is the 64-bit aarch64 Linux >>>>>>>>> distribution. There?s really >>>>>>>>> > no need for this property since there?s only 1 ABI that?s widely >>>>>>>>> used today on that >>>>>>>>> > architecture. >>>>>>>>> > >>>>>>>>> > Bob. >>>>>>>>> > >>>>>>>>> My comment was about the OpenJDK aarch32 builds. From your original >>>>>>>>> post, >>>>>>>>> I have the impression that the OpenJDK aarch32 builds don't set this >>>>>>>>> property. >>>>>>>>> If it could be added for the OpenJDK aarch32 builds, this would be >>>>>>>>> very useful >>>>>>>>> for my application. >>>>>>>>> I understand that this is not needed for aarch64 builds. >>>>>>>>> Simon >>>>>>>>> >> On Apr 3, 2017, at 12:53 PM, Simon Nash > >>>>>>>>> >> wrote: >>>>>>>>> >> >>>>>>>>> >> Hi Bob, >>>>>>>>> >> I would find such a property very useful. >>>>>>>>> >> >>>>>>>>> >> My application is mostly written in Java but also uses a native >>>>>>>>> library >>>>>>>>> >> that is loaded dynamically by the Java code. In order to distribute >>>>>>>>> >> fewer versions of the application and make things simpler for users, >>>>>>>>> >> I have recently started packaging multiple versions of the >>>>>>>>> native library >>>>>>>>> >> (for example, Intel x86 and Intel x64) in a single version of the >>>>>>>>> >> application and using Java runtime properties to determine which of >>>>>>>>> >> these native libraries to load. >>>>>>>>> >> >>>>>>>>> >> I would like to do this for gnueabi and gnueabihf if I could find a >>>>>>>>> >> reliable way to determine at runtime which of these native libraries >>>>>>>>> >> is needed. It sounds like this property would be an ideal solution. >>>>>>>>> >> >>>>>>>>> >> Best regards, >>>>>>>>> >> Simon >>>>>>>>> >> >>>>>>>>> >> On 03/04/2017 16:57, Bob Vandette wrote: >>>>>>>>> >>> I?m inclined to not fix this bug but thought I?d bring it to >>>>>>>>> your attention just in case. >>>>>>>>> >>> I assume that OpenJDK ARM builds never set this property >>>>>>>>> anyway, right? >>>>>>>>> >>> https://bugs.openjdk.java.net/browse/JDK-8177976 >>>>>>>>> > >>>>>>>>> >>> Bob. >>>>>>>>> > >>>>>>>>> > >> > From aph at redhat.com Fri Apr 7 17:03:49 2017 From: aph at redhat.com (Andrew Haley) Date: Fri, 7 Apr 2017 18:03:49 +0100 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: Message-ID: <719cae05-efc8-0550-e999-9b5b113c0662@redhat.com> On 30/03/17 02:43, Zhongwei Yao wrote: > And from the data, aarch64 OpenJDK is better than arm64 OpenJDK > generally, but with some exceptions. So we think it is worth to take a look > at following cases for aarch64 OpenJDK: > - Dacapo's sunflow, tradebeans and xalan > - SPECjvm2008's scimark.lu.large > > And we also find arm64 is better than aarch64 for byte/short data type > vectorization in our JMH cases ([2]), which we are investigating. > > Feedbacks are welcome. Thanks! Thanks for doing this. It would help a great deal if you could share with us how you ran these tests. For example, I get exceptions if I try to run tradebeans from dacapo-9.12-bach.jar. Andrew. From andrey.petushkov at gmail.com Fri Apr 7 17:09:04 2017 From: andrey.petushkov at gmail.com (Andrey Petushkov) Date: Fri, 7 Apr 2017 20:09:04 +0300 Subject: [aarch64-port-dev ] [aarch32-8u] RFR: 8178318: SUN_ARCH_ABI property not set or in release file for aarch32 builds In-Reply-To: References: <58E27DFF.6010007@cjnash.com> <52B351FD-BC1A-4B0D-8E4D-16CD72BCA0E3@oracle.com> <58E2AE03.1010309@cjnash.com> <58E2B73C.5010004@cjnash.com> <58E4FFB3.1050505@cjnash.com> <178965FE-E30F-46CE-A864-BC62F644B86A@gmail.com> <58E539EB.8080801@cjnash.com> <58E666BF.50900@cjnash.com> <1D54B81D-481E-4CB9-B2A1-F666C8B3FC90@gmail.com> Message-ID: Hi Bob, Oh, yeah, I see. It?s just quite a lot of make code to verify and integrate.. Although for good, no question Andrey > On 07 Apr 2017, at 16:25, Bob Vandette wrote: > > Andrey, > > I haven?t looked at any of your other files related to compiler flags for ARM but I don?t > think you should add a new configure option when one already exists in JDK 9. > > The ABI name is very much dependent on the compiler flags used to build the native binaries. > Simply specifying the abi name can cause incorrect builds to be produced. > > I suggest that you use ?with-abi-profile so that when you transition to JDK9, you won?t have > to revisit this issue. > > Bob. > > >> On Apr 7, 2017, at 8:54 AM, Andrey Petushkov > wrote: >> >> Dear All, >> >> I?ve made relevant changes into our internal repos to account for this property. If you?d like I?ve prepared a webrev for integration of those into aarch32-8u repos. >> the root of the forest http://cr.openjdk.java.net/~apetushkov/8178318/webrev/ >> the jdk repo http://cr.openjdk.java.net/~apetushkov/8178318/jdk/webrev/ >> >> I see no point in integration the whole Oracle?s files.m4 machinery. At the same time requirement to pass the value with ?with-extra-flags seem to be too loose to ensure the mechanism continues to function in time. So I?ve created a (mandatory) ?with-abi-name parameter to configure script >> >> Regards, >> Andrey >> >>> On 06 Apr 2017, at 19:03, Simon Nash > wrote: >>> >>> On 06/04/2017 13:25, Andrey Petushkov wrote: >>>>> On 05 Apr 2017, at 21:39, Simon Nash >> wrote: >>>>> >>>>> On 05/04/2017 15:50, Andrey Petushkov wrote: >>>>>>> On 05 Apr 2017, at 17:31, Simon Nash >> wrote: >>>>>>> >>>>>>> On 05/04/2017 14:43, Andrey Petushkov wrote: >>>>>>>> Dear Simon, >>>>>>>> Sorry for the delay. I was trying to build the code so that it has the property, but apparently the necessary piece of magic is missing. The location for that piece is only present in the Oracle?s arm port repos, not anywhere else, including stock OpenJDK 8u and 9. I doubt we want to integrate it just because of this property. So we will think how to play around it.. >>>>>>> Thanks for this information. This is turning out to be more difficult >>>>>>> than I expected. >>>>>> The instructions from Bob should not be hard to follow. Although I?m not quite sure the ?with-extra-cflags is the best implementation it should be good for you >>>>> >>>>> Are you suggesting that I should create and test a patch for 8u based on >>>>> Bob's instructions and submit it for merging into the 8u codebase? >>>> No, not in any way. And indeed, Bob?s instructions for 8u cannot make any patch since they are for the entity which runs configure script. Which is user. Which is not a part of the repos :) >>> >>> Thanks, I see now that the #ifdefs that Bob mentioned are present in the >>> jdk8u sources but in different files. I will give this a try. >>> >>>>> >>>>>>>>> 03 Apr 2017, at 23:57, Simon Nash >> wrote: >>>>>>>>> >>>>>>>>> Hi Andrey, >>>>>>>>> I am using the OpenJDK sources in the aarch32-port repository to build >>>>>>>>> a JRE for my application, so it will help to have this property set by >>>>>>>>> this JRE. I will try my current binary to see whether this property >>>>>>>>> is already available. >>>>>>>> If you?re building from Oracle?s port I believe Bob should be able to tell how to bring the magic over. Otherwise please stay tuned, we?ll work on bringing it into the rest of aarch32 repos >>>>>>> For JDK 8, I am building aarch32-port/jdk8u. For JDK 9, I was building >>>>>>> aarch32-port/arm-3264. Since this has been merged into jdk9/jdk9 I am >>>>>>> now building jdk9/jdk9 instead. >>>>>>> >>>>>>>>> I have sucessfully built the aarch32-port sources for gnueabihf but I >>>>>>>>> could not build them for gnueabi becaise there appear to be some missing >>>>>>>>> files in the aarch32-port sources that are neeeded for softfp support. >>>>>>>>> Is this correct? If so, are there any plans to support a softfp version? >>>>>>>> Could you please indicate what repos are you building from: 8u, 9 or 9-arm3264 (aka Oracle) >>>>>>> See above. I have got softfp working with 9-arm3264 but I wasn't able >>>>>>> to build 8u with softfp because of missing files. >>>>>> What files are you missing? Could you please elaborate a bit? >>>>> >>>>> I will go back and recheck on the details and post here when I have them. >>>>> >>>>>> One more question, is softfp is mandatory for you? The reason why I?m asking is that we?re regularly building 8u in soft-float configuration with VFP support in hotspot compiler. It should give almost the same performance as softfp. As what to softfp itself it might be broken, we?re not testing it >>>>> >>>>> I would like to run 8u on ARMv5 machines that only support gnueabi and >>>>> don't have hardware floating-point support. I have built a JDK9 runtime >>>>> for this from the 9-arm3264 sources and I have verified that it works. >>>> A-ha, then the problem should be not in VP but rather in ARMv5. Sorry to say but aarch32-8u codebase does not support any ARM core lower than v6k. (Although it should be pretty easy to make interpreter work on v5 and even below) >>> >>> Thanks for the clarification. >>> >>> Simon >>> >>>> Andrey >>>>> >>>>> Simon >>>>> >>>>>> Thanks, >>>>>> Andrey >>>>>>> Simon >>>>>>> >>>>>>>> Thanks, >>>>>>>> Andrey >>>>>>>>> Best regards, >>>>>>>>> Simon >>>>>>>>> >>>>>>>>> On 03/04/2017 21:45, Andrey Petushkov wrote: >>>>>>>>>> Hi Simon, >>>>>>>>>> from the first glance it's set with the command line when the binary is built. so there is no code change is required but rather build system setup. we can ensure Azul is building with it so it will propagate into any downstream distribution taking our binaries. yet it might help you or might not depending on what you call the "openjdk build" >>>>>>>>>> Regards, >>>>>>>>>> Andrey >>>>>>>>>> On Mon, Apr 3, 2017, 23:18 Simon Nash > >> wrote: >>>>>>>>>> On 03/04/2017 17:58, Bob Vandette wrote: >>>>>>>>>> > The Oracle binaries for JDK 8 and JDK 9 Linux arm already include >>>>>>>>>> this property for the >>>>>>>>>> > 32-bit ARM binaries. >>>>>>>>>> > >>>>>>>>>> > The only release that in question is the 64-bit aarch64 Linux >>>>>>>>>> distribution. There?s really >>>>>>>>>> > no need for this property since there?s only 1 ABI that?s widely >>>>>>>>>> used today on that >>>>>>>>>> > architecture. >>>>>>>>>> > >>>>>>>>>> > Bob. >>>>>>>>>> > >>>>>>>>>> My comment was about the OpenJDK aarch32 builds. From your original >>>>>>>>>> post, >>>>>>>>>> I have the impression that the OpenJDK aarch32 builds don't set this >>>>>>>>>> property. >>>>>>>>>> If it could be added for the OpenJDK aarch32 builds, this would be >>>>>>>>>> very useful >>>>>>>>>> for my application. >>>>>>>>>> I understand that this is not needed for aarch64 builds. >>>>>>>>>> Simon >>>>>>>>>> >> On Apr 3, 2017, at 12:53 PM, Simon Nash > >>>>>>>>>> >> wrote: >>>>>>>>>> >> >>>>>>>>>> >> Hi Bob, >>>>>>>>>> >> I would find such a property very useful. >>>>>>>>>> >> >>>>>>>>>> >> My application is mostly written in Java but also uses a native >>>>>>>>>> library >>>>>>>>>> >> that is loaded dynamically by the Java code. In order to distribute >>>>>>>>>> >> fewer versions of the application and make things simpler for users, >>>>>>>>>> >> I have recently started packaging multiple versions of the >>>>>>>>>> native library >>>>>>>>>> >> (for example, Intel x86 and Intel x64) in a single version of the >>>>>>>>>> >> application and using Java runtime properties to determine which of >>>>>>>>>> >> these native libraries to load. >>>>>>>>>> >> >>>>>>>>>> >> I would like to do this for gnueabi and gnueabihf if I could find a >>>>>>>>>> >> reliable way to determine at runtime which of these native libraries >>>>>>>>>> >> is needed. It sounds like this property would be an ideal solution. >>>>>>>>>> >> >>>>>>>>>> >> Best regards, >>>>>>>>>> >> Simon >>>>>>>>>> >> >>>>>>>>>> >> On 03/04/2017 16:57, Bob Vandette wrote: >>>>>>>>>> >>> I?m inclined to not fix this bug but thought I?d bring it to >>>>>>>>>> your attention just in case. >>>>>>>>>> >>> I assume that OpenJDK ARM builds never set this property >>>>>>>>>> anyway, right? >>>>>>>>>> >>> https://bugs.openjdk.java.net/browse/JDK-8177976 >>>>>>>>>> > >>>>>>>>>> >>> Bob. >>>>>>>>>> > >>>>>>>>>> > >>> >> > From bob.vandette at oracle.com Fri Apr 7 19:37:31 2017 From: bob.vandette at oracle.com (Bob Vandette) Date: Fri, 7 Apr 2017 15:37:31 -0400 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: Message-ID: <1EC3C311-D6E0-427C-A21B-2161F49717BC@oracle.com> Zongwei, Thanks for running these benchmarks. Have you had the chance to try any server workload type of benchmarks? Just wondering if you had any results running things like specJBB or Hadoop TeraSort. Bob. > On Mar 29, 2017, at 9:43 PM, Zhongwei Yao wrote: > > Hi, > We have been running some Java benchmarks on AArch64 servers with different > OpenJDK ports: aarch64 and arm64. You can find the results at [1]. > And our JDK version: > - aarch64 OpenJDK: build from latest JDK9 source with config: > "--with-jvm-variants=server --with-debug-level=release" > > - arm64 OpenJDK: build from latest JDK9 source with config: > "--with-jvm-variants=server --with-debug-level=release --wi > th-cpu-port=arm64" > > And from the data, aarch64 OpenJDK is better than arm64 OpenJDK > generally, but with some exceptions. So we think it is worth to take a look > at following cases for aarch64 OpenJDK: > - Dacapo's sunflow, tradebeans and xalan > - SPECjvm2008's scimark.lu.large > > And we also find arm64 is better than aarch64 for byte/short data type > vectorization in our JMH cases ([2]), which we are investigating. > > Feedbacks are welcome. Thanks! > > [1]: > https://docs.google.com/spreadsheets/d/18iklOrbaL67i46XHsPTrdTObWqUJJK8EO4-k0eqdLKM/edit?usp=sharing > [2]: https://git.linaro.org/leg/openjdk/jmh-linaro-org.git/ > > -- > Best regards, > Zhongwei From jamsheed.c.m at oracle.com Sat Apr 8 13:30:35 2017 From: jamsheed.c.m at oracle.com (Jamsheed C m) Date: Sat, 8 Apr 2017 19:00:35 +0530 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: Message-ID: Hi Zhongwei, ReservedCodeCacheSize of Openjdk Amr64 JDK port is 240M (by default) and Openjdk Aarch64 JDK port is 128M(by default), it would be good if we set same value for both ports for performance comparison(i.e set both to 128M). Thank you! Best Regards, Jamsheed On 3/30/2017 7:13 AM, Zhongwei Yao wrote: > Hi, > We have been running some Java benchmarks on AArch64 servers with different > OpenJDK ports: aarch64 and arm64. You can find the results at [1]. > And our JDK version: > - aarch64 OpenJDK: build from latest JDK9 source with config: > "--with-jvm-variants=server --with-debug-level=release" > > - arm64 OpenJDK: build from latest JDK9 source with config: > "--with-jvm-variants=server --with-debug-level=release --wi > th-cpu-port=arm64" > > And from the data, aarch64 OpenJDK is better than arm64 OpenJDK > generally, but with some exceptions. So we think it is worth to take a look > at following cases for aarch64 OpenJDK: > - Dacapo's sunflow, tradebeans and xalan > - SPECjvm2008's scimark.lu.large > > And we also find arm64 is better than aarch64 for byte/short data type > vectorization in our JMH cases ([2]), which we are investigating. > > Feedbacks are welcome. Thanks! > > [1]: > https://docs.google.com/spreadsheets/d/18iklOrbaL67i46XHsPTrdTObWqUJJK8EO4-k0eqdLKM/edit?usp=sharing > [2]: https://git.linaro.org/leg/openjdk/jmh-linaro-org.git/ > From ci_notify at linaro.org Sat Apr 8 16:22:51 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sat, 8 Apr 2017 16:22:51 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <4561636.236.1491668573158.JavaMail.jenkins@630323898de9> 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/097/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/02 pass: 1,387; fail: 5 Build 1: aarch64/2017/mar/03 pass: 1,387; fail: 5 Build 2: aarch64/2017/mar/08 pass: 1,388; fail: 5 Build 3: aarch64/2017/mar/11 pass: 1,388; fail: 5 Build 4: aarch64/2017/mar/13 pass: 1,388; fail: 5 Build 5: aarch64/2017/mar/15 pass: 1,387; fail: 6 Build 6: aarch64/2017/mar/17 pass: 1,390; fail: 6 Build 7: aarch64/2017/mar/19 pass: 1,391; fail: 5 Build 8: aarch64/2017/mar/21 pass: 1,391; fail: 5 Build 9: aarch64/2017/mar/25 pass: 1,393; fail: 4 Build 10: aarch64/2017/mar/27 pass: 1,393; fail: 4 Build 11: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 12: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 13: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 14: aarch64/2017/apr/07 pass: 1,396; fail: 4 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/02 pass: 7,272; fail: 705; error: 15 Build 1: aarch64/2017/mar/03 pass: 7,252; fail: 720; error: 21 Build 2: aarch64/2017/mar/08 pass: 7,251; fail: 720; error: 23 Build 3: aarch64/2017/mar/11 pass: 7,263; fail: 718; error: 18 Build 4: aarch64/2017/mar/13 pass: 7,268; fail: 710; error: 21 Build 5: aarch64/2017/mar/15 pass: 7,283; fail: 693; error: 25 Build 6: aarch64/2017/mar/17 pass: 7,273; fail: 709; error: 20 Build 7: aarch64/2017/mar/19 pass: 7,253; fail: 727; error: 24 Build 8: aarch64/2017/mar/21 pass: 7,294; fail: 689; error: 21 Build 9: aarch64/2017/mar/25 pass: 7,278; fail: 713; error: 23 Build 10: aarch64/2017/mar/27 pass: 7,304; fail: 690; error: 20 Build 11: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 12: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 13: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 14: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/02 pass: 3,862; error: 2 Build 1: aarch64/2017/mar/03 pass: 3,863; error: 2 Build 2: aarch64/2017/mar/08 pass: 3,866; error: 1 Build 3: aarch64/2017/mar/11 pass: 3,871; error: 2 Build 4: aarch64/2017/mar/13 pass: 3,872; error: 1 Build 5: aarch64/2017/mar/15 pass: 3,874; error: 4 Build 6: aarch64/2017/mar/17 pass: 3,878; error: 2 Build 7: aarch64/2017/mar/19 pass: 3,878; error: 2 Build 8: aarch64/2017/mar/21 pass: 3,876; error: 5 Build 9: aarch64/2017/mar/25 pass: 3,886; fail: 1 Build 10: aarch64/2017/mar/27 pass: 3,883; error: 4 Build 11: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 12: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 13: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 14: aarch64/2017/apr/07 pass: 3,889; error: 2 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/02 pass: 1,390; fail: 5 Build 1: aarch64/2017/mar/03 pass: 1,390; fail: 5 Build 2: aarch64/2017/mar/08 pass: 1,391; fail: 6 Build 3: aarch64/2017/mar/11 pass: 1,392; fail: 5 Build 4: aarch64/2017/mar/13 pass: 1,392; fail: 5 Build 5: aarch64/2017/mar/15 pass: 1,392; fail: 5 Build 6: aarch64/2017/mar/17 pass: 1,395; fail: 5 Build 7: aarch64/2017/mar/19 pass: 1,395; fail: 5 Build 8: aarch64/2017/mar/21 pass: 1,394; fail: 6 Build 9: aarch64/2017/mar/25 pass: 1,397; fail: 4 Build 10: aarch64/2017/mar/27 pass: 1,396; fail: 5 Build 11: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 12: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 13: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 14: aarch64/2017/apr/07 pass: 1,400; fail: 4 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/02 pass: 7,284; fail: 689; error: 19 Build 1: aarch64/2017/mar/03 pass: 7,257; fail: 720; error: 16 Build 2: aarch64/2017/mar/08 pass: 7,296; fail: 679; error: 19 Build 3: aarch64/2017/mar/11 pass: 7,261; fail: 722; error: 16 Build 4: aarch64/2017/mar/13 pass: 7,290; fail: 687; error: 22 Build 5: aarch64/2017/mar/15 pass: 7,285; fail: 697; error: 19 Build 6: aarch64/2017/mar/17 pass: 7,278; fail: 703; error: 21 Build 7: aarch64/2017/mar/19 pass: 7,261; fail: 723; error: 20 Build 8: aarch64/2017/mar/21 pass: 7,271; fail: 712; error: 21 Build 9: aarch64/2017/mar/25 pass: 7,284; fail: 708; error: 22 Build 10: aarch64/2017/mar/27 pass: 7,297; fail: 695; error: 22 Build 11: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 12: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 13: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 14: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/02 pass: 3,858; fail: 1; error: 5 Build 1: aarch64/2017/mar/03 pass: 3,863; fail: 1; error: 2 Build 2: aarch64/2017/mar/08 pass: 3,867 Build 3: aarch64/2017/mar/11 pass: 3,873 Build 4: aarch64/2017/mar/13 pass: 3,871; error: 2 Build 5: aarch64/2017/mar/15 pass: 3,878 Build 6: aarch64/2017/mar/17 pass: 3,876; error: 4 Build 7: aarch64/2017/mar/19 pass: 3,876; error: 4 Build 8: aarch64/2017/mar/21 pass: 3,879; error: 2 Build 9: aarch64/2017/mar/25 pass: 3,885; error: 2 Build 10: aarch64/2017/mar/27 pass: 3,881; error: 6 Build 11: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 12: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 13: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 14: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 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.90x 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.76, Server: 117.63 Client 72.76 / Client 2014-04-01 (43.00): 1.69x Server 117.63 / Server 2014-04-01 (71.00): 1.66x 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-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/ 2017-03-26 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/084/results/ 2017-03-28 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/086/results/ 2017-03-31 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/089/results/ 2017-04-02 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/091/results/ 2017-04-04 pass rate: 11550/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/093/results/ 2017-04-08 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/097/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/ From zhongwei.yao at linaro.org Mon Apr 10 02:17:15 2017 From: zhongwei.yao at linaro.org (Zhongwei Yao) Date: Mon, 10 Apr 2017 10:17:15 +0800 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: <1EC3C311-D6E0-427C-A21B-2161F49717BC@oracle.com> References: <1EC3C311-D6E0-427C-A21B-2161F49717BC@oracle.com> Message-ID: Hi, Bob, There are specJBB2015 and Hadoop TeraSort in our benchmarks results already. Please check the other tabs in our benchmarks result in the spreadsheet. Thanks! On 8 April 2017 at 03:37, Bob Vandette wrote: > Zongwei, > > Thanks for running these benchmarks. > > Have you had the chance to try any server workload type of benchmarks? > > Just wondering if you had any results running things like specJBB or > Hadoop TeraSort. > > Bob. > > > > On Mar 29, 2017, at 9:43 PM, Zhongwei Yao > wrote: > > > > Hi, > > We have been running some Java benchmarks on AArch64 servers with > different > > OpenJDK ports: aarch64 and arm64. You can find the results at [1]. > > And our JDK version: > > - aarch64 OpenJDK: build from latest JDK9 source with config: > > "--with-jvm-variants=server --with-debug-level=release" > > > > - arm64 OpenJDK: build from latest JDK9 source with config: > > "--with-jvm-variants=server --with-debug-level=release --wi > > th-cpu-port=arm64" > > > > And from the data, aarch64 OpenJDK is better than arm64 OpenJDK > > generally, but with some exceptions. So we think it is worth to take a > look > > at following cases for aarch64 OpenJDK: > > - Dacapo's sunflow, tradebeans and xalan > > - SPECjvm2008's scimark.lu.large > > > > And we also find arm64 is better than aarch64 for byte/short data type > > vectorization in our JMH cases ([2]), which we are investigating. > > > > Feedbacks are welcome. Thanks! > > > > [1]: > > https://docs.google.com/spreadsheets/d/18iklOrbaL67i46XHsPTrdTObWqUJJ > K8EO4-k0eqdLKM/edit?usp=sharing > > [2]: https://git.linaro.org/leg/openjdk/jmh-linaro-org.git/ > > > > -- > > Best regards, > > Zhongwei > > -- Best regards, Zhongwei From zhongwei.yao at linaro.org Mon Apr 10 02:19:11 2017 From: zhongwei.yao at linaro.org (Zhongwei Yao) Date: Mon, 10 Apr 2017 10:19:11 +0800 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: Message-ID: Hi Jamsheed, Thanks for your suggestions! I'll check that option. On 8 April 2017 at 21:30, Jamsheed C m wrote: > Hi Zhongwei, > > ReservedCodeCacheSize of Openjdk Amr64 JDK port is 240M (by default) and > Openjdk Aarch64 JDK port is 128M(by default), it would be good if we set > same value for both ports for performance comparison(i.e set both to 128M). > > Thank you! > > Best Regards, > > Jamsheed > > On 3/30/2017 7:13 AM, Zhongwei Yao wrote: > >> Hi, >> We have been running some Java benchmarks on AArch64 servers with >> different >> OpenJDK ports: aarch64 and arm64. You can find the results at [1]. >> And our JDK version: >> - aarch64 OpenJDK: build from latest JDK9 source with config: >> "--with-jvm-variants=server --with-debug-level=release" >> >> - arm64 OpenJDK: build from latest JDK9 source with config: >> "--with-jvm-variants=server --with-debug-level=release --wi >> th-cpu-port=arm64" >> >> And from the data, aarch64 OpenJDK is better than arm64 OpenJDK >> generally, but with some exceptions. So we think it is worth to take a >> look >> at following cases for aarch64 OpenJDK: >> - Dacapo's sunflow, tradebeans and xalan >> - SPECjvm2008's scimark.lu.large >> >> And we also find arm64 is better than aarch64 for byte/short data type >> vectorization in our JMH cases ([2]), which we are investigating. >> >> Feedbacks are welcome. Thanks! >> >> [1]: >> https://docs.google.com/spreadsheets/d/18iklOrbaL67i46XHsPTr >> dTObWqUJJK8EO4-k0eqdLKM/edit?usp=sharing >> [2]: https://git.linaro.org/leg/openjdk/jmh-linaro-org.git/ >> >> > -- Best regards, Zhongwei From zhongwei.yao at linaro.org Mon Apr 10 02:46:08 2017 From: zhongwei.yao at linaro.org (Zhongwei Yao) Date: Mon, 10 Apr 2017 10:46:08 +0800 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: <719cae05-efc8-0550-e999-9b5b113c0662@redhat.com> References: <719cae05-efc8-0550-e999-9b5b113c0662@redhat.com> Message-ID: Hi, Andrew, Thanks for pointing out. Here are the commands to run them: Dacapo (version: dacapo-9.12-bach.jar): java -jar dacapo.jar -C avrora java -jar dacapo.jar -C fop java -jar dacapo.jar -C h2 java -jar dacapo.jar -C jython java -jar dacapo.jar -C luindex java -jar dacapo.jar -C lusearch java -jar dacapo.jar -C pmd java -jar dacapo.jar -C sunflow java --add-opens java.base/java.lang=ALL-UNNAMED -jar dacapo.jar -C tradebeans java -jar dacapo.jar -C xalan SPECjvm2008: java --add-exports jdk.compiler/com.sun.tools.javac.main=ALL-UNNAMED --add-exports java.xml/com.sun.org.apache.xerces.internal.util=ALL-UNNAMED --add-exports java.xml/com.sun.org.apache.xerces.internal.parsers=ALL-UNNAMED -jar SPECjvm2008.jar -pf props/specjvm.new.properties --jvmArgs -coe -ikv -wt 5s -i 5 -it 20s SPECjbb2015: java --add-modules java.se.ee -Xms4g -Xmx16g -jar specjbb2015.jar -m COMPOSITE Hadoop TeraSort: ./bin/hadoop jar ./share/hadoop/mapreduce/hadoop-mapreduce-examples-*.jar teragen 20000000 terainput time ./bin/hadoop jar ./share/hadoop/mapreduce/hadoop-mapreduce-examples-*.jar terasort terainput teraoutput ./bin/hadoop jar ./share/hadoop/mapreduce/hadoop-mapreduce-examples-*.jar teravalidate -D mapred.reduce.tasks=8 teraoutput teravalidate On 8 April 2017 at 01:03, Andrew Haley wrote: > On 30/03/17 02:43, Zhongwei Yao wrote: > > And from the data, aarch64 OpenJDK is better than arm64 OpenJDK > > generally, but with some exceptions. So we think it is worth to take a > look > > at following cases for aarch64 OpenJDK: > > - Dacapo's sunflow, tradebeans and xalan > > - SPECjvm2008's scimark.lu.large > > > > And we also find arm64 is better than aarch64 for byte/short data type > > vectorization in our JMH cases ([2]), which we are investigating. > > > > Feedbacks are welcome. Thanks! > > Thanks for doing this. > > It would help a great deal if you could share with us how you > ran these tests. For example, I get exceptions if I try to run > tradebeans from dacapo-9.12-bach.jar. > > Andrew. > > -- Best regards, Zhongwei From aph at redhat.com Mon Apr 10 08:33:41 2017 From: aph at redhat.com (Andrew Haley) Date: Mon, 10 Apr 2017 09:33:41 +0100 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: <719cae05-efc8-0550-e999-9b5b113c0662@redhat.com> Message-ID: On 10/04/17 03:46, Zhongwei Yao wrote: > Thanks for pointing out. Here are the commands to run them: Doesn't work for me. Exactly which version of Java are you using? Andrew. From zhongwei.yao at linaro.org Mon Apr 10 09:49:47 2017 From: zhongwei.yao at linaro.org (Zhongwei Yao) Date: Mon, 10 Apr 2017 17:49:47 +0800 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: <719cae05-efc8-0550-e999-9b5b113c0662@redhat.com> Message-ID: My aarch64 java is built from latest jdk9 dev tree with following configure: --with-debug-level=release --with-jvm-variants=server On 10 April 2017 at 16:33, Andrew Haley wrote: > On 10/04/17 03:46, Zhongwei Yao wrote: > > Thanks for pointing out. Here are the commands to run them: > > Doesn't work for me. Exactly which version of Java are you using? > > Andrew. > > -- Best regards, Zhongwei From aph at redhat.com Mon Apr 10 09:59:26 2017 From: aph at redhat.com (Andrew Haley) Date: Mon, 10 Apr 2017 10:59:26 +0100 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: <719cae05-efc8-0550-e999-9b5b113c0662@redhat.com> Message-ID: On 10/04/17 10:49, Zhongwei Yao wrote: > My aarch64 java is built from latest jdk9 dev tree with following configure: > --with-debug-level=release --with-jvm-variants=server OK, I'll try again. Andrew. From bob.vandette at oracle.com Mon Apr 10 14:37:01 2017 From: bob.vandette at oracle.com (Bob Vandette) Date: Mon, 10 Apr 2017 10:37:01 -0400 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: <1EC3C311-D6E0-427C-A21B-2161F49717BC@oracle.com> Message-ID: Thanks for pointing that out. The bottom tabs was offscreen when I popped up the spreadsheet on my laptop. I assume Partner A has implemented some of the Large System Extensions on the system your are testing on? Bob. > On Apr 9, 2017, at 10:17 PM, Zhongwei Yao wrote: > > Hi, Bob, > There are specJBB2015 and Hadoop TeraSort in our benchmarks results already. Please check the other tabs in our benchmarks result in the spreadsheet. Thanks! > > On 8 April 2017 at 03:37, Bob Vandette > wrote: > Zongwei, > > Thanks for running these benchmarks. > > Have you had the chance to try any server workload type of benchmarks? > > Just wondering if you had any results running things like specJBB or Hadoop TeraSort. > > Bob. > > > > On Mar 29, 2017, at 9:43 PM, Zhongwei Yao > wrote: > > > > Hi, > > We have been running some Java benchmarks on AArch64 servers with different > > OpenJDK ports: aarch64 and arm64. You can find the results at [1]. > > And our JDK version: > > - aarch64 OpenJDK: build from latest JDK9 source with config: > > "--with-jvm-variants=server --with-debug-level=release" > > > > - arm64 OpenJDK: build from latest JDK9 source with config: > > "--with-jvm-variants=server --with-debug-level=release --wi > > th-cpu-port=arm64" > > > > And from the data, aarch64 OpenJDK is better than arm64 OpenJDK > > generally, but with some exceptions. So we think it is worth to take a look > > at following cases for aarch64 OpenJDK: > > - Dacapo's sunflow, tradebeans and xalan > > - SPECjvm2008's scimark.lu.large > > > > And we also find arm64 is better than aarch64 for byte/short data type > > vectorization in our JMH cases ([2]), which we are investigating. > > > > Feedbacks are welcome. Thanks! > > > > [1]: > > https://docs.google.com/spreadsheets/d/18iklOrbaL67i46XHsPTrdTObWqUJJK8EO4-k0eqdLKM/edit?usp=sharing > > [2]: https://git.linaro.org/leg/openjdk/jmh-linaro-org.git/ > > > > -- > > Best regards, > > Zhongwei > > > > > -- > Best regards, > Zhongwei From aph at redhat.com Mon Apr 10 15:46:51 2017 From: aph at redhat.com (Andrew Haley) Date: Mon, 10 Apr 2017 16:46:51 +0100 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: <719cae05-efc8-0550-e999-9b5b113c0662@redhat.com> Message-ID: On 10/04/17 03:46, Zhongwei Yao wrote: > java --add-opens java.base/java.lang=ALL-UNNAMED -jar dacapo.jar -C > tradebeans I really can't reproduce your result. I'm looking at a significant advantage for aarch64 over arm64. Please send me information about the hardware you're using, offlist. Andrew. From zhongwei.yao at linaro.org Tue Apr 11 02:00:31 2017 From: zhongwei.yao at linaro.org (Zhongwei Yao) Date: Tue, 11 Apr 2017 10:00:31 +0800 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: <1EC3C311-D6E0-427C-A21B-2161F49717BC@oracle.com> Message-ID: I see. And I would share the Partner A's information by offlist discussion. On 10 April 2017 at 22:37, Bob Vandette wrote: > Thanks for pointing that out. The bottom tabs was offscreen when I popped > up the spreadsheet > on my laptop. > > I assume Partner A has implemented some of the Large System Extensions on > the system your > are testing on? > > Bob. > > On Apr 9, 2017, at 10:17 PM, Zhongwei Yao wrote: > > Hi, Bob, > There are specJBB2015 and Hadoop TeraSort in our benchmarks results > already. Please check the other tabs in our benchmarks result in the > spreadsheet. Thanks! > > On 8 April 2017 at 03:37, Bob Vandette wrote: > >> Zongwei, >> >> Thanks for running these benchmarks. >> >> Have you had the chance to try any server workload type of benchmarks? >> >> Just wondering if you had any results running things like specJBB or >> Hadoop TeraSort. >> >> Bob. >> >> >> > On Mar 29, 2017, at 9:43 PM, Zhongwei Yao >> wrote: >> > >> > Hi, >> > We have been running some Java benchmarks on AArch64 servers with >> different >> > OpenJDK ports: aarch64 and arm64. You can find the results at [1]. >> > And our JDK version: >> > - aarch64 OpenJDK: build from latest JDK9 source with config: >> > "--with-jvm-variants=server --with-debug-level=release" >> > >> > - arm64 OpenJDK: build from latest JDK9 source with config: >> > "--with-jvm-variants=server --with-debug-level=release --wi >> > th-cpu-port=arm64" >> > >> > And from the data, aarch64 OpenJDK is better than arm64 OpenJDK >> > generally, but with some exceptions. So we think it is worth to take a >> look >> > at following cases for aarch64 OpenJDK: >> > - Dacapo's sunflow, tradebeans and xalan >> > - SPECjvm2008's scimark.lu.large >> > >> > And we also find arm64 is better than aarch64 for byte/short data type >> > vectorization in our JMH cases ([2]), which we are investigating. >> > >> > Feedbacks are welcome. Thanks! >> > >> > [1]: >> > https://docs.google.com/spreadsheets/d/18iklOrbaL67i46XHsPTr >> dTObWqUJJK8EO4-k0eqdLKM/edit?usp=sharing >> > [2]: https://git.linaro.org/leg/openjdk/jmh-linaro-org.git/ >> > >> > -- >> > Best regards, >> > Zhongwei >> >> > > > -- > Best regards, > Zhongwei > > > -- Best regards, Zhongwei From zhongwei.yao at linaro.org Tue Apr 11 02:22:28 2017 From: zhongwei.yao at linaro.org (Zhongwei Yao) Date: Tue, 11 Apr 2017 10:22:28 +0800 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: <719cae05-efc8-0550-e999-9b5b113c0662@redhat.com> Message-ID: For the tradebeans, the standard deviation is not low. I think it is worth re-run the bench enough times to get stable result. I'll send you the hardware info offlist. On 10 April 2017 at 23:46, Andrew Haley wrote: > On 10/04/17 03:46, Zhongwei Yao wrote: > > java --add-opens java.base/java.lang=ALL-UNNAMED -jar dacapo.jar -C > > tradebeans > > I really can't reproduce your result. I'm looking at a significant > advantage for aarch64 over arm64. Please send me information about > the hardware you're using, offlist. > > Andrew. > > -- Best regards, Zhongwei From ci_notify at linaro.org Wed Apr 12 16:54:19 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Wed, 12 Apr 2017 16:54:19 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <803759259.599.1492016060689.JavaMail.jenkins@90c74440cc95> 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/101/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/03 pass: 1,387; fail: 5 Build 1: aarch64/2017/mar/08 pass: 1,388; fail: 5 Build 2: aarch64/2017/mar/11 pass: 1,388; fail: 5 Build 3: aarch64/2017/mar/13 pass: 1,388; fail: 5 Build 4: aarch64/2017/mar/15 pass: 1,387; fail: 6 Build 5: aarch64/2017/mar/17 pass: 1,390; fail: 6 Build 6: aarch64/2017/mar/19 pass: 1,391; fail: 5 Build 7: aarch64/2017/mar/21 pass: 1,391; fail: 5 Build 8: aarch64/2017/mar/25 pass: 1,393; fail: 4 Build 9: aarch64/2017/mar/27 pass: 1,393; fail: 4 Build 10: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 11: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 12: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 13: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 14: aarch64/2017/apr/11 pass: 1,399; fail: 7 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/03 pass: 7,252; fail: 720; error: 21 Build 1: aarch64/2017/mar/08 pass: 7,251; fail: 720; error: 23 Build 2: aarch64/2017/mar/11 pass: 7,263; fail: 718; error: 18 Build 3: aarch64/2017/mar/13 pass: 7,268; fail: 710; error: 21 Build 4: aarch64/2017/mar/15 pass: 7,283; fail: 693; error: 25 Build 5: aarch64/2017/mar/17 pass: 7,273; fail: 709; error: 20 Build 6: aarch64/2017/mar/19 pass: 7,253; fail: 727; error: 24 Build 7: aarch64/2017/mar/21 pass: 7,294; fail: 689; error: 21 Build 8: aarch64/2017/mar/25 pass: 7,278; fail: 713; error: 23 Build 9: aarch64/2017/mar/27 pass: 7,304; fail: 690; error: 20 Build 10: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 11: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 12: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 13: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 14: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/03 pass: 3,863; error: 2 Build 1: aarch64/2017/mar/08 pass: 3,866; error: 1 Build 2: aarch64/2017/mar/11 pass: 3,871; error: 2 Build 3: aarch64/2017/mar/13 pass: 3,872; error: 1 Build 4: aarch64/2017/mar/15 pass: 3,874; error: 4 Build 5: aarch64/2017/mar/17 pass: 3,878; error: 2 Build 6: aarch64/2017/mar/19 pass: 3,878; error: 2 Build 7: aarch64/2017/mar/21 pass: 3,876; error: 5 Build 8: aarch64/2017/mar/25 pass: 3,886; fail: 1 Build 9: aarch64/2017/mar/27 pass: 3,883; error: 4 Build 10: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 11: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 12: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 13: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 14: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/03 pass: 1,390; fail: 5 Build 1: aarch64/2017/mar/08 pass: 1,391; fail: 6 Build 2: aarch64/2017/mar/11 pass: 1,392; fail: 5 Build 3: aarch64/2017/mar/13 pass: 1,392; fail: 5 Build 4: aarch64/2017/mar/15 pass: 1,392; fail: 5 Build 5: aarch64/2017/mar/17 pass: 1,395; fail: 5 Build 6: aarch64/2017/mar/19 pass: 1,395; fail: 5 Build 7: aarch64/2017/mar/21 pass: 1,394; fail: 6 Build 8: aarch64/2017/mar/25 pass: 1,397; fail: 4 Build 9: aarch64/2017/mar/27 pass: 1,396; fail: 5 Build 10: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 11: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 12: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 13: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 14: aarch64/2017/apr/11 pass: 1,403; fail: 7 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/03 pass: 7,257; fail: 720; error: 16 Build 1: aarch64/2017/mar/08 pass: 7,296; fail: 679; error: 19 Build 2: aarch64/2017/mar/11 pass: 7,261; fail: 722; error: 16 Build 3: aarch64/2017/mar/13 pass: 7,290; fail: 687; error: 22 Build 4: aarch64/2017/mar/15 pass: 7,285; fail: 697; error: 19 Build 5: aarch64/2017/mar/17 pass: 7,278; fail: 703; error: 21 Build 6: aarch64/2017/mar/19 pass: 7,261; fail: 723; error: 20 Build 7: aarch64/2017/mar/21 pass: 7,271; fail: 712; error: 21 Build 8: aarch64/2017/mar/25 pass: 7,284; fail: 708; error: 22 Build 9: aarch64/2017/mar/27 pass: 7,297; fail: 695; error: 22 Build 10: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 11: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 12: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 13: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 14: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/03 pass: 3,863; fail: 1; error: 2 Build 1: aarch64/2017/mar/08 pass: 3,867 Build 2: aarch64/2017/mar/11 pass: 3,873 Build 3: aarch64/2017/mar/13 pass: 3,871; error: 2 Build 4: aarch64/2017/mar/15 pass: 3,878 Build 5: aarch64/2017/mar/17 pass: 3,876; error: 4 Build 6: aarch64/2017/mar/19 pass: 3,876; error: 4 Build 7: aarch64/2017/mar/21 pass: 3,879; error: 2 Build 8: aarch64/2017/mar/25 pass: 3,885; error: 2 Build 9: aarch64/2017/mar/27 pass: 3,881; error: 6 Build 10: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 11: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 12: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 13: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 14: aarch64/2017/apr/11 pass: 3,888; fail: 1; 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.02x Relative performance: Server critical-jOPS (nc): 0.74x 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: 71.65, Server: 120.64 Client 71.65 / Client 2014-04-01 (43.00): 1.67x Server 120.64 / Server 2014-04-01 (71.00): 1.70x 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-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/ 2017-03-26 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/084/results/ 2017-03-28 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/086/results/ 2017-03-31 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/089/results/ 2017-04-02 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/091/results/ 2017-04-04 pass rate: 11550/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/093/results/ 2017-04-08 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/097/results/ 2017-04-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/101/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/ From stuart.monteith at linaro.org Thu Apr 13 13:09:01 2017 From: stuart.monteith at linaro.org (Stuart Monteith) Date: Thu, 13 Apr 2017 14:09:01 +0100 Subject: [aarch64-port-dev ] Linaro OpenJDK 1704 Engineering Builds available Message-ID: Hello, JDK8u, 9 and 7 builds for aarch64 (marked 1704) are now available here: http://openjdk.linaro.org/relhome.htm They have the following BOM ("Bill Of Materials" ) file contents. BOM for http://icedtea.classpath.org/hg/icedtea7-forest Subdir Hash Tag Tag hash . 2f2744eb059a jdk7u131-b00 259e6ca7faf1 corba d28d6461f8b8 jdk7u131-b00 d93d13bcb01d jaxp 30630c7ce6bb jdk7u131-b00 51ed13d07beb jaxws 27d0b96548ab jdk7u131-b00 edcc7c1e2975 langtools f6551a412274 jdk7u131-b00 240ca8086e71 jdk d6392d3c3e8d jdk7u131-b00 86d0df913089 hotspot 4eea81cf6f63 jdk7u131-b00 95e4ea3d479e BOM for http://hg.openjdk.java.net/aarch64-port/jdk8u Subdir "Hash Tag" Tag hash . 0ea0e60bbbfa aarch64-jdk8u121-b14 0ecc94005f98 corba d219158e0758 aarch64-jdk8u121-b14 a8df076b8d46 jaxp 6658da128353 aarch64-jdk8u121-b14 6df944cb6374 jaxws 3c9b35d71d99 aarch64-jdk8u121-b14 115879cb1143 langtools 06ec76842b04 aarch64-jdk8u121-b14 d2d11291ba74 jdk 86b9391b28d7 aarch64-jdk8u121-b14 223e917a5196 hotspot e5d7f637919f aarch64-jdk8u121-b14 f65e5ad41276 nashorn e42e6f6a6aae aarch64-jdk8u121-b14 b2780a3d3bd9 BOM for http://hg.openjdk.java.net/jdk9/dev Subdir Hash Tag Tag hash . aff4f339acd4 jdk-9+164 7810f75d016a corba a510b2201154 jdk-9+164 965bbae30727 jaxp 554196039897 jdk-9+164 6dc790a4e831 jaxws e4cd98db3249 jdk-9+164 1a52de2da827 langtools a3a30789ab61 jdk-9+164 c7f3df19667b jdk 182207b208dc jdk-9+164 6dea581453d7 hotspot d80c43d9a99e jdk-9+164 0af429be8bba nashorn e36e62d3ea53 jdk-9+164 b473fab09baa BR, Stuart From gnu.andrew at redhat.com Thu Apr 13 21:21:23 2017 From: gnu.andrew at redhat.com (Andrew Hughes) Date: Thu, 13 Apr 2017 17:21:23 -0400 (EDT) Subject: [aarch64-port-dev ] jdk8: backport of 8177661: AArch64: Incorrect C2 patterns cause system register corruption In-Reply-To: <45f9c343-459e-5eb2-89e7-835721f8313e@redhat.com> References: <349a8ce3-4377-4c19-fee8-020d7fbc8ee5@redhat.com> <53ac52fa-9c05-77c9-a350-8560613ce986@redhat.com> <1911453721.17127167.1490830012926.JavaMail.zimbra@redhat.com> <45f9c343-459e-5eb2-89e7-835721f8313e@redhat.com> Message-ID: <817138535.27263009.1492118483571.JavaMail.zimbra@redhat.com> ----- Original Message ----- > On 30/03/17 00:26, Andrew Hughes wrote: > > There's no need to put it in jdk8u-shenandoah either, as it pulls changes > > from aarch64/jdk8u anyway. > > Mmm, I know that, but on what clock tick are those changes pulled? > At least quarterly with every security update / release. We can do out-of-band merges as well if required, but nothing is going to languish there for longer than three months. Back to the subject of this bug; are there plans to backport this to 7? A cursory glance suggests the issue is present there too. > Andrew. > > Thanks, -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) Web Site: http://fuseyism.com Twitter: https://twitter.com/gnu_andrew_java PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 From ci_notify at linaro.org Fri Apr 14 16:44:11 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 14 Apr 2017 16:44:11 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <1124963354.780.1492188253502.JavaMail.jenkins@90c74440cc95> 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/103/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/08 pass: 1,388; fail: 5 Build 1: aarch64/2017/mar/11 pass: 1,388; fail: 5 Build 2: aarch64/2017/mar/13 pass: 1,388; fail: 5 Build 3: aarch64/2017/mar/15 pass: 1,387; fail: 6 Build 4: aarch64/2017/mar/17 pass: 1,390; fail: 6 Build 5: aarch64/2017/mar/19 pass: 1,391; fail: 5 Build 6: aarch64/2017/mar/21 pass: 1,391; fail: 5 Build 7: aarch64/2017/mar/25 pass: 1,393; fail: 4 Build 8: aarch64/2017/mar/27 pass: 1,393; fail: 4 Build 9: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 10: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 11: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 12: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 13: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 14: aarch64/2017/apr/13 pass: 1,400; fail: 7 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/08 pass: 7,251; fail: 720; error: 23 Build 1: aarch64/2017/mar/11 pass: 7,263; fail: 718; error: 18 Build 2: aarch64/2017/mar/13 pass: 7,268; fail: 710; error: 21 Build 3: aarch64/2017/mar/15 pass: 7,283; fail: 693; error: 25 Build 4: aarch64/2017/mar/17 pass: 7,273; fail: 709; error: 20 Build 5: aarch64/2017/mar/19 pass: 7,253; fail: 727; error: 24 Build 6: aarch64/2017/mar/21 pass: 7,294; fail: 689; error: 21 Build 7: aarch64/2017/mar/25 pass: 7,278; fail: 713; error: 23 Build 8: aarch64/2017/mar/27 pass: 7,304; fail: 690; error: 20 Build 9: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 10: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 11: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 12: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 13: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 14: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/08 pass: 3,866; error: 1 Build 1: aarch64/2017/mar/11 pass: 3,871; error: 2 Build 2: aarch64/2017/mar/13 pass: 3,872; error: 1 Build 3: aarch64/2017/mar/15 pass: 3,874; error: 4 Build 4: aarch64/2017/mar/17 pass: 3,878; error: 2 Build 5: aarch64/2017/mar/19 pass: 3,878; error: 2 Build 6: aarch64/2017/mar/21 pass: 3,876; error: 5 Build 7: aarch64/2017/mar/25 pass: 3,886; fail: 1 Build 8: aarch64/2017/mar/27 pass: 3,883; error: 4 Build 9: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 10: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 11: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 12: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 13: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 14: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/08 pass: 1,391; fail: 6 Build 1: aarch64/2017/mar/11 pass: 1,392; fail: 5 Build 2: aarch64/2017/mar/13 pass: 1,392; fail: 5 Build 3: aarch64/2017/mar/15 pass: 1,392; fail: 5 Build 4: aarch64/2017/mar/17 pass: 1,395; fail: 5 Build 5: aarch64/2017/mar/19 pass: 1,395; fail: 5 Build 6: aarch64/2017/mar/21 pass: 1,394; fail: 6 Build 7: aarch64/2017/mar/25 pass: 1,397; fail: 4 Build 8: aarch64/2017/mar/27 pass: 1,396; fail: 5 Build 9: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 10: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 11: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 12: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 13: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 14: aarch64/2017/apr/13 pass: 1,404; fail: 7 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/08 pass: 7,296; fail: 679; error: 19 Build 1: aarch64/2017/mar/11 pass: 7,261; fail: 722; error: 16 Build 2: aarch64/2017/mar/13 pass: 7,290; fail: 687; error: 22 Build 3: aarch64/2017/mar/15 pass: 7,285; fail: 697; error: 19 Build 4: aarch64/2017/mar/17 pass: 7,278; fail: 703; error: 21 Build 5: aarch64/2017/mar/19 pass: 7,261; fail: 723; error: 20 Build 6: aarch64/2017/mar/21 pass: 7,271; fail: 712; error: 21 Build 7: aarch64/2017/mar/25 pass: 7,284; fail: 708; error: 22 Build 8: aarch64/2017/mar/27 pass: 7,297; fail: 695; error: 22 Build 9: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 10: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 11: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 12: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 13: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 14: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/08 pass: 3,867 Build 1: aarch64/2017/mar/11 pass: 3,873 Build 2: aarch64/2017/mar/13 pass: 3,871; error: 2 Build 3: aarch64/2017/mar/15 pass: 3,878 Build 4: aarch64/2017/mar/17 pass: 3,876; error: 4 Build 5: aarch64/2017/mar/19 pass: 3,876; error: 4 Build 6: aarch64/2017/mar/21 pass: 3,879; error: 2 Build 7: aarch64/2017/mar/25 pass: 3,885; error: 2 Build 8: aarch64/2017/mar/27 pass: 3,881; error: 6 Build 9: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 10: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 11: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 12: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 13: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 14: aarch64/2017/apr/13 pass: 3,890; error: 1 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.68x 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: 119.62 Client 72.38 / Client 2014-04-01 (43.00): 1.68x Server 119.62 / Server 2014-04-01 (71.00): 1.68x 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-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/ 2017-03-26 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/084/results/ 2017-03-28 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/086/results/ 2017-03-31 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/089/results/ 2017-04-02 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/091/results/ 2017-04-04 pass rate: 11550/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/093/results/ 2017-04-08 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/097/results/ 2017-04-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/101/results/ 2017-04-14 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/103/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/ From ci_notify at linaro.org Sun Apr 16 16:28:00 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sun, 16 Apr 2017 16:28:00 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <488248897.871.1492360081840.JavaMail.jenkins@90c74440cc95> 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/105/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/11 pass: 1,388; fail: 5 Build 1: aarch64/2017/mar/13 pass: 1,388; fail: 5 Build 2: aarch64/2017/mar/15 pass: 1,387; fail: 6 Build 3: aarch64/2017/mar/17 pass: 1,390; fail: 6 Build 4: aarch64/2017/mar/19 pass: 1,391; fail: 5 Build 5: aarch64/2017/mar/21 pass: 1,391; fail: 5 Build 6: aarch64/2017/mar/25 pass: 1,393; fail: 4 Build 7: aarch64/2017/mar/27 pass: 1,393; fail: 4 Build 8: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 9: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 10: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 11: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 12: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 13: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 14: aarch64/2017/apr/15 pass: 1,400; fail: 7 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/11 pass: 7,263; fail: 718; error: 18 Build 1: aarch64/2017/mar/13 pass: 7,268; fail: 710; error: 21 Build 2: aarch64/2017/mar/15 pass: 7,283; fail: 693; error: 25 Build 3: aarch64/2017/mar/17 pass: 7,273; fail: 709; error: 20 Build 4: aarch64/2017/mar/19 pass: 7,253; fail: 727; error: 24 Build 5: aarch64/2017/mar/21 pass: 7,294; fail: 689; error: 21 Build 6: aarch64/2017/mar/25 pass: 7,278; fail: 713; error: 23 Build 7: aarch64/2017/mar/27 pass: 7,304; fail: 690; error: 20 Build 8: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 9: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 10: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 11: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 12: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 13: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 14: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/11 pass: 3,871; error: 2 Build 1: aarch64/2017/mar/13 pass: 3,872; error: 1 Build 2: aarch64/2017/mar/15 pass: 3,874; error: 4 Build 3: aarch64/2017/mar/17 pass: 3,878; error: 2 Build 4: aarch64/2017/mar/19 pass: 3,878; error: 2 Build 5: aarch64/2017/mar/21 pass: 3,876; error: 5 Build 6: aarch64/2017/mar/25 pass: 3,886; fail: 1 Build 7: aarch64/2017/mar/27 pass: 3,883; error: 4 Build 8: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 9: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 10: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 11: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 12: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 13: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 14: aarch64/2017/apr/15 pass: 3,891 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/11 pass: 1,392; fail: 5 Build 1: aarch64/2017/mar/13 pass: 1,392; fail: 5 Build 2: aarch64/2017/mar/15 pass: 1,392; fail: 5 Build 3: aarch64/2017/mar/17 pass: 1,395; fail: 5 Build 4: aarch64/2017/mar/19 pass: 1,395; fail: 5 Build 5: aarch64/2017/mar/21 pass: 1,394; fail: 6 Build 6: aarch64/2017/mar/25 pass: 1,397; fail: 4 Build 7: aarch64/2017/mar/27 pass: 1,396; fail: 5 Build 8: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 9: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 10: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 11: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 12: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 13: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 14: aarch64/2017/apr/15 pass: 1,404; fail: 7 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/11 pass: 7,261; fail: 722; error: 16 Build 1: aarch64/2017/mar/13 pass: 7,290; fail: 687; error: 22 Build 2: aarch64/2017/mar/15 pass: 7,285; fail: 697; error: 19 Build 3: aarch64/2017/mar/17 pass: 7,278; fail: 703; error: 21 Build 4: aarch64/2017/mar/19 pass: 7,261; fail: 723; error: 20 Build 5: aarch64/2017/mar/21 pass: 7,271; fail: 712; error: 21 Build 6: aarch64/2017/mar/25 pass: 7,284; fail: 708; error: 22 Build 7: aarch64/2017/mar/27 pass: 7,297; fail: 695; error: 22 Build 8: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 9: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 10: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 11: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 12: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 13: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 14: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/11 pass: 3,873 Build 1: aarch64/2017/mar/13 pass: 3,871; error: 2 Build 2: aarch64/2017/mar/15 pass: 3,878 Build 3: aarch64/2017/mar/17 pass: 3,876; error: 4 Build 4: aarch64/2017/mar/19 pass: 3,876; error: 4 Build 5: aarch64/2017/mar/21 pass: 3,879; error: 2 Build 6: aarch64/2017/mar/25 pass: 3,885; error: 2 Build 7: aarch64/2017/mar/27 pass: 3,881; error: 6 Build 8: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 9: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 10: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 11: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 12: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 13: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 14: aarch64/2017/apr/15 pass: 3,888; fail: 1; 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.03x Relative performance: Server critical-jOPS (nc): 0.81x 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: 71.29, Server: 120.64 Client 71.29 / Client 2014-04-01 (43.00): 1.66x Server 120.64 / Server 2014-04-01 (71.00): 1.70x 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-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/ 2017-03-26 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/084/results/ 2017-03-28 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/086/results/ 2017-03-31 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/089/results/ 2017-04-02 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/091/results/ 2017-04-04 pass rate: 11550/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/093/results/ 2017-04-08 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/097/results/ 2017-04-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/101/results/ 2017-04-14 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/103/results/ 2017-04-16 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/105/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/ From adinn at redhat.com Tue Apr 18 08:09:57 2017 From: adinn at redhat.com (Andrew Dinn) Date: Tue, 18 Apr 2017 09:09:57 +0100 Subject: [aarch64-port-dev ] jdk8: backport of 8177661: AArch64: Incorrect C2 patterns cause system register corruption In-Reply-To: <817138535.27263009.1492118483571.JavaMail.zimbra@redhat.com> References: <349a8ce3-4377-4c19-fee8-020d7fbc8ee5@redhat.com> <53ac52fa-9c05-77c9-a350-8560613ce986@redhat.com> <1911453721.17127167.1490830012926.JavaMail.zimbra@redhat.com> <45f9c343-459e-5eb2-89e7-835721f8313e@redhat.com> <817138535.27263009.1492118483571.JavaMail.zimbra@redhat.com> Message-ID: <0595d018-bbd4-4ae9-e21f-8071c4cd6932@redhat.com> On 13/04/17 22:21, Andrew Hughes wrote: > ----- Original Message ----- >> On 30/03/17 00:26, Andrew Hughes wrote: >>> There's no need to put it in jdk8u-shenandoah either, as it pulls changes >>> from aarch64/jdk8u anyway. >> >> Mmm, I know that, but on what clock tick are those changes pulled? >> > > At least quarterly with every security update / release. We can do > out-of-band merges as well if required, but nothing is going to languish > there for longer than three months. > > Back to the subject of this bug; are there plans to backport this to 7? > A cursory glance suggests the issue is present there too. Yes, the same issue is present and I believe the same patch will fix it (modulo some line number fuzz). Andrew Hughes, do you want to apply it? now or after the CPU? regards, Andrew Dinn ----------- From aph at redhat.com Tue Apr 18 08:53:46 2017 From: aph at redhat.com (Andrew Haley) Date: Tue, 18 Apr 2017 09:53:46 +0100 Subject: [aarch64-port-dev ] jdk8: backport of 8177661: AArch64: Incorrect C2 patterns cause system register corruption In-Reply-To: <0595d018-bbd4-4ae9-e21f-8071c4cd6932@redhat.com> References: <349a8ce3-4377-4c19-fee8-020d7fbc8ee5@redhat.com> <53ac52fa-9c05-77c9-a350-8560613ce986@redhat.com> <1911453721.17127167.1490830012926.JavaMail.zimbra@redhat.com> <45f9c343-459e-5eb2-89e7-835721f8313e@redhat.com> <817138535.27263009.1492118483571.JavaMail.zimbra@redhat.com> <0595d018-bbd4-4ae9-e21f-8071c4cd6932@redhat.com> Message-ID: <8e96de17-b039-1958-18b7-f15fd4c4e264@redhat.com> On 18/04/17 09:09, Andrew Dinn wrote: > Yes, the same issue is present and I believe the same patch will fix it > (modulo some line number fuzz). We need to construct a list of these. There are probably more than one. Andrew. From ci_notify at linaro.org Tue Apr 18 17:02:21 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Tue, 18 Apr 2017 17:02:21 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <888781096.1076.1492534943631.JavaMail.jenkins@90c74440cc95> 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/107/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/13 pass: 1,388; fail: 5 Build 1: aarch64/2017/mar/15 pass: 1,387; fail: 6 Build 2: aarch64/2017/mar/17 pass: 1,390; fail: 6 Build 3: aarch64/2017/mar/19 pass: 1,391; fail: 5 Build 4: aarch64/2017/mar/21 pass: 1,391; fail: 5 Build 5: aarch64/2017/mar/25 pass: 1,393; fail: 4 Build 6: aarch64/2017/mar/27 pass: 1,393; fail: 4 Build 7: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 8: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 9: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 10: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 11: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 12: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 13: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 14: aarch64/2017/apr/17 pass: 1,400; fail: 7 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/13 pass: 7,268; fail: 710; error: 21 Build 1: aarch64/2017/mar/15 pass: 7,283; fail: 693; error: 25 Build 2: aarch64/2017/mar/17 pass: 7,273; fail: 709; error: 20 Build 3: aarch64/2017/mar/19 pass: 7,253; fail: 727; error: 24 Build 4: aarch64/2017/mar/21 pass: 7,294; fail: 689; error: 21 Build 5: aarch64/2017/mar/25 pass: 7,278; fail: 713; error: 23 Build 6: aarch64/2017/mar/27 pass: 7,304; fail: 690; error: 20 Build 7: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 8: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 9: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 10: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 11: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 12: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 13: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 14: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/13 pass: 3,872; error: 1 Build 1: aarch64/2017/mar/15 pass: 3,874; error: 4 Build 2: aarch64/2017/mar/17 pass: 3,878; error: 2 Build 3: aarch64/2017/mar/19 pass: 3,878; error: 2 Build 4: aarch64/2017/mar/21 pass: 3,876; error: 5 Build 5: aarch64/2017/mar/25 pass: 3,886; fail: 1 Build 6: aarch64/2017/mar/27 pass: 3,883; error: 4 Build 7: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 8: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 9: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 10: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 11: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 12: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 13: aarch64/2017/apr/15 pass: 3,891 Build 14: aarch64/2017/apr/17 pass: 3,891 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/13 pass: 1,392; fail: 5 Build 1: aarch64/2017/mar/15 pass: 1,392; fail: 5 Build 2: aarch64/2017/mar/17 pass: 1,395; fail: 5 Build 3: aarch64/2017/mar/19 pass: 1,395; fail: 5 Build 4: aarch64/2017/mar/21 pass: 1,394; fail: 6 Build 5: aarch64/2017/mar/25 pass: 1,397; fail: 4 Build 6: aarch64/2017/mar/27 pass: 1,396; fail: 5 Build 7: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 8: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 9: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 10: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 11: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 12: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 13: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 14: aarch64/2017/apr/17 pass: 1,404; fail: 7 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/13 pass: 7,290; fail: 687; error: 22 Build 1: aarch64/2017/mar/15 pass: 7,285; fail: 697; error: 19 Build 2: aarch64/2017/mar/17 pass: 7,278; fail: 703; error: 21 Build 3: aarch64/2017/mar/19 pass: 7,261; fail: 723; error: 20 Build 4: aarch64/2017/mar/21 pass: 7,271; fail: 712; error: 21 Build 5: aarch64/2017/mar/25 pass: 7,284; fail: 708; error: 22 Build 6: aarch64/2017/mar/27 pass: 7,297; fail: 695; error: 22 Build 7: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 8: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 9: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 10: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 11: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 12: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 13: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 14: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/13 pass: 3,871; error: 2 Build 1: aarch64/2017/mar/15 pass: 3,878 Build 2: aarch64/2017/mar/17 pass: 3,876; error: 4 Build 3: aarch64/2017/mar/19 pass: 3,876; error: 4 Build 4: aarch64/2017/mar/21 pass: 3,879; error: 2 Build 5: aarch64/2017/mar/25 pass: 3,885; error: 2 Build 6: aarch64/2017/mar/27 pass: 3,881; error: 6 Build 7: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 8: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 9: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 10: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 11: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 12: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 13: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 14: aarch64/2017/apr/17 pass: 3,890; error: 1 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.83x 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.02, Server: 119.62 Client 72.02 / Client 2014-04-01 (43.00): 1.67x Server 119.62 / Server 2014-04-01 (71.00): 1.68x 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-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/ 2017-03-26 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/084/results/ 2017-03-28 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/086/results/ 2017-03-31 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/089/results/ 2017-04-02 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/091/results/ 2017-04-04 pass rate: 11550/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/093/results/ 2017-04-08 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/097/results/ 2017-04-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/101/results/ 2017-04-14 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/103/results/ 2017-04-16 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/105/results/ 2017-04-18 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/107/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/ From gnu.andrew at redhat.com Wed Apr 19 05:46:50 2017 From: gnu.andrew at redhat.com (Andrew Hughes) Date: Wed, 19 Apr 2017 01:46:50 -0400 (EDT) Subject: [aarch64-port-dev ] jdk8: backport of 8177661: AArch64: Incorrect C2 patterns cause system register corruption In-Reply-To: <0595d018-bbd4-4ae9-e21f-8071c4cd6932@redhat.com> References: <349a8ce3-4377-4c19-fee8-020d7fbc8ee5@redhat.com> <53ac52fa-9c05-77c9-a350-8560613ce986@redhat.com> <1911453721.17127167.1490830012926.JavaMail.zimbra@redhat.com> <45f9c343-459e-5eb2-89e7-835721f8313e@redhat.com> <817138535.27263009.1492118483571.JavaMail.zimbra@redhat.com> <0595d018-bbd4-4ae9-e21f-8071c4cd6932@redhat.com> Message-ID: <1019830720.28941739.1492580810257.JavaMail.zimbra@redhat.com> snip... > > Back to the subject of this bug; are there plans to backport this to 7? > > A cursory glance suggests the issue is present there too. > > Yes, the same issue is present and I believe the same patch will fix it > (modulo some line number fuzz). > > Andrew Hughes, do you want to apply it? now or after the CPU? > > regards, > > > Andrew Dinn > ----------- > > Ok, I'll include it with other backports for the CPU. Thanks, -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) Web Site: http://fuseyism.com Twitter: https://twitter.com/gnu_andrew_java PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 From gnu.andrew at redhat.com Wed Apr 19 06:04:41 2017 From: gnu.andrew at redhat.com (Andrew Hughes) Date: Wed, 19 Apr 2017 02:04:41 -0400 (EDT) Subject: [aarch64-port-dev ] [RFR] u131 Update In-Reply-To: <412218983.28942333.1492580914162.JavaMail.zimbra@redhat.com> Message-ID: <573664785.28945174.1492581881397.JavaMail.zimbra@redhat.com> Hi, OpenJDK 8 was recently updated with a security update, u131. Here is the corresponding update for aarch64/jdk8u, aarch64-jdk8u131-b11. We also add an AArch64 port of 8168699 to create aarch64-jdk8u131-b12. http://cr.openjdk.java.net/~andrew/aarch64-8/u131 Ok to push? Changes in aarch64-jdk8u131-b12: - AArch64 support for "8168699: Validate special case invocations" Changes in aarch64-jdk8u131-b11: - S6474807: (smartcardio) CardTerminal.connect() throws CardException instead of CardNotPresentException - S7155957: closed/java/awt/MenuBar/MenuBarStress1/MenuBarStress1.java hangs on win 64 bit with jdk8 - S7167293: FtpURLConnection connection leak on FileNotFoundException - S8035568: [macosx] Cursor management unification - S8079595: Resizing dialog which is JWindow parent makes JVM crash - S8130769: The new menu can't be shown on the menubar after clicking the "Add" button. - S8146602: jdk/test/sun/misc/URLClassPath/ClassnameCharTest.java test fails with NullPointerException - S8147842: IME Composition Window is displayed at incorrect location - S8147910: Cache initial active_processor_count - S8150490: Update OS detection code to recognize Windows Server 2016 - S8160951: [TEST_BUG] javax/xml/bind/marshal/8134111/UnmarshalTest.java should be added into :needs_jre group - S8160958: [TEST_BUG] java/net/SetFactoryPermission/SetFactoryPermission.java should be added into :needs_compact2 group - S8161147: jvm crashes when -XX:+UseCountedLoopSafepoints is enabled - S8161195: Regression: closed/javax/swing/text/FlowView/LayoutTest.java - S8161993: G1 crashes if active_processor_count changes during startup - S8162876: [TEST_BUG] sun/net/www/protocol/http/HttpInputStream.java fails intermittently - S8162916: Test sun/security/krb5/auto/UnboundSSL.java fails - S8163520: Reuse cache entries - S8163528: Better library loading - S8164533: sun/security/ssl/SSLSocketImpl/CloseSocket.java failed with "Error while cleaning up threads after test" - S8165626: Improved window framing - S8167110: Windows peering issue - S8167179: Make XSL generated namespace prefixes local to transformation process - S8168699: Validate special case invocations - S8168774: Polymorhic signature method check crashes javac - S8169011: Resizing XML parse trees - S8169465: Deadlock in com.sun.jndi.ldap.pool.Connections - S8169589: [macosx] Activating a JDialog puts to back another dialog - S8170222: Better transfers of files - S8170307: Stack size option -Xss is ignored - S8170316: (tz) Support tzdata2016j - S8170814: Reuse cache entries (part II) - S8170888: [linux] Experimental support for cgroup memory limits in container (ie Docker) environments - S8171121: Enhancing jar checking - S8171388: Update JNDI Thread contexts - S8171533: Better email transfer - S8171949: [macosx] AWT_ZoomFrame Automated tests fail with error: The bitwise mask Frame.ICONIFIED is not setwhen the frame is in ICONIFIED state - S8171952: [macosx] AWT_Modality/Automated/ModalExclusion/NoExclusion/ModelessDialog test fails as DummyButton on Dialog did not gain focus when clicked. - S8172299: Improve class processing - S8173783: IllegalArgumentException: jdk.tls.namedGroups - S8173931: 8u131 L10n resource file update - S8174844: Incorrect GPL header causes RE script to miss swap to commercial header for licensee source bundle - S8174985: NTLM authentication doesn't work with IIS if NTLM cache is disabled - S8176044: (tz) Support tzdata2017a -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) Web Site: http://fuseyism.com Twitter: https://twitter.com/gnu_andrew_java PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 From aph at redhat.com Wed Apr 19 11:30:14 2017 From: aph at redhat.com (Andrew Haley) Date: Wed, 19 Apr 2017 12:30:14 +0100 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: Message-ID: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> Looking at this some more, I can't tell which benchmarks are throughput (big is good) and which are time (small is good). This makes it very hard for me to see where community AArch64 is lagging performance. I think Dacapo is throughput? And TeraSort is time? The results for Partner B's hardware on Dacapo are so weird that I think there must be something wrong. lusearch didn't work at all, so there must be a code generation problem somewhere. SPECjvm I understand, it's well-designed and stable, and I'm quite satisfied with the results there. With regard to the default size of the code cache, I think that's a hangover from the time whan we hadn't solved the problem of generating far calls, and I'm considering changing it to be the same as other architectures. The problem with switching, though, is that while it won't make any significant difference to throughput it will increase code size, but I can see that it makes sense that we dont run out of code cache before other architectures do. Andrew. From aph at redhat.com Wed Apr 19 11:44:49 2017 From: aph at redhat.com (Andrew Haley) Date: Wed, 19 Apr 2017 12:44:49 +0100 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> References: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> Message-ID: <703449d3-038c-d46c-1e20-b39397ad3a60@redhat.com> On 19/04/17 12:30, Andrew Haley wrote: > The results for Partner B's hardware on Dacapo are so weird that I > think there must be something wrong. lusearch didn't work at all, so > there must be a code generation problem somewhere. ... in addition, the score for sunflow on Partner B openjdk-arm64 looks deeply suspect. It has a relative score of 37.88% and a standard deviation of zero. These results are so strange, and so difficult for me to verify, that I'm going to have to ignore them until I can get suitable hardware. Andrew. From aph at redhat.com Wed Apr 19 11:47:45 2017 From: aph at redhat.com (Andrew Haley) Date: Wed, 19 Apr 2017 12:47:45 +0100 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> References: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> Message-ID: <01f26378-9579-0469-8c03-ef0a71758d6e@redhat.com> On 19/04/17 12:30, Andrew Haley wrote: > I think Dacapo is throughput? And TeraSort is time? My apologies: I had downloaded the spreadsheets, and OpenOffice wasn't showing me the (less is better). Andrew. From aph at redhat.com Wed Apr 19 16:13:08 2017 From: aph at redhat.com (Andrew Haley) Date: Wed, 19 Apr 2017 17:13:08 +0100 Subject: [aarch64-port-dev ] [RFR] u131 Update In-Reply-To: <573664785.28945174.1492581881397.JavaMail.zimbra@redhat.com> References: <573664785.28945174.1492581881397.JavaMail.zimbra@redhat.com> Message-ID: On 19/04/17 07:04, Andrew Hughes wrote: > We also add an AArch64 port of 8168699 to create aarch64-jdk8u131-b12. > > http://cr.openjdk.java.net/~andrew/aarch64-8/u131 > > Ok to push? OK, thanks. Andrew. From gnu.andrew at redhat.com Wed Apr 19 16:20:18 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:20:18 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u: 3 new changesets Message-ID: <201704191620.v3JGKIYP020138@aojmv0008.oracle.com> Changeset: f440db50782f Author: andrew Date: 2017-04-12 08:31 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/rev/f440db50782f Added tag aarch64-jdk8u121-b15 for changeset 0ea0e60bbbfa ! .hgtags Changeset: 8e5c7286cd85 Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/rev/8e5c7286cd85 Added tag aarch64-jdk8u131-b11 for changeset f440db50782f ! .hgtags Changeset: 950ef0ca8ebf Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/rev/950ef0ca8ebf Added tag aarch64-jdk8u131-b12 for changeset 8e5c7286cd85 ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:20:26 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:20:26 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/corba: 3 new changesets Message-ID: <201704191620.v3JGKQbX020289@aojmv0008.oracle.com> Changeset: 9c8194ce0391 Author: andrew Date: 2017-04-12 08:31 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/corba/rev/9c8194ce0391 Added tag aarch64-jdk8u121-b15 for changeset d219158e0758 ! .hgtags Changeset: 7ab076b30e78 Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/corba/rev/7ab076b30e78 Added tag aarch64-jdk8u131-b11 for changeset 9c8194ce0391 ! .hgtags Changeset: c49173b21d2c Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/corba/rev/c49173b21d2c Added tag aarch64-jdk8u131-b12 for changeset 7ab076b30e78 ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:20:33 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:20:33 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/jaxp: 6 new changesets Message-ID: <201704191620.v3JGKXNk020353@aojmv0008.oracle.com> Changeset: 45decba838b4 Author: andrew Date: 2017-04-12 08:31 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jaxp/rev/45decba838b4 Added tag aarch64-jdk8u121-b15 for changeset 6658da128353 ! .hgtags Changeset: ec0d38ff9678 Author: aefimov Date: 2016-10-24 17:02 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jaxp/rev/ec0d38ff9678 8167179: Make XSL generated namespace prefixes local to transformation process Reviewed-by: joehw ! src/com/sun/org/apache/xalan/internal/xsltc/compiler/Stylesheet.java ! src/com/sun/org/apache/xalan/internal/xsltc/runtime/BasisLibrary.java Changeset: fe5081adbba2 Author: aefimov Date: 2017-01-20 14:50 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jaxp/rev/fe5081adbba2 8169011: Resizing XML parse trees Reviewed-by: joehw ! src/com/sun/org/apache/xerces/internal/impl/XML11NSDocumentScannerImpl.java ! src/com/sun/org/apache/xerces/internal/impl/XMLDTDScannerImpl.java ! src/com/sun/org/apache/xerces/internal/impl/XMLNSDocumentScannerImpl.java ! src/com/sun/org/apache/xerces/internal/impl/XMLStreamReaderImpl.java Changeset: f0e90978da55 Author: asaha Date: 2017-02-04 01:21 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jaxp/rev/f0e90978da55 8173931: 8u131 L10n resource file update Reviewed-by: coffeys Contributed-by: li.jiang at oracle.com ! src/com/sun/org/apache/xalan/internal/res/XSLTErrorResources_it.java ! src/com/sun/org/apache/xerces/internal/impl/msg/XMLSchemaMessages_it.properties ! src/com/sun/org/apache/xerces/internal/impl/msg/XPointerMessages_it.properties Changeset: 87da19c7cc5f Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jaxp/rev/87da19c7cc5f Added tag aarch64-jdk8u131-b11 for changeset f0e90978da55 ! .hgtags Changeset: 60afaf2daa82 Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jaxp/rev/60afaf2daa82 Added tag aarch64-jdk8u131-b12 for changeset 87da19c7cc5f ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:20:39 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:20:39 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/jaxws: 3 new changesets Message-ID: <201704191620.v3JGKdX0020414@aojmv0008.oracle.com> Changeset: 9e9a88d5e2cd Author: andrew Date: 2017-04-12 08:32 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jaxws/rev/9e9a88d5e2cd Added tag aarch64-jdk8u121-b15 for changeset 3c9b35d71d99 ! .hgtags Changeset: 2b6e5bb5844a Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jaxws/rev/2b6e5bb5844a Added tag aarch64-jdk8u131-b11 for changeset 9e9a88d5e2cd ! .hgtags Changeset: 6b798680f1b0 Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jaxws/rev/6b798680f1b0 Added tag aarch64-jdk8u131-b12 for changeset 2b6e5bb5844a ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:20:47 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:20:47 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/langtools: 4 new changesets Message-ID: <201704191620.v3JGKlcO020472@aojmv0008.oracle.com> Changeset: 957a3f295558 Author: andrew Date: 2017-04-12 08:32 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/langtools/rev/957a3f295558 Added tag aarch64-jdk8u121-b15 for changeset 06ec76842b04 ! .hgtags Changeset: 8a78ce0ebb3c Author: mcimadamore Date: 2017-01-05 18:58 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/langtools/rev/8a78ce0ebb3c 8168774: Polymorhic signature method check crashes javac Summary: Check for polysig method assumes arity is greater than zero Reviewed-by: vromero ! src/share/classes/com/sun/tools/javac/code/Types.java + test/tools/javac/meth/BadPolySig.java Changeset: 919a3c6bc315 Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/langtools/rev/919a3c6bc315 Added tag aarch64-jdk8u131-b11 for changeset 8a78ce0ebb3c ! .hgtags Changeset: 8ef3f0de2bc2 Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/langtools/rev/8ef3f0de2bc2 Added tag aarch64-jdk8u131-b12 for changeset 919a3c6bc315 ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:20:54 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:20:54 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/hotspot: 11 new changesets Message-ID: <201704191620.v3JGKs4V020561@aojmv0008.oracle.com> Changeset: 0fe0c692f4e9 Author: andrew Date: 2017-04-12 08:32 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/0fe0c692f4e9 Added tag aarch64-jdk8u121-b15 for changeset e5d7f637919f ! .hgtags Changeset: e68ad2c10623 Author: tschatzl Date: 2016-12-15 19:48 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/e68ad2c10623 8147910: Cache initial active_processor_count Summary: Introduce and initialize active_processor_count variable in VM. Reviewed-by: dholmes, jprovino ! src/share/vm/runtime/os.cpp ! src/share/vm/runtime/os.hpp Changeset: d11a5c24bdb2 Author: msolovie Date: 2016-12-09 19:40 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/d11a5c24bdb2 8150490: Update OS detection code to recognize Windows Server 2016 Reviewed-by: mgronlun, alanb, dholmes ! src/os/windows/vm/os_windows.cpp Changeset: 21eefd0c7215 Author: roland Date: 2016-07-25 14:31 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/21eefd0c7215 8161147: jvm crashes when -XX:+UseCountedLoopSafepoints is enabled Summary: don't convert loop with safepoint on the backedge to Counted loop Reviewed-by: kvn ! src/share/vm/opto/loopnode.cpp + test/compiler/loopopts/TestCountedLoopSafepointBackedge.java Changeset: 2e0b9dc9b8ba Author: tschatzl Date: 2016-12-15 20:00 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/2e0b9dc9b8ba 8161993: G1 crashes if active_processor_count changes during startup Summary: Use the initial active processor count for memory initialization instead of the current active one. Reviewed-by: dholmes, mgerdin ! src/share/vm/gc_implementation/g1/concurrentMark.cpp ! src/share/vm/gc_implementation/g1/dirtyCardQueue.cpp ! src/share/vm/runtime/vm_version.cpp Changeset: 4eb424fb499f Author: coleenp Date: 2016-12-13 14:37 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/4eb424fb499f 8168699: Validate special case invocations Reviewed-by: kevinw, vlivanov ! src/cpu/sparc/vm/c1_LIRGenerator_sparc.cpp ! src/cpu/x86/vm/c1_LIRGenerator_x86.cpp ! src/share/vm/c1/c1_CodeStubs.hpp ! src/share/vm/c1/c1_GraphBuilder.cpp ! src/share/vm/c1/c1_Instruction.hpp ! src/share/vm/ci/ciInstanceKlass.cpp ! src/share/vm/ci/ciInstanceKlass.hpp ! src/share/vm/ci/ciMethod.cpp ! src/share/vm/ci/ciMethod.hpp ! src/share/vm/interpreter/interpreterRuntime.cpp ! src/share/vm/interpreter/linkResolver.cpp ! src/share/vm/interpreter/linkResolver.hpp ! src/share/vm/oops/cpCache.cpp ! src/share/vm/oops/cpCache.hpp ! src/share/vm/opto/doCall.cpp ! src/share/vm/prims/methodHandles.cpp ! src/share/vm/runtime/javaCalls.cpp Changeset: 44f283fb5180 Author: dholmes Date: 2016-12-20 16:06 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/44f283fb5180 8170307: Stack size option -Xss is ignored Reviewed-by: dcubed, sspitsyn, gtriantafill ! src/os/linux/vm/os_linux.cpp Changeset: 71cf0e117575 Author: dholmes Date: 2017-01-05 18:55 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/71cf0e117575 8170888: [linux] Experimental support for cgroup memory limits in container (ie Docker) environments Summary: Set apparent physical memory to cgroup memory limit when UseCGroupMemoryLimitForHeap is true Reviewed-by: acorn, gtriantafill Contributed-by: Christine Flood ! src/share/vm/runtime/arguments.cpp ! src/share/vm/runtime/globals.hpp Changeset: 36dc9bbfa5f8 Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/36dc9bbfa5f8 Added tag aarch64-jdk8u131-b11 for changeset 71cf0e117575 ! .hgtags Changeset: f4086f3a0d69 Author: aph Date: 2017-04-18 13:07 -0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/f4086f3a0d69 AArch64 support for "8168699: Validate special case invocations" ! src/cpu/aarch64/vm/c1_LIRGenerator_aarch64.cpp Changeset: a3b619b8e2b6 Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/a3b619b8e2b6 Added tag aarch64-jdk8u131-b12 for changeset f4086f3a0d69 ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:21:06 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:21:06 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/jdk: 35 new changesets Message-ID: <201704191621.v3JGL7EA020624@aojmv0008.oracle.com> Changeset: 4987b365f035 Author: andrew Date: 2017-04-12 08:32 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/4987b365f035 Added tag aarch64-jdk8u121-b15 for changeset 86b9391b28d7 ! .hgtags Changeset: f7afebfedc72 Author: igerasim Date: 2016-08-31 11:19 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/f7afebfedc72 6474807: (smartcardio) CardTerminal.connect() throws CardException instead of CardNotPresentException Reviewed-by: valeriep ! src/share/classes/sun/security/smartcardio/TerminalImpl.java Changeset: 2e9439f06256 Author: mcherkas Date: 2017-01-24 22:39 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/2e9439f06256 8167110: Windows peering issue 7155957: closed/java/awt/MenuBar/MenuBarStress1/MenuBarStress1.java hangs on win 64 bit with jdk8 8079595: Resizing dialog which is JWindow parent makes JVM crash 8147842: IME Composition Window is displayed at incorrect location Reviewed-by: serb ! src/share/classes/java/awt/Menu.java ! src/share/classes/java/awt/MenuBar.java ! src/share/classes/java/awt/MenuComponent.java ! src/windows/classes/sun/awt/windows/WMenuItemPeer.java ! src/windows/classes/sun/awt/windows/WObjectPeer.java ! src/windows/native/sun/windows/awt_Component.cpp ! src/windows/native/sun/windows/awt_Menu.cpp ! src/windows/native/sun/windows/awt_Menu.h ! src/windows/native/sun/windows/awt_MenuBar.cpp ! src/windows/native/sun/windows/awt_MenuBar.h ! src/windows/native/sun/windows/awt_MenuItem.cpp ! src/windows/native/sun/windows/awt_MenuItem.h ! src/windows/native/sun/windows/awt_PopupMenu.cpp ! src/windows/native/sun/windows/awt_PopupMenu.h ! src/windows/native/sun/windows/awt_new.cpp Changeset: 50e3a607d99d Author: vtewari Date: 2016-04-05 17:07 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/50e3a607d99d 7167293: FtpURLConnection connection leak on FileNotFoundException Reviewed-by: chegar, rriggs ! src/share/classes/sun/net/www/protocol/ftp/FtpURLConnection.java Changeset: f745f7bab4c9 Author: pchelko Date: 2016-12-09 10:01 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/f745f7bab4c9 8035568: [macosx] Cursor management unification Reviewed-by: anthony, serb ! src/macosx/classes/sun/lwawt/LWMouseInfoPeer.java ! src/macosx/classes/sun/lwawt/LWToolkit.java ! src/macosx/classes/sun/lwawt/LWWindowPeer.java ! src/macosx/classes/sun/lwawt/PlatformWindow.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformEmbeddedFrame.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformLWWindow.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformWindow.java ! src/macosx/classes/sun/lwawt/macosx/CRobot.java ! src/macosx/classes/sun/lwawt/macosx/CViewPlatformEmbeddedFrame.java ! src/macosx/classes/sun/lwawt/macosx/LWCToolkit.java ! src/macosx/native/sun/awt/AWTWindow.m ! src/macosx/native/sun/awt/CCursorManager.m ! src/macosx/native/sun/awt/CRobot.m + test/java/awt/MouseInfo/GetPointerInfoTest.java + test/java/awt/MouseInfo/MultiscreenPointerInfo.java Changeset: 330ba74dfe49 Author: mcherkas Date: 2017-01-25 18:16 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/330ba74dfe49 8130769: The new menu can't be shown on the menubar after clicking the "Add" button. Reviewed-by: serb ! src/share/classes/java/awt/MenuBar.java Changeset: 6ede986bc351 Author: snikandrova Date: 2016-08-18 16:27 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/6ede986bc351 8146602: jdk/test/sun/misc/URLClassPath/ClassnameCharTest.java test fails with NullPointerException Reviewed-by: dfuchs, clanger ! test/sun/misc/URLClassPath/ClassnameCharTest.java Changeset: 91482fd579b0 Author: msolovie Date: 2016-12-09 19:34 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/91482fd579b0 8150490: Update OS detection code to recognize Windows Server 2016 Reviewed-by: mgronlun, alanb, dholmes ! src/windows/native/java/lang/java_props_md.c Changeset: e3babd92a65d Author: rpatil Date: 2016-09-10 22:54 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/e3babd92a65d 8160951: [TEST_BUG] javax/xml/bind/marshal/8134111/UnmarshalTest.java should be added into :needs_jre group 8160958: [TEST_BUG] java/net/SetFactoryPermission/SetFactoryPermission.java should be added into :needs_compact2 group Reviewed-by: igerasim ! test/TEST.groups Changeset: fe8d78a0f02a Author: mcherkas Date: 2017-01-26 17:26 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/fe8d78a0f02a 8161195: Regression: closed/javax/swing/text/FlowView/LayoutTest.java Reviewed-by: serb ! src/windows/native/sun/windows/awt_Component.cpp Changeset: f93d25469e44 Author: snikandrova Date: 2016-08-08 20:16 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/f93d25469e44 8162876: [TEST_BUG] sun/net/www/protocol/http/HttpInputStream.java fails intermittently Reviewed-by: chegar ! test/sun/net/www/protocol/http/HttpInputStream.java Changeset: 522d7ee4e17f Author: coffeys Date: 2016-08-19 07:42 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/522d7ee4e17f 8162916: Test sun/security/krb5/auto/UnboundSSL.java fails Reviewed-by: weijun, asmotrak ! test/sun/security/krb5/auto/UnboundSSL.java Changeset: 8003c75a1396 Author: dfuchs Date: 2016-12-09 18:18 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/8003c75a1396 8163520: Reuse cache entries Reviewed-by: chegar, aefimov ! src/share/classes/sun/net/www/http/HttpClient.java ! src/share/classes/sun/net/www/protocol/http/AuthenticationInfo.java ! src/solaris/classes/sun/net/www/protocol/http/ntlm/NTLMAuthentication.java ! src/windows/classes/sun/net/www/protocol/http/ntlm/NTLMAuthentication.java Changeset: a3720aa79c07 Author: valeriep Date: 2016-11-23 19:46 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/a3720aa79c07 8163528: Better library loading Reviewed-by: mullan Contributed-by: florian at bogner.sh ! src/share/classes/sun/misc/Launcher.java Changeset: 248b9dfd9559 Author: snikandrova Date: 2016-08-29 20:55 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/248b9dfd9559 8164533: sun/security/ssl/SSLSocketImpl/CloseSocket.java failed with "Error while cleaning up threads after test" Reviewed-by: xuelei ! test/sun/security/ssl/com/sun/net/ssl/internal/ssl/SSLSocketImpl/CloseSocket.java Changeset: 8f411e15b753 Author: mcherkas Date: 2016-11-11 16:55 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/8f411e15b753 8165626: Improved window framing Reviewed-by: serb ! src/macosx/classes/com/apple/eawt/_AppDockIconHandler.java ! src/macosx/classes/sun/java2d/opengl/CGLLayer.java ! src/macosx/classes/sun/lwawt/macosx/CFRetainedResource.java ! src/macosx/classes/sun/lwawt/macosx/CImage.java ! src/macosx/classes/sun/lwawt/macosx/CMenuItem.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformComponent.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformLWWindow.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformView.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformWindow.java ! src/macosx/classes/sun/lwawt/macosx/CTrayIcon.java ! src/macosx/classes/sun/lwawt/macosx/CViewPlatformEmbeddedFrame.java ! src/macosx/classes/sun/lwawt/macosx/CWarningWindow.java ! src/macosx/native/sun/awt/AWTSurfaceLayers.h ! src/macosx/native/sun/awt/AWTSurfaceLayers.m Changeset: 0e0a752e3809 Author: aefimov Date: 2016-10-24 17:02 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/0e0a752e3809 8167179: Make XSL generated namespace prefixes local to transformation process Reviewed-by: joehw + test/javax/xml/jaxp/transform/8167179/NamespacePrefixTest.java Changeset: 23c5c7127222 Author: robm Date: 2017-01-09 18:33 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/23c5c7127222 8169465: Deadlock in com.sun.jndi.ldap.pool.Connections Reviewed-by: dfuchs, vtewari ! src/share/classes/com/sun/jndi/ldap/pool/Connections.java ! src/share/classes/com/sun/jndi/ldap/pool/Pool.java Changeset: ad51ad05aecc Author: dmarkov Date: 2017-01-19 22:45 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/ad51ad05aecc 8169589: [macosx] Activating a JDialog puts to back another dialog Reviewed-by: anthony, serb ! src/macosx/classes/sun/lwawt/macosx/CPlatformWindow.java ! src/share/classes/java/awt/Window.java ! src/share/classes/sun/awt/AWTAccessor.java Changeset: d86ed639df42 Author: rpatil Date: 2017-02-25 09:50 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/d86ed639df42 8170222: Better transfers of files Reviewed-by: dfuchs, chegar, vtewari ! src/share/classes/sun/net/ftp/impl/FtpClient.java Changeset: e89ee7075633 Author: rpatil Date: 2016-12-12 17:30 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/e89ee7075633 8170316: (tz) Support tzdata2016j Reviewed-by: martin, okutsu ! make/data/tzdata/VERSION ! make/data/tzdata/africa ! make/data/tzdata/asia ! make/data/tzdata/europe ! make/data/tzdata/iso3166.tab ! make/data/tzdata/zone.tab ! test/sun/util/calendar/zi/tzdata/VERSION ! test/sun/util/calendar/zi/tzdata/africa ! test/sun/util/calendar/zi/tzdata/asia ! test/sun/util/calendar/zi/tzdata/europe ! test/sun/util/calendar/zi/tzdata/iso3166.tab ! test/sun/util/calendar/zi/tzdata/zone.tab Changeset: 26cda931a436 Author: aefimov Date: 2017-01-17 15:35 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/26cda931a436 8170814: Reuse cache entries (part II) Reviewed-by: dfuchs ! src/share/classes/sun/net/www/http/HttpClient.java ! src/share/classes/sun/net/www/protocol/http/NegotiateAuthentication.java Changeset: 0ad54e1d1ef5 Author: rpatil Date: 2016-12-26 16:00 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/0ad54e1d1ef5 8171121: Enhancing jar checking Reviewed-by: ascarpino ! src/share/lib/security/java.security-aix ! src/share/lib/security/java.security-linux ! src/share/lib/security/java.security-macosx ! src/share/lib/security/java.security-solaris ! src/share/lib/security/java.security-windows ! test/sun/security/tools/jarsigner/TimestampCheck.java Changeset: f2e5534d1e70 Author: robm Date: 2016-12-16 20:39 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/f2e5534d1e70 8171388: Update JNDI Thread contexts Reviewed-by: chegar ! src/share/classes/java/lang/Thread.java Changeset: 3ad5f8977692 Author: rpatil Date: 2017-02-27 19:19 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/3ad5f8977692 8171533: Better email transfer Reviewed-by: dfuchs, chegar, vtewari ! src/share/classes/sun/net/smtp/SmtpClient.java Changeset: b6c62eddc86c Author: dmarkov Date: 2017-01-19 22:47 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/b6c62eddc86c 8171949: [macosx] AWT_ZoomFrame Automated tests fail with error: The bitwise mask Frame.ICONIFIED is not setwhen the frame is in ICONIFIED state Reviewed-by: ssadetsky, serb ! src/macosx/classes/sun/lwawt/macosx/CPlatformWindow.java ! src/macosx/native/sun/awt/AWTWindow.m Changeset: f3b312f1ce87 Author: dmarkov Date: 2017-01-02 17:15 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/f3b312f1ce87 8171952: [macosx] AWT_Modality/Automated/ModalExclusion/NoExclusion/ModelessDialog test fails as DummyButton on Dialog did not gain focus when clicked. Reviewed-by: ssadetsky, serb ! src/macosx/native/sun/awt/AWTWindow.m + test/java/awt/Frame/ObscuredFrame/ObscuredFrameTest.java Changeset: 094fd7d891b6 Author: robm Date: 2017-02-09 16:34 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/094fd7d891b6 8172299: Improve class processing Reviewed-by: rriggs ! src/share/classes/java/io/ObjectInputStream.java Changeset: fdfb9f6f399b Author: coffeys Date: 2017-02-08 12:10 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/fdfb9f6f399b 8173783: IllegalArgumentException: jdk.tls.namedGroups Reviewed-by: xuelei, wetmore ! src/share/classes/sun/security/ssl/SupportedEllipticCurvesExtension.java + test/sun/security/ssl/ServerHandshaker/HelloExtensionsTest.java Changeset: e940b178ce4f Author: asaha Date: 2017-02-04 01:22 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/e940b178ce4f 8173931: 8u131 L10n resource file update Reviewed-by: coffeys Contributed-by: li.jiang at oracle.com ! src/macosx/classes/com/apple/laf/resources/aqua_de.properties ! src/share/classes/com/sun/java/swing/plaf/windows/resources/windows_ko.properties ! src/share/classes/com/sun/rowset/RowSetResourceBundle_sv.properties ! src/share/classes/com/sun/swing/internal/plaf/metal/resources/metal_ko.properties ! src/share/classes/com/sun/swing/internal/plaf/synth/resources/synth_ko.properties ! src/share/classes/sun/security/tools/jarsigner/Resources_ja.java ! src/share/classes/sun/security/tools/jarsigner/Resources_zh_CN.java ! src/share/classes/sun/security/tools/policytool/Resources_sv.java ! src/share/classes/sun/tools/jar/resources/jar_sv.properties Changeset: 968ff27bac31 Author: robm Date: 2017-02-27 17:43 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/968ff27bac31 8174844: Incorrect GPL header causes RE script to miss swap to commercial header for licensee source bundle Reviewed-by: coffeys ! src/share/classes/sun/security/util/AbstractAlgorithmConstraints.java Changeset: 75bc4c5db073 Author: aefimov Date: 2017-02-28 14:44 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/75bc4c5db073 8174985: NTLM authentication doesn't work with IIS if NTLM cache is disabled Reviewed-by: dfuchs ! src/share/classes/sun/net/www/http/HttpClient.java Changeset: 05e10ee4afec Author: rpatil Date: 2017-03-10 12:50 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/05e10ee4afec 8176044: (tz) Support tzdata2017a Reviewed-by: naoto ! make/data/tzdata/VERSION ! make/data/tzdata/africa ! make/data/tzdata/antarctica ! make/data/tzdata/asia ! make/data/tzdata/australasia ! make/data/tzdata/backward ! make/data/tzdata/europe ! make/data/tzdata/leapseconds ! make/data/tzdata/northamerica ! make/data/tzdata/southamerica ! make/data/tzdata/zone.tab ! test/sun/util/calendar/zi/tzdata/VERSION ! test/sun/util/calendar/zi/tzdata/africa ! test/sun/util/calendar/zi/tzdata/antarctica ! test/sun/util/calendar/zi/tzdata/asia ! test/sun/util/calendar/zi/tzdata/australasia ! test/sun/util/calendar/zi/tzdata/backward ! test/sun/util/calendar/zi/tzdata/europe ! test/sun/util/calendar/zi/tzdata/leapseconds ! test/sun/util/calendar/zi/tzdata/northamerica ! test/sun/util/calendar/zi/tzdata/southamerica ! test/sun/util/calendar/zi/tzdata/zone.tab Changeset: 9ae547861e9f Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/9ae547861e9f Added tag aarch64-jdk8u131-b11 for changeset 05e10ee4afec ! .hgtags Changeset: 968945f351b7 Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/jdk/rev/968945f351b7 Added tag aarch64-jdk8u131-b12 for changeset 9ae547861e9f ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:21:14 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:21:14 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/nashorn: 3 new changesets Message-ID: <201704191621.v3JGLErO020702@aojmv0008.oracle.com> Changeset: 13ad0227abae Author: andrew Date: 2017-04-12 08:32 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/nashorn/rev/13ad0227abae Added tag aarch64-jdk8u121-b15 for changeset e42e6f6a6aae ! .hgtags Changeset: 9c1264a75e80 Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/nashorn/rev/9c1264a75e80 Added tag aarch64-jdk8u131-b11 for changeset 13ad0227abae ! .hgtags Changeset: 2c46c952e68f Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/nashorn/rev/2c46c952e68f Added tag aarch64-jdk8u131-b12 for changeset 9c1264a75e80 ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:47:24 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:47:24 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah: 7 new changesets Message-ID: <201704191647.v3JGlOBD000570@aojmv0008.oracle.com> Changeset: f440db50782f Author: andrew Date: 2017-04-12 08:31 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/f440db50782f Added tag aarch64-jdk8u121-b15 for changeset 0ea0e60bbbfa ! .hgtags Changeset: 8e5c7286cd85 Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/8e5c7286cd85 Added tag aarch64-jdk8u131-b11 for changeset f440db50782f ! .hgtags Changeset: 7245cfe40f39 Author: andrew Date: 2017-04-13 05:55 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/7245cfe40f39 Merge aarch64-jdk8u131-b11 ! .hgtags Changeset: 4a851d2277a3 Author: andrew Date: 2017-04-13 05:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/4a851d2277a3 Added tag aarch64-shenandoah-jdk8u131-b11 for changeset 7245cfe40f39 ! .hgtags Changeset: 950ef0ca8ebf Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/950ef0ca8ebf Added tag aarch64-jdk8u131-b12 for changeset 8e5c7286cd85 ! .hgtags Changeset: b71759188fca Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/b71759188fca Merge aarch64-jdk8u131-b12 ! .hgtags Changeset: 7e7905cd2090 Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/7e7905cd2090 Added tag aarch64-shenandoah-jdk8u131-b12 for changeset b71759188fca ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:47:30 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:47:30 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/corba: 7 new changesets Message-ID: <201704191647.v3JGlUla000712@aojmv0008.oracle.com> Changeset: 9c8194ce0391 Author: andrew Date: 2017-04-12 08:31 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/9c8194ce0391 Added tag aarch64-jdk8u121-b15 for changeset d219158e0758 ! .hgtags Changeset: 7ab076b30e78 Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/7ab076b30e78 Added tag aarch64-jdk8u131-b11 for changeset 9c8194ce0391 ! .hgtags Changeset: 36113c8586c7 Author: andrew Date: 2017-04-13 05:54 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/36113c8586c7 Merge aarch64-jdk8u131-b11 ! .hgtags Changeset: d354de0ce002 Author: andrew Date: 2017-04-13 05:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/d354de0ce002 Added tag aarch64-shenandoah-jdk8u131-b11 for changeset 36113c8586c7 ! .hgtags Changeset: c49173b21d2c Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/c49173b21d2c Added tag aarch64-jdk8u131-b12 for changeset 7ab076b30e78 ! .hgtags Changeset: 10531a5190ee Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/10531a5190ee Merge aarch64-jdk8u131-b12 ! .hgtags Changeset: fd5ad2b93775 Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/fd5ad2b93775 Added tag aarch64-shenandoah-jdk8u131-b12 for changeset 10531a5190ee ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:47:36 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:47:36 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxp: 10 new changesets Message-ID: <201704191647.v3JGlbA1001005@aojmv0008.oracle.com> Changeset: 45decba838b4 Author: andrew Date: 2017-04-12 08:31 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/45decba838b4 Added tag aarch64-jdk8u121-b15 for changeset 6658da128353 ! .hgtags Changeset: ec0d38ff9678 Author: aefimov Date: 2016-10-24 17:02 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/ec0d38ff9678 8167179: Make XSL generated namespace prefixes local to transformation process Reviewed-by: joehw ! src/com/sun/org/apache/xalan/internal/xsltc/compiler/Stylesheet.java ! src/com/sun/org/apache/xalan/internal/xsltc/runtime/BasisLibrary.java Changeset: fe5081adbba2 Author: aefimov Date: 2017-01-20 14:50 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/fe5081adbba2 8169011: Resizing XML parse trees Reviewed-by: joehw ! src/com/sun/org/apache/xerces/internal/impl/XML11NSDocumentScannerImpl.java ! src/com/sun/org/apache/xerces/internal/impl/XMLDTDScannerImpl.java ! src/com/sun/org/apache/xerces/internal/impl/XMLNSDocumentScannerImpl.java ! src/com/sun/org/apache/xerces/internal/impl/XMLStreamReaderImpl.java Changeset: f0e90978da55 Author: asaha Date: 2017-02-04 01:21 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/f0e90978da55 8173931: 8u131 L10n resource file update Reviewed-by: coffeys Contributed-by: li.jiang at oracle.com ! src/com/sun/org/apache/xalan/internal/res/XSLTErrorResources_it.java ! src/com/sun/org/apache/xerces/internal/impl/msg/XMLSchemaMessages_it.properties ! src/com/sun/org/apache/xerces/internal/impl/msg/XPointerMessages_it.properties Changeset: 87da19c7cc5f Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/87da19c7cc5f Added tag aarch64-jdk8u131-b11 for changeset f0e90978da55 ! .hgtags Changeset: 17f5d6d4d8c7 Author: andrew Date: 2017-04-13 05:54 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/17f5d6d4d8c7 Merge aarch64-jdk8u131-b11 ! .hgtags Changeset: 27db192f4f98 Author: andrew Date: 2017-04-13 05:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/27db192f4f98 Added tag aarch64-shenandoah-jdk8u131-b11 for changeset 17f5d6d4d8c7 ! .hgtags Changeset: 60afaf2daa82 Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/60afaf2daa82 Added tag aarch64-jdk8u131-b12 for changeset 87da19c7cc5f ! .hgtags Changeset: 1f02abbca31d Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/1f02abbca31d Merge aarch64-jdk8u131-b12 ! .hgtags Changeset: b1f21ba8f2ad Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/b1f21ba8f2ad Added tag aarch64-shenandoah-jdk8u131-b12 for changeset 1f02abbca31d ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:47:43 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:47:43 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxws: 7 new changesets Message-ID: <201704191647.v3JGlhaM001086@aojmv0008.oracle.com> Changeset: 9e9a88d5e2cd Author: andrew Date: 2017-04-12 08:32 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/9e9a88d5e2cd Added tag aarch64-jdk8u121-b15 for changeset 3c9b35d71d99 ! .hgtags Changeset: 2b6e5bb5844a Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/2b6e5bb5844a Added tag aarch64-jdk8u131-b11 for changeset 9e9a88d5e2cd ! .hgtags Changeset: 7853fae4dfe8 Author: andrew Date: 2017-04-13 05:54 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/7853fae4dfe8 Merge aarch64-jdk8u131-b11 ! .hgtags Changeset: 6851340b8fa8 Author: andrew Date: 2017-04-13 05:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/6851340b8fa8 Added tag aarch64-shenandoah-jdk8u131-b11 for changeset 7853fae4dfe8 ! .hgtags Changeset: 6b798680f1b0 Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/6b798680f1b0 Added tag aarch64-jdk8u131-b12 for changeset 2b6e5bb5844a ! .hgtags Changeset: e2e230cdfaf4 Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/e2e230cdfaf4 Merge aarch64-jdk8u131-b12 ! .hgtags Changeset: 7a2663f80a5f Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/7a2663f80a5f Added tag aarch64-shenandoah-jdk8u131-b12 for changeset e2e230cdfaf4 ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:47:50 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:47:50 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/langtools: 8 new changesets Message-ID: <201704191647.v3JGlpAe001326@aojmv0008.oracle.com> Changeset: 957a3f295558 Author: andrew Date: 2017-04-12 08:32 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/957a3f295558 Added tag aarch64-jdk8u121-b15 for changeset 06ec76842b04 ! .hgtags Changeset: 8a78ce0ebb3c Author: mcimadamore Date: 2017-01-05 18:58 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/8a78ce0ebb3c 8168774: Polymorhic signature method check crashes javac Summary: Check for polysig method assumes arity is greater than zero Reviewed-by: vromero ! src/share/classes/com/sun/tools/javac/code/Types.java + test/tools/javac/meth/BadPolySig.java Changeset: 919a3c6bc315 Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/919a3c6bc315 Added tag aarch64-jdk8u131-b11 for changeset 8a78ce0ebb3c ! .hgtags Changeset: 493b3b58e3ca Author: andrew Date: 2017-04-13 05:54 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/493b3b58e3ca Merge aarch64-jdk8u131-b11 ! .hgtags Changeset: 0003cf4fca26 Author: andrew Date: 2017-04-13 05:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/0003cf4fca26 Added tag aarch64-shenandoah-jdk8u131-b11 for changeset 493b3b58e3ca ! .hgtags Changeset: 8ef3f0de2bc2 Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/8ef3f0de2bc2 Added tag aarch64-jdk8u131-b12 for changeset 919a3c6bc315 ! .hgtags Changeset: 3e12b4074316 Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/3e12b4074316 Merge aarch64-jdk8u131-b12 ! .hgtags Changeset: 13feb8932152 Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/13feb8932152 Added tag aarch64-shenandoah-jdk8u131-b12 for changeset 3e12b4074316 ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:47:58 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:47:58 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 19 new changesets Message-ID: <201704191647.v3JGlwcC001614@aojmv0008.oracle.com> Changeset: 142389cae1d3 Author: adinn Date: 2017-03-28 06:12 -0400 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/142389cae1d3 Correct ad rule output register types from iRegX to iRegXNoSp Backport to jdk8 of JDK9 fix for JDK-8177661 ! src/cpu/aarch64/vm/aarch64.ad Changeset: f2330cb3af9f Author: aph Date: 2017-04-04 14:49 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/f2330cb3af9f 8173472: AArch64: C1 comparisons with null only use 32-bit instructions Reviewed-by: roland ! src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp Changeset: 089205f7bfd2 Author: njian Date: 2017-01-22 16:33 +0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/089205f7bfd2 8172881: AArch64: assertion failure: the int pressure is incorrect Summary: Change the dst register type of get_and_setI/L/N/P from any register to non-special register. Reviewed-by: aph Contributed-by: yang.zhang at linaro.org ! src/cpu/aarch64/vm/aarch64.ad Changeset: e5d7f637919f Author: aph Date: 2017-04-04 14:59 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/e5d7f637919f 8170100: AArch64: Crash in C1-compiled code accessing References Reviewed-by: roland ! src/cpu/aarch64/vm/templateInterpreter_aarch64.cpp Changeset: 0fe0c692f4e9 Author: andrew Date: 2017-04-12 08:32 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/0fe0c692f4e9 Added tag aarch64-jdk8u121-b15 for changeset e5d7f637919f ! .hgtags Changeset: e68ad2c10623 Author: tschatzl Date: 2016-12-15 19:48 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/e68ad2c10623 8147910: Cache initial active_processor_count Summary: Introduce and initialize active_processor_count variable in VM. Reviewed-by: dholmes, jprovino ! src/share/vm/runtime/os.cpp ! src/share/vm/runtime/os.hpp Changeset: d11a5c24bdb2 Author: msolovie Date: 2016-12-09 19:40 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/d11a5c24bdb2 8150490: Update OS detection code to recognize Windows Server 2016 Reviewed-by: mgronlun, alanb, dholmes ! src/os/windows/vm/os_windows.cpp Changeset: 21eefd0c7215 Author: roland Date: 2016-07-25 14:31 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/21eefd0c7215 8161147: jvm crashes when -XX:+UseCountedLoopSafepoints is enabled Summary: don't convert loop with safepoint on the backedge to Counted loop Reviewed-by: kvn ! src/share/vm/opto/loopnode.cpp + test/compiler/loopopts/TestCountedLoopSafepointBackedge.java Changeset: 2e0b9dc9b8ba Author: tschatzl Date: 2016-12-15 20:00 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/2e0b9dc9b8ba 8161993: G1 crashes if active_processor_count changes during startup Summary: Use the initial active processor count for memory initialization instead of the current active one. Reviewed-by: dholmes, mgerdin ! src/share/vm/gc_implementation/g1/concurrentMark.cpp ! src/share/vm/gc_implementation/g1/dirtyCardQueue.cpp ! src/share/vm/runtime/vm_version.cpp Changeset: 4eb424fb499f Author: coleenp Date: 2016-12-13 14:37 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/4eb424fb499f 8168699: Validate special case invocations Reviewed-by: kevinw, vlivanov ! src/cpu/sparc/vm/c1_LIRGenerator_sparc.cpp ! src/cpu/x86/vm/c1_LIRGenerator_x86.cpp ! src/share/vm/c1/c1_CodeStubs.hpp ! src/share/vm/c1/c1_GraphBuilder.cpp ! src/share/vm/c1/c1_Instruction.hpp ! src/share/vm/ci/ciInstanceKlass.cpp ! src/share/vm/ci/ciInstanceKlass.hpp ! src/share/vm/ci/ciMethod.cpp ! src/share/vm/ci/ciMethod.hpp ! src/share/vm/interpreter/interpreterRuntime.cpp ! src/share/vm/interpreter/linkResolver.cpp ! src/share/vm/interpreter/linkResolver.hpp ! src/share/vm/oops/cpCache.cpp ! src/share/vm/oops/cpCache.hpp ! src/share/vm/opto/doCall.cpp ! src/share/vm/prims/methodHandles.cpp ! src/share/vm/runtime/javaCalls.cpp Changeset: 44f283fb5180 Author: dholmes Date: 2016-12-20 16:06 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/44f283fb5180 8170307: Stack size option -Xss is ignored Reviewed-by: dcubed, sspitsyn, gtriantafill ! src/os/linux/vm/os_linux.cpp Changeset: 71cf0e117575 Author: dholmes Date: 2017-01-05 18:55 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/71cf0e117575 8170888: [linux] Experimental support for cgroup memory limits in container (ie Docker) environments Summary: Set apparent physical memory to cgroup memory limit when UseCGroupMemoryLimitForHeap is true Reviewed-by: acorn, gtriantafill Contributed-by: Christine Flood ! src/share/vm/runtime/arguments.cpp ! src/share/vm/runtime/globals.hpp Changeset: 36dc9bbfa5f8 Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/36dc9bbfa5f8 Added tag aarch64-jdk8u131-b11 for changeset 71cf0e117575 ! .hgtags Changeset: b1d7eee4de51 Author: andrew Date: 2017-04-13 05:54 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/b1d7eee4de51 Merge aarch64-jdk8u131-b11 ! .hgtags ! src/cpu/aarch64/vm/aarch64.ad ! src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp ! src/cpu/aarch64/vm/templateInterpreter_aarch64.cpp ! src/cpu/x86/vm/c1_LIRGenerator_x86.cpp ! src/share/vm/ci/ciInstanceKlass.cpp ! src/share/vm/ci/ciInstanceKlass.hpp ! src/share/vm/gc_implementation/g1/concurrentMark.cpp ! src/share/vm/interpreter/interpreterRuntime.cpp ! src/share/vm/opto/loopnode.cpp ! src/share/vm/prims/methodHandles.cpp ! src/share/vm/runtime/arguments.cpp ! src/share/vm/runtime/globals.hpp ! src/share/vm/runtime/os.hpp Changeset: 83b5c71d212f Author: andrew Date: 2017-04-13 05:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/83b5c71d212f Added tag aarch64-shenandoah-jdk8u131-b11 for changeset b1d7eee4de51 ! .hgtags Changeset: f4086f3a0d69 Author: aph Date: 2017-04-18 13:07 -0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/f4086f3a0d69 AArch64 support for "8168699: Validate special case invocations" ! src/cpu/aarch64/vm/c1_LIRGenerator_aarch64.cpp Changeset: a3b619b8e2b6 Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/a3b619b8e2b6 Added tag aarch64-jdk8u131-b12 for changeset f4086f3a0d69 ! .hgtags Changeset: b878250be3dd Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/b878250be3dd Merge aarch64-jdk8u131-b12 ! .hgtags ! src/cpu/aarch64/vm/c1_LIRGenerator_aarch64.cpp Changeset: a9e9a19a0412 Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/a9e9a19a0412 Added tag aarch64-shenandoah-jdk8u131-b12 for changeset b878250be3dd ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:48:08 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:48:08 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jdk: 39 new changesets Message-ID: <201704191648.v3JGm9n6002092@aojmv0008.oracle.com> Changeset: 4987b365f035 Author: andrew Date: 2017-04-12 08:32 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/4987b365f035 Added tag aarch64-jdk8u121-b15 for changeset 86b9391b28d7 ! .hgtags Changeset: f7afebfedc72 Author: igerasim Date: 2016-08-31 11:19 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f7afebfedc72 6474807: (smartcardio) CardTerminal.connect() throws CardException instead of CardNotPresentException Reviewed-by: valeriep ! src/share/classes/sun/security/smartcardio/TerminalImpl.java Changeset: 2e9439f06256 Author: mcherkas Date: 2017-01-24 22:39 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/2e9439f06256 8167110: Windows peering issue 7155957: closed/java/awt/MenuBar/MenuBarStress1/MenuBarStress1.java hangs on win 64 bit with jdk8 8079595: Resizing dialog which is JWindow parent makes JVM crash 8147842: IME Composition Window is displayed at incorrect location Reviewed-by: serb ! src/share/classes/java/awt/Menu.java ! src/share/classes/java/awt/MenuBar.java ! src/share/classes/java/awt/MenuComponent.java ! src/windows/classes/sun/awt/windows/WMenuItemPeer.java ! src/windows/classes/sun/awt/windows/WObjectPeer.java ! src/windows/native/sun/windows/awt_Component.cpp ! src/windows/native/sun/windows/awt_Menu.cpp ! src/windows/native/sun/windows/awt_Menu.h ! src/windows/native/sun/windows/awt_MenuBar.cpp ! src/windows/native/sun/windows/awt_MenuBar.h ! src/windows/native/sun/windows/awt_MenuItem.cpp ! src/windows/native/sun/windows/awt_MenuItem.h ! src/windows/native/sun/windows/awt_PopupMenu.cpp ! src/windows/native/sun/windows/awt_PopupMenu.h ! src/windows/native/sun/windows/awt_new.cpp Changeset: 50e3a607d99d Author: vtewari Date: 2016-04-05 17:07 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/50e3a607d99d 7167293: FtpURLConnection connection leak on FileNotFoundException Reviewed-by: chegar, rriggs ! src/share/classes/sun/net/www/protocol/ftp/FtpURLConnection.java Changeset: f745f7bab4c9 Author: pchelko Date: 2016-12-09 10:01 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f745f7bab4c9 8035568: [macosx] Cursor management unification Reviewed-by: anthony, serb ! src/macosx/classes/sun/lwawt/LWMouseInfoPeer.java ! src/macosx/classes/sun/lwawt/LWToolkit.java ! src/macosx/classes/sun/lwawt/LWWindowPeer.java ! src/macosx/classes/sun/lwawt/PlatformWindow.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformEmbeddedFrame.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformLWWindow.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformWindow.java ! src/macosx/classes/sun/lwawt/macosx/CRobot.java ! src/macosx/classes/sun/lwawt/macosx/CViewPlatformEmbeddedFrame.java ! src/macosx/classes/sun/lwawt/macosx/LWCToolkit.java ! src/macosx/native/sun/awt/AWTWindow.m ! src/macosx/native/sun/awt/CCursorManager.m ! src/macosx/native/sun/awt/CRobot.m + test/java/awt/MouseInfo/GetPointerInfoTest.java + test/java/awt/MouseInfo/MultiscreenPointerInfo.java Changeset: 330ba74dfe49 Author: mcherkas Date: 2017-01-25 18:16 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/330ba74dfe49 8130769: The new menu can't be shown on the menubar after clicking the "Add" button. Reviewed-by: serb ! src/share/classes/java/awt/MenuBar.java Changeset: 6ede986bc351 Author: snikandrova Date: 2016-08-18 16:27 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/6ede986bc351 8146602: jdk/test/sun/misc/URLClassPath/ClassnameCharTest.java test fails with NullPointerException Reviewed-by: dfuchs, clanger ! test/sun/misc/URLClassPath/ClassnameCharTest.java Changeset: 91482fd579b0 Author: msolovie Date: 2016-12-09 19:34 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/91482fd579b0 8150490: Update OS detection code to recognize Windows Server 2016 Reviewed-by: mgronlun, alanb, dholmes ! src/windows/native/java/lang/java_props_md.c Changeset: e3babd92a65d Author: rpatil Date: 2016-09-10 22:54 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/e3babd92a65d 8160951: [TEST_BUG] javax/xml/bind/marshal/8134111/UnmarshalTest.java should be added into :needs_jre group 8160958: [TEST_BUG] java/net/SetFactoryPermission/SetFactoryPermission.java should be added into :needs_compact2 group Reviewed-by: igerasim ! test/TEST.groups Changeset: fe8d78a0f02a Author: mcherkas Date: 2017-01-26 17:26 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/fe8d78a0f02a 8161195: Regression: closed/javax/swing/text/FlowView/LayoutTest.java Reviewed-by: serb ! src/windows/native/sun/windows/awt_Component.cpp Changeset: f93d25469e44 Author: snikandrova Date: 2016-08-08 20:16 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f93d25469e44 8162876: [TEST_BUG] sun/net/www/protocol/http/HttpInputStream.java fails intermittently Reviewed-by: chegar ! test/sun/net/www/protocol/http/HttpInputStream.java Changeset: 522d7ee4e17f Author: coffeys Date: 2016-08-19 07:42 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/522d7ee4e17f 8162916: Test sun/security/krb5/auto/UnboundSSL.java fails Reviewed-by: weijun, asmotrak ! test/sun/security/krb5/auto/UnboundSSL.java Changeset: 8003c75a1396 Author: dfuchs Date: 2016-12-09 18:18 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/8003c75a1396 8163520: Reuse cache entries Reviewed-by: chegar, aefimov ! src/share/classes/sun/net/www/http/HttpClient.java ! src/share/classes/sun/net/www/protocol/http/AuthenticationInfo.java ! src/solaris/classes/sun/net/www/protocol/http/ntlm/NTLMAuthentication.java ! src/windows/classes/sun/net/www/protocol/http/ntlm/NTLMAuthentication.java Changeset: a3720aa79c07 Author: valeriep Date: 2016-11-23 19:46 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/a3720aa79c07 8163528: Better library loading Reviewed-by: mullan Contributed-by: florian at bogner.sh ! src/share/classes/sun/misc/Launcher.java Changeset: 248b9dfd9559 Author: snikandrova Date: 2016-08-29 20:55 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/248b9dfd9559 8164533: sun/security/ssl/SSLSocketImpl/CloseSocket.java failed with "Error while cleaning up threads after test" Reviewed-by: xuelei ! test/sun/security/ssl/com/sun/net/ssl/internal/ssl/SSLSocketImpl/CloseSocket.java Changeset: 8f411e15b753 Author: mcherkas Date: 2016-11-11 16:55 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/8f411e15b753 8165626: Improved window framing Reviewed-by: serb ! src/macosx/classes/com/apple/eawt/_AppDockIconHandler.java ! src/macosx/classes/sun/java2d/opengl/CGLLayer.java ! src/macosx/classes/sun/lwawt/macosx/CFRetainedResource.java ! src/macosx/classes/sun/lwawt/macosx/CImage.java ! src/macosx/classes/sun/lwawt/macosx/CMenuItem.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformComponent.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformLWWindow.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformView.java ! src/macosx/classes/sun/lwawt/macosx/CPlatformWindow.java ! src/macosx/classes/sun/lwawt/macosx/CTrayIcon.java ! src/macosx/classes/sun/lwawt/macosx/CViewPlatformEmbeddedFrame.java ! src/macosx/classes/sun/lwawt/macosx/CWarningWindow.java ! src/macosx/native/sun/awt/AWTSurfaceLayers.h ! src/macosx/native/sun/awt/AWTSurfaceLayers.m Changeset: 0e0a752e3809 Author: aefimov Date: 2016-10-24 17:02 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/0e0a752e3809 8167179: Make XSL generated namespace prefixes local to transformation process Reviewed-by: joehw + test/javax/xml/jaxp/transform/8167179/NamespacePrefixTest.java Changeset: 23c5c7127222 Author: robm Date: 2017-01-09 18:33 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/23c5c7127222 8169465: Deadlock in com.sun.jndi.ldap.pool.Connections Reviewed-by: dfuchs, vtewari ! src/share/classes/com/sun/jndi/ldap/pool/Connections.java ! src/share/classes/com/sun/jndi/ldap/pool/Pool.java Changeset: ad51ad05aecc Author: dmarkov Date: 2017-01-19 22:45 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/ad51ad05aecc 8169589: [macosx] Activating a JDialog puts to back another dialog Reviewed-by: anthony, serb ! src/macosx/classes/sun/lwawt/macosx/CPlatformWindow.java ! src/share/classes/java/awt/Window.java ! src/share/classes/sun/awt/AWTAccessor.java Changeset: d86ed639df42 Author: rpatil Date: 2017-02-25 09:50 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/d86ed639df42 8170222: Better transfers of files Reviewed-by: dfuchs, chegar, vtewari ! src/share/classes/sun/net/ftp/impl/FtpClient.java Changeset: e89ee7075633 Author: rpatil Date: 2016-12-12 17:30 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/e89ee7075633 8170316: (tz) Support tzdata2016j Reviewed-by: martin, okutsu ! make/data/tzdata/VERSION ! make/data/tzdata/africa ! make/data/tzdata/asia ! make/data/tzdata/europe ! make/data/tzdata/iso3166.tab ! make/data/tzdata/zone.tab ! test/sun/util/calendar/zi/tzdata/VERSION ! test/sun/util/calendar/zi/tzdata/africa ! test/sun/util/calendar/zi/tzdata/asia ! test/sun/util/calendar/zi/tzdata/europe ! test/sun/util/calendar/zi/tzdata/iso3166.tab ! test/sun/util/calendar/zi/tzdata/zone.tab Changeset: 26cda931a436 Author: aefimov Date: 2017-01-17 15:35 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/26cda931a436 8170814: Reuse cache entries (part II) Reviewed-by: dfuchs ! src/share/classes/sun/net/www/http/HttpClient.java ! src/share/classes/sun/net/www/protocol/http/NegotiateAuthentication.java Changeset: 0ad54e1d1ef5 Author: rpatil Date: 2016-12-26 16:00 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/0ad54e1d1ef5 8171121: Enhancing jar checking Reviewed-by: ascarpino ! src/share/lib/security/java.security-aix ! src/share/lib/security/java.security-linux ! src/share/lib/security/java.security-macosx ! src/share/lib/security/java.security-solaris ! src/share/lib/security/java.security-windows ! test/sun/security/tools/jarsigner/TimestampCheck.java Changeset: f2e5534d1e70 Author: robm Date: 2016-12-16 20:39 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f2e5534d1e70 8171388: Update JNDI Thread contexts Reviewed-by: chegar ! src/share/classes/java/lang/Thread.java Changeset: 3ad5f8977692 Author: rpatil Date: 2017-02-27 19:19 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/3ad5f8977692 8171533: Better email transfer Reviewed-by: dfuchs, chegar, vtewari ! src/share/classes/sun/net/smtp/SmtpClient.java Changeset: b6c62eddc86c Author: dmarkov Date: 2017-01-19 22:47 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/b6c62eddc86c 8171949: [macosx] AWT_ZoomFrame Automated tests fail with error: The bitwise mask Frame.ICONIFIED is not setwhen the frame is in ICONIFIED state Reviewed-by: ssadetsky, serb ! src/macosx/classes/sun/lwawt/macosx/CPlatformWindow.java ! src/macosx/native/sun/awt/AWTWindow.m Changeset: f3b312f1ce87 Author: dmarkov Date: 2017-01-02 17:15 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f3b312f1ce87 8171952: [macosx] AWT_Modality/Automated/ModalExclusion/NoExclusion/ModelessDialog test fails as DummyButton on Dialog did not gain focus when clicked. Reviewed-by: ssadetsky, serb ! src/macosx/native/sun/awt/AWTWindow.m + test/java/awt/Frame/ObscuredFrame/ObscuredFrameTest.java Changeset: 094fd7d891b6 Author: robm Date: 2017-02-09 16:34 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/094fd7d891b6 8172299: Improve class processing Reviewed-by: rriggs ! src/share/classes/java/io/ObjectInputStream.java Changeset: fdfb9f6f399b Author: coffeys Date: 2017-02-08 12:10 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/fdfb9f6f399b 8173783: IllegalArgumentException: jdk.tls.namedGroups Reviewed-by: xuelei, wetmore ! src/share/classes/sun/security/ssl/SupportedEllipticCurvesExtension.java + test/sun/security/ssl/ServerHandshaker/HelloExtensionsTest.java Changeset: e940b178ce4f Author: asaha Date: 2017-02-04 01:22 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/e940b178ce4f 8173931: 8u131 L10n resource file update Reviewed-by: coffeys Contributed-by: li.jiang at oracle.com ! src/macosx/classes/com/apple/laf/resources/aqua_de.properties ! src/share/classes/com/sun/java/swing/plaf/windows/resources/windows_ko.properties ! src/share/classes/com/sun/rowset/RowSetResourceBundle_sv.properties ! src/share/classes/com/sun/swing/internal/plaf/metal/resources/metal_ko.properties ! src/share/classes/com/sun/swing/internal/plaf/synth/resources/synth_ko.properties ! src/share/classes/sun/security/tools/jarsigner/Resources_ja.java ! src/share/classes/sun/security/tools/jarsigner/Resources_zh_CN.java ! src/share/classes/sun/security/tools/policytool/Resources_sv.java ! src/share/classes/sun/tools/jar/resources/jar_sv.properties Changeset: 968ff27bac31 Author: robm Date: 2017-02-27 17:43 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/968ff27bac31 8174844: Incorrect GPL header causes RE script to miss swap to commercial header for licensee source bundle Reviewed-by: coffeys ! src/share/classes/sun/security/util/AbstractAlgorithmConstraints.java Changeset: 75bc4c5db073 Author: aefimov Date: 2017-02-28 14:44 +0300 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/75bc4c5db073 8174985: NTLM authentication doesn't work with IIS if NTLM cache is disabled Reviewed-by: dfuchs ! src/share/classes/sun/net/www/http/HttpClient.java Changeset: 05e10ee4afec Author: rpatil Date: 2017-03-10 12:50 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/05e10ee4afec 8176044: (tz) Support tzdata2017a Reviewed-by: naoto ! make/data/tzdata/VERSION ! make/data/tzdata/africa ! make/data/tzdata/antarctica ! make/data/tzdata/asia ! make/data/tzdata/australasia ! make/data/tzdata/backward ! make/data/tzdata/europe ! make/data/tzdata/leapseconds ! make/data/tzdata/northamerica ! make/data/tzdata/southamerica ! make/data/tzdata/zone.tab ! test/sun/util/calendar/zi/tzdata/VERSION ! test/sun/util/calendar/zi/tzdata/africa ! test/sun/util/calendar/zi/tzdata/antarctica ! test/sun/util/calendar/zi/tzdata/asia ! test/sun/util/calendar/zi/tzdata/australasia ! test/sun/util/calendar/zi/tzdata/backward ! test/sun/util/calendar/zi/tzdata/europe ! test/sun/util/calendar/zi/tzdata/leapseconds ! test/sun/util/calendar/zi/tzdata/northamerica ! test/sun/util/calendar/zi/tzdata/southamerica ! test/sun/util/calendar/zi/tzdata/zone.tab Changeset: 9ae547861e9f Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/9ae547861e9f Added tag aarch64-jdk8u131-b11 for changeset 05e10ee4afec ! .hgtags Changeset: 75599266749d Author: andrew Date: 2017-04-13 05:54 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/75599266749d Merge aarch64-jdk8u131-b11 ! .hgtags Changeset: cd22faffc218 Author: andrew Date: 2017-04-13 05:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/cd22faffc218 Added tag aarch64-shenandoah-jdk8u131-b11 for changeset 75599266749d ! .hgtags Changeset: 968945f351b7 Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/968945f351b7 Added tag aarch64-jdk8u131-b12 for changeset 9ae547861e9f ! .hgtags Changeset: 15514a0fc567 Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/15514a0fc567 Merge aarch64-jdk8u131-b12 ! .hgtags Changeset: 692cc6892c60 Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/692cc6892c60 Added tag aarch64-shenandoah-jdk8u131-b12 for changeset 15514a0fc567 ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 16:48:15 2017 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Wed, 19 Apr 2017 16:48:15 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/nashorn: 7 new changesets Message-ID: <201704191648.v3JGmFJE002239@aojmv0008.oracle.com> Changeset: 13ad0227abae Author: andrew Date: 2017-04-12 08:32 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/13ad0227abae Added tag aarch64-jdk8u121-b15 for changeset e42e6f6a6aae ! .hgtags Changeset: 9c1264a75e80 Author: andrew Date: 2017-04-12 18:56 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/9c1264a75e80 Added tag aarch64-jdk8u131-b11 for changeset 13ad0227abae ! .hgtags Changeset: be771eb5f952 Author: andrew Date: 2017-04-13 05:54 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/be771eb5f952 Merge aarch64-jdk8u131-b11 ! .hgtags Changeset: 6da04cc53cb0 Author: andrew Date: 2017-04-13 05:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/6da04cc53cb0 Added tag aarch64-shenandoah-jdk8u131-b11 for changeset be771eb5f952 ! .hgtags Changeset: 2c46c952e68f Author: andrew Date: 2017-04-19 06:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/2c46c952e68f Added tag aarch64-jdk8u131-b12 for changeset 9c1264a75e80 ! .hgtags Changeset: e97f26c79b9c Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/e97f26c79b9c Merge aarch64-jdk8u131-b12 ! .hgtags Changeset: 598a0ca370c1 Author: andrew Date: 2017-04-19 16:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/598a0ca370c1 Added tag aarch64-shenandoah-jdk8u131-b12 for changeset e97f26c79b9c ! .hgtags From gnu.andrew at redhat.com Wed Apr 19 22:21:03 2017 From: gnu.andrew at redhat.com (Andrew Hughes) Date: Wed, 19 Apr 2017 18:21:03 -0400 (EDT) Subject: [aarch64-port-dev ] [RFR] u131 Update In-Reply-To: References: <573664785.28945174.1492581881397.JavaMail.zimbra@redhat.com> Message-ID: <36091975.29350211.1492640463612.JavaMail.zimbra@redhat.com> ----- Original Message ----- > On 19/04/17 07:04, Andrew Hughes wrote: > > We also add an AArch64 port of 8168699 to create aarch64-jdk8u131-b12. > > > > http://cr.openjdk.java.net/~andrew/aarch64-8/u131 > > > > Ok to push? > > OK, thanks. > > Andrew. > > Thanks. Pushed and synced to shenandoah-jdk8u as aarch64-shenandoah-jdk8u131-b12. -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) Web Site: http://fuseyism.com Twitter: https://twitter.com/gnu_andrew_java PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 From ningsheng.jian at linaro.org Thu Apr 20 01:53:57 2017 From: ningsheng.jian at linaro.org (Ningsheng Jian) Date: Thu, 20 Apr 2017 09:53:57 +0800 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: <01f26378-9579-0469-8c03-ef0a71758d6e@redhat.com> References: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> <01f26378-9579-0469-8c03-ef0a71758d6e@redhat.com> Message-ID: Yes, viewing online should be better. TeraSort is time, and the gap of TeraSort number between arm64 and aarch64 deserves an investigation. Ningsheng On 19 April 2017 at 19:47, Andrew Haley wrote: > On 19/04/17 12:30, Andrew Haley wrote: > > I think Dacapo is throughput? And TeraSort is time? > > My apologies: I had downloaded the spreadsheets, and OpenOffice > wasn't showing me the (less is better). > > Andrew. > > From zhongwei.yao at linaro.org Thu Apr 20 02:03:12 2017 From: zhongwei.yao at linaro.org (Zhongwei Yao) Date: Thu, 20 Apr 2017 10:03:12 +0800 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> References: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> Message-ID: On 19 April 2017 at 19:30, Andrew Haley wrote: > Looking at this some more, I can't tell which benchmarks are > throughput (big is good) and which are time (small is good). This > makes it very hard for me to see where community AArch64 is lagging > performance. > > I think Dacapo is throughput? And TeraSort is time? > > The results for Partner B's hardware on Dacapo are so weird that I > think there must be something wrong. lusearch didn't work at all, so > there must be a code generation problem somewhere. On our Partner B's hardware, lusearch could run but it failed to converge at warmup stage at every time. So the result is set to 0 in our result. And for sunflow case, it is in similar case like lusearch. Sunflow could run but it failed to converge at most time. I've checked it succeeds to converge only once in our result. So the standard deviation is 0 because of there are only one. I should have added note for this case. Sorry for confusion. > SPECjvm I understand, it's well-designed and stable, and I'm quite > satisfied with the results there. > > With regard to the default size of the code cache, I think that's a > hangover from the time whan we hadn't solved the problem of generating > far calls, and I'm considering changing it to be the same as other > architectures. The problem with switching, though, is that while it > won't make any significant difference to throughput it will increase > code size, but I can see that it makes sense that we dont run out of > code cache before other architectures do. > > Andrew. > -- Best regards, Zhongwei From zhongwei.yao at linaro.org Thu Apr 20 02:52:14 2017 From: zhongwei.yao at linaro.org (Zhongwei Yao) Date: Thu, 20 Apr 2017 10:52:14 +0800 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> Message-ID: By the way, here is one failure log message for "lusearch" in DaCapo on Partner B platform. It fails to converge after 20 iterations. ===== DaCapo 9.12 lusearch starting warmup 1 ===== ===== DaCapo 9.12 lusearch completed warmup 1 in xxx msec ===== ===== DaCapo 9.12 lusearch starting warmup 2 ===== ===== DaCapo 9.12 lusearch completed warmup 2 in xxx msec ===== . . . ===== DaCapo 9.12 lusearch starting warmup 20 ===== ===== DaCapo 9.12 lusearch completed warmup 20 in xxx msec ===== Benchmark failed to converge. (real numbers are replaced by "xxx") On 20 April 2017 at 10:03, Zhongwei Yao wrote: > > On 19 April 2017 at 19:30, Andrew Haley wrote: > >> Looking at this some more, I can't tell which benchmarks are >> throughput (big is good) and which are time (small is good). This >> makes it very hard for me to see where community AArch64 is lagging >> performance. >> >> I think Dacapo is throughput? And TeraSort is time? >> >> The results for Partner B's hardware on Dacapo are so weird that I >> think there must be something wrong. lusearch didn't work at all, so >> there must be a code generation problem somewhere. > > > On our Partner B's hardware, lusearch could run but it failed to converge > at warmup stage at every time. So the result is set to 0 in our result. > > And for sunflow case, it is in similar case like lusearch. Sunflow could > run but it failed to converge at most time. I've checked it succeeds to > converge only once in our result. So the standard deviation is 0 because of > there are only one. I should have added note for this case. Sorry for > confusion. > > >> SPECjvm I understand, it's well-designed and stable, and I'm quite >> satisfied with the results there. >> >> With regard to the default size of the code cache, I think that's a >> hangover from the time whan we hadn't solved the problem of generating >> far calls, and I'm considering changing it to be the same as other >> architectures. The problem with switching, though, is that while it >> won't make any significant difference to throughput it will increase >> code size, but I can see that it makes sense that we dont run out of >> code cache before other architectures do. >> >> Andrew. >> > > > > -- > Best regards, > Zhongwei > -- Best regards, Zhongwei From aph at redhat.com Thu Apr 20 09:07:04 2017 From: aph at redhat.com (Andrew Haley) Date: Thu, 20 Apr 2017 10:07:04 +0100 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> Message-ID: <89264c5c-da92-dbc3-c547-d1473d692460@redhat.com> On 20/04/17 03:03, Zhongwei Yao wrote: > On 19 April 2017 at 19:30, Andrew Haley wrote: > >> Looking at this some more, I can't tell which benchmarks are >> throughput (big is good) and which are time (small is good). This >> makes it very hard for me to see where community AArch64 is lagging >> performance. >> >> I think Dacapo is throughput? And TeraSort is time? >> >> The results for Partner B's hardware on Dacapo are so weird that I >> think there must be something wrong. lusearch didn't work at all, so >> there must be a code generation problem somewhere. > > On our Partner B's hardware, lusearch could run but it failed to converge > at warmup stage at every time. So the result is set to 0 in our result. > > And for sunflow case, it is in similar case like lusearch. Sunflow could > run but it failed to converge at most time. I've checked it succeeds to > converge only once in our result. So the standard deviation is 0 because of > there are only one. I should have added note for this case. Sorry for > confusion. OK, so I think we have to reject all of the results on Partner B's hardware because something is severely broken. Andrew. From aph at redhat.com Thu Apr 20 09:09:31 2017 From: aph at redhat.com (Andrew Haley) Date: Thu, 20 Apr 2017 10:09:31 +0100 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> <01f26378-9579-0469-8c03-ef0a71758d6e@redhat.com> Message-ID: <624cee20-03b2-8b73-70f3-87701ba28c97@redhat.com> On 20/04/17 02:53, Ningsheng Jian wrote: > TeraSort is time, and the gap of TeraSort number between arm64 and aarch64 > deserves an investigation. Why does it deserve an investigation? I don't understand this. Andrew. From ningsheng.jian at linaro.org Thu Apr 20 09:47:07 2017 From: ningsheng.jian at linaro.org (Ningsheng Jian) Date: Thu, 20 Apr 2017 17:47:07 +0800 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: <624cee20-03b2-8b73-70f3-87701ba28c97@redhat.com> References: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> <01f26378-9579-0469-8c03-ef0a71758d6e@redhat.com> <624cee20-03b2-8b73-70f3-87701ba28c97@redhat.com> Message-ID: On 20 April 2017 at 17:09, Andrew Haley wrote: > On 20/04/17 02:53, Ningsheng Jian wrote: >> TeraSort is time, and the gap of TeraSort number between arm64 and aarch64 >> deserves an investigation. > > Why does it deserve an investigation? I don't understand this. > aarch64 is ~50% better than arm64 on this benchmark. For a non-micro benchmark, it is a big gap. Maybe Oracle people care more about this. Thanks, Ningsheng From aph at redhat.com Thu Apr 20 09:54:27 2017 From: aph at redhat.com (Andrew Haley) Date: Thu, 20 Apr 2017 10:54:27 +0100 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> <01f26378-9579-0469-8c03-ef0a71758d6e@redhat.com> <624cee20-03b2-8b73-70f3-87701ba28c97@redhat.com> Message-ID: On 20/04/17 10:47, Ningsheng Jian wrote: > On 20 April 2017 at 17:09, Andrew Haley wrote: >> On 20/04/17 02:53, Ningsheng Jian wrote: >>> TeraSort is time, and the gap of TeraSort number between arm64 and aarch64 >>> deserves an investigation. >> >> Why does it deserve an investigation? I don't understand this. >> > > aarch64 is ~50% better than arm64 on this benchmark. For a non-micro > benchmark, it is a big gap. Maybe Oracle people care more about this. Oh, I see. OK. Andrew. From stuart.monteith at linaro.org Thu Apr 20 10:39:14 2017 From: stuart.monteith at linaro.org (Stuart Monteith) Date: Thu, 20 Apr 2017 11:39:14 +0100 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: <89264c5c-da92-dbc3-c547-d1473d692460@redhat.com> References: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> <89264c5c-da92-dbc3-c547-d1473d692460@redhat.com> Message-ID: Zhongwei - I'd like you to check the OS as it is running. Are there any background processes running? What is the memory pressure like? Are there any errors in the kernel logs? Does a pristine machine exhibit the same behaviour? I'm concerned there might not be the controls necessary to get clean results. BR, Stuart On 20 April 2017 at 10:07, Andrew Haley wrote: > On 20/04/17 03:03, Zhongwei Yao wrote: >> On 19 April 2017 at 19:30, Andrew Haley wrote: >> >>> Looking at this some more, I can't tell which benchmarks are >>> throughput (big is good) and which are time (small is good). This >>> makes it very hard for me to see where community AArch64 is lagging >>> performance. >>> >>> I think Dacapo is throughput? And TeraSort is time? >>> >>> The results for Partner B's hardware on Dacapo are so weird that I >>> think there must be something wrong. lusearch didn't work at all, so >>> there must be a code generation problem somewhere. >> >> On our Partner B's hardware, lusearch could run but it failed to converge >> at warmup stage at every time. So the result is set to 0 in our result. >> >> And for sunflow case, it is in similar case like lusearch. Sunflow could >> run but it failed to converge at most time. I've checked it succeeds to >> converge only once in our result. So the standard deviation is 0 because of >> there are only one. I should have added note for this case. Sorry for >> confusion. > > OK, so I think we have to reject all of the results on Partner B's hardware > because something is severely broken. > > Andrew. > From rkennke at redhat.com Thu Apr 20 13:26:04 2017 From: rkennke at redhat.com (Roman Kennke) Date: Thu, 20 Apr 2017 15:26:04 +0200 Subject: [aarch64-port-dev ] RFR: Import 3 Shenandoah fixes into JDK8 integration repo Message-ID: <9b048f2c-37c9-5285-c20b-f55fb2d31419@redhat.com> We need 3 more fixes from Shenandoah's JDK8u repo in the aarch64/shenandoah integration repo: http://hg.openjdk.java.net/shenandoah/jdk8u/hotspot/rev/516125718f54 http://hg.openjdk.java.net/shenandoah/jdk8u/hotspot/rev/335eb870833a http://hg.openjdk.java.net/shenandoah/jdk8u/hotspot/rev/b733ce321ce9 This is the combined changeset: http://cr.openjdk.java.net/~rkennke/2017-04-20/webrev.00/ Ok to push? Roman From aph at redhat.com Thu Apr 20 13:28:38 2017 From: aph at redhat.com (Andrew Haley) Date: Thu, 20 Apr 2017 14:28:38 +0100 Subject: [aarch64-port-dev ] RFR: Import 3 Shenandoah fixes into JDK8 integration repo In-Reply-To: <9b048f2c-37c9-5285-c20b-f55fb2d31419@redhat.com> References: <9b048f2c-37c9-5285-c20b-f55fb2d31419@redhat.com> Message-ID: <91dc2c22-b63a-14a9-a928-3b573bae3016@redhat.com> On 20/04/17 14:26, Roman Kennke wrote: > http://cr.openjdk.java.net/~rkennke/2017-04-20/webrev.00/ > > Ok to push? OK, thanks. Andrew. From roman at kennke.org Thu Apr 20 13:32:26 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 13:32:26 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: Import from Shenandoah tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-03-23 Message-ID: <201704201332.v3KDWQcq027422@aojmv0008.oracle.com> Changeset: 3b2e6a63336f Author: shade Date: 2017-04-19 16:46 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/3b2e6a63336f Import from Shenandoah tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-03-23 ! src/share/vm/asm/assembler.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahCollectorPolicy.cpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeapRegion.hpp ! src/share/vm/gc_implementation/shenandoah/shenandoahHeapRegion.inline.hpp From roman at kennke.org Thu Apr 20 13:33:00 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 13:33:00 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah: Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset 7e7905cd2090 Message-ID: <201704201333.v3KDX0IC027985@aojmv0008.oracle.com> Changeset: f046a4cc0af9 Author: rkennke Date: 2017-04-20 15:31 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/f046a4cc0af9 Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset 7e7905cd2090 ! .hgtags From roman at kennke.org Thu Apr 20 13:33:01 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 13:33:01 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/langtools: Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset 13feb8932152 Message-ID: <201704201333.v3KDX1kj028031@aojmv0008.oracle.com> Changeset: 555d67494161 Author: rkennke Date: 2017-04-20 15:31 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/555d67494161 Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset 13feb8932152 ! .hgtags From roman at kennke.org Thu Apr 20 13:33:02 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 13:33:02 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/corba: Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset fd5ad2b93775 Message-ID: <201704201333.v3KDX2PX028136@aojmv0008.oracle.com> Changeset: 4654b9575b4f Author: rkennke Date: 2017-04-20 15:31 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/4654b9575b4f Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset fd5ad2b93775 ! .hgtags From roman at kennke.org Thu Apr 20 13:33:01 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 13:33:01 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxws: Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset 7a2663f80a5f Message-ID: <201704201333.v3KDX2k0028094@aojmv0008.oracle.com> Changeset: bc344953e401 Author: rkennke Date: 2017-04-20 15:31 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/bc344953e401 Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset 7a2663f80a5f ! .hgtags From roman at kennke.org Thu Apr 20 13:33:03 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 13:33:03 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxp: Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset b1f21ba8f2ad Message-ID: <201704201333.v3KDX3nH028142@aojmv0008.oracle.com> Changeset: 223c5b41a6b2 Author: rkennke Date: 2017-04-20 15:31 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/223c5b41a6b2 Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset b1f21ba8f2ad ! .hgtags From roman at kennke.org Thu Apr 20 13:33:04 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 13:33:04 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jdk: Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset 692cc6892c60 Message-ID: <201704201333.v3KDX4HN028155@aojmv0008.oracle.com> Changeset: b5602b6ff119 Author: rkennke Date: 2017-04-20 15:31 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/b5602b6ff119 Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset 692cc6892c60 ! .hgtags From roman at kennke.org Thu Apr 20 13:33:06 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 13:33:06 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/nashorn: Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset 598a0ca370c1 Message-ID: <201704201333.v3KDX65x028232@aojmv0008.oracle.com> Changeset: ae64a9237a3d Author: rkennke Date: 2017-04-20 15:31 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/ae64a9237a3d Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset 598a0ca370c1 ! .hgtags From roman at kennke.org Thu Apr 20 13:33:05 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 13:33:05 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset 3b2e6a63336f Message-ID: <201704201333.v3KDX5bP028213@aojmv0008.oracle.com> Changeset: 6ffe8637a506 Author: rkennke Date: 2017-04-20 15:31 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/6ffe8637a506 Added tag aarch64-shenandoah-jdk8u121-b14-shenandoah-merge-2017-04-20 for changeset 3b2e6a63336f ! .hgtags From roman at kennke.org Thu Apr 20 15:07:57 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 15:07:57 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/langtools: Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset 555d67494161 Message-ID: <201704201507.v3KF7vv1005611@aojmv0008.oracle.com> Changeset: 6ee0027a38e2 Author: rkennke Date: 2017-04-20 17:06 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/6ee0027a38e2 Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset 555d67494161 ! .hgtags From roman at kennke.org Thu Apr 20 15:07:56 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 15:07:56 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxws: Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset bc344953e401 Message-ID: <201704201507.v3KF7vjp005559@aojmv0008.oracle.com> Changeset: 075e44b28f09 Author: rkennke Date: 2017-04-20 17:06 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/075e44b28f09 Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset bc344953e401 ! .hgtags From roman at kennke.org Thu Apr 20 15:07:56 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 15:07:56 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah: Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset f046a4cc0af9 Message-ID: <201704201507.v3KF7umi005546@aojmv0008.oracle.com> Changeset: ecdcc34293e7 Author: rkennke Date: 2017-04-20 17:06 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/ecdcc34293e7 Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset f046a4cc0af9 ! .hgtags From roman at kennke.org Thu Apr 20 15:07:58 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 15:07:58 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/corba: Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset 4654b9575b4f Message-ID: <201704201507.v3KF7wlb005664@aojmv0008.oracle.com> Changeset: 1da98775fd8d Author: rkennke Date: 2017-04-20 17:06 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/1da98775fd8d Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset 4654b9575b4f ! .hgtags From roman at kennke.org Thu Apr 20 15:07:59 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 15:07:59 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jdk: Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset b5602b6ff119 Message-ID: <201704201507.v3KF7xKH005679@aojmv0008.oracle.com> Changeset: 69650d4d1fa4 Author: rkennke Date: 2017-04-20 17:06 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/69650d4d1fa4 Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset b5602b6ff119 ! .hgtags From roman at kennke.org Thu Apr 20 15:08:00 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 15:08:00 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxp: Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset 223c5b41a6b2 Message-ID: <201704201508.v3KF80H6005687@aojmv0008.oracle.com> Changeset: 6f237609794a Author: rkennke Date: 2017-04-20 17:06 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/6f237609794a Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset 223c5b41a6b2 ! .hgtags From roman at kennke.org Thu Apr 20 15:08:01 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 15:08:01 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/nashorn: Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset ae64a9237a3d Message-ID: <201704201508.v3KF81cP005693@aojmv0008.oracle.com> Changeset: 4bd25f647c77 Author: rkennke Date: 2017-04-20 17:06 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/4bd25f647c77 Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset ae64a9237a3d ! .hgtags From roman at kennke.org Thu Apr 20 15:08:02 2017 From: roman at kennke.org (roman at kennke.org) Date: Thu, 20 Apr 2017 15:08:02 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset 6ffe8637a506 Message-ID: <201704201508.v3KF82f7005699@aojmv0008.oracle.com> Changeset: e67d2a8b9aca Author: rkennke Date: 2017-04-20 17:06 +0200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/e67d2a8b9aca Added tag aarch64-shenandoah-jdk8u131-b12-shenandoah-merge-2017-04-20 for changeset 6ffe8637a506 ! .hgtags From ci_notify at linaro.org Thu Apr 20 22:40:20 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Thu, 20 Apr 2017 22:40:20 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <1532841526.1721.1492728022012.JavaMail.jenkins@90c74440cc95> 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/2017/110/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2016/dec/01 pass: 668; fail: 44; error: 6 Build 1: aarch64/2016/dec/21 pass: 668; fail: 44; error: 6 Build 2: aarch64/2017/jan/18 pass: 672; fail: 44; error: 3 Build 3: aarch64/2017/feb/04 pass: 672; fail: 44; error: 3 Build 4: aarch64/2017/feb/24 pass: 672; fail: 44; error: 3 Build 5: aarch64/2017/mar/29 pass: 672; fail: 44; error: 3 Build 6: aarch64/2017/apr/05 pass: 672; fail: 44; error: 3 Build 7: aarch64/2017/apr/20 pass: 673; fail: 44; error: 3 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2016/dec/21 pass: 5,621; fail: 219; error: 45 Build 1: aarch64/2017/jan/18 pass: 5,683; fail: 213; error: 36 Build 2: aarch64/2017/feb/04 pass: 5,667; fail: 234; error: 41 Build 3: aarch64/2017/feb/24 pass: 5,701; fail: 217; error: 27 Build 4: aarch64/2017/mar/29 pass: 5,686; fail: 225; error: 34 Build 5: aarch64/2017/apr/05 pass: 5,677; fail: 235; error: 33 Build 6: aarch64/2017/apr/20 pass: 5,671; fail: 254; error: 34 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2016/dec/01 pass: 3,091; error: 16 Build 1: aarch64/2016/dec/21 pass: 3,096; error: 11 Build 2: aarch64/2017/jan/18 pass: 3,098; error: 13 Build 3: aarch64/2017/feb/04 pass: 3,094; error: 17 Build 4: aarch64/2017/feb/24 pass: 3,106; error: 6 Build 5: aarch64/2017/mar/29 pass: 3,105; fail: 2; error: 5 Build 6: aarch64/2017/apr/05 pass: 3,104; fail: 2; error: 6 Build 7: aarch64/2017/apr/20 pass: 3,101; fail: 2; error: 10 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2016/nov/03 pass: 664; fail: 44; error: 6 Build 1: aarch64/2016/nov/08 pass: 664; fail: 44; error: 6 Build 2: aarch64/2016/nov/09 pass: 664; fail: 44; error: 6 Build 3: aarch64/2016/nov/21 pass: 668; fail: 44; error: 6 Build 4: aarch64/2016/dec/01 pass: 669; fail: 43; error: 6 Build 5: aarch64/2016/dec/21 pass: 668; fail: 44; error: 6 Build 6: aarch64/2017/jan/18 pass: 673; fail: 43; error: 3 Build 7: aarch64/2017/feb/04 pass: 673; fail: 43; error: 3 Build 8: aarch64/2017/feb/24 pass: 673; fail: 43; error: 3 Build 9: aarch64/2017/mar/29 pass: 673; fail: 43; error: 3 Build 10: aarch64/2017/apr/05 pass: 673; fail: 43; error: 3 Build 11: aarch64/2017/apr/20 pass: 674; fail: 43; error: 3 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2016/dec/21 pass: 5,618; fail: 226; error: 41 Build 1: aarch64/2017/jan/18 pass: 5,690; fail: 206; error: 36 Build 2: aarch64/2017/feb/04 pass: 5,669; fail: 214; error: 59 Build 3: aarch64/2017/feb/24 pass: 5,701; fail: 221; error: 23 Build 4: aarch64/2017/mar/29 pass: 5,696; fail: 222; error: 27 Build 5: aarch64/2017/apr/05 pass: 5,692; fail: 229; error: 24 Build 6: aarch64/2017/apr/20 pass: 5,705; fail: 220; error: 34 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2016/nov/03 pass: 3,092; error: 15 Build 1: aarch64/2016/nov/08 pass: 3,092; error: 15 Build 2: aarch64/2016/nov/09 pass: 3,091; error: 16 Build 3: aarch64/2016/nov/21 pass: 3,095; error: 12 Build 4: aarch64/2016/dec/01 pass: 3,095; error: 12 Build 5: aarch64/2016/dec/21 pass: 3,092; error: 15 Build 6: aarch64/2017/jan/18 pass: 3,102; error: 9 Build 7: aarch64/2017/feb/04 pass: 3,099; error: 12 Build 8: aarch64/2017/feb/24 pass: 3,109; error: 3 Build 9: aarch64/2017/mar/29 pass: 3,104; fail: 2; error: 6 Build 10: aarch64/2017/apr/05 pass: 3,105; fail: 2; error: 5 Build 11: aarch64/2017/apr/20 pass: 3,098; fail: 2; error: 13 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): 0.98x Relative performance: Server critical-jOPS (nc): 0.95x 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 client and server compilers on 2014-04-01. Relative performance: Zero: 1.0, Client: 57.15, Server: 111.14 Client 57.15 / Client 2014-04-01 (43.00): 1.33x Server 111.14 / Server 2014-04-01 (71.00): 1.57x 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. 2016-11-03 pass rate: 5140/5140, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2016/308/results/ 2016-11-21 pass rate: 5140/5140, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2016/326/results/ 2016-12-01 pass rate: 5140/5140, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2016/336/results/ 2016-12-22 pass rate: 5140/5140, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2016/356/results/ 2017-01-18 pass rate: 5140/5140, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2017/018/results/ 2017-02-06 pass rate: 5140/5140, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2017/035/results/ 2017-02-25 pass rate: 5176/5176, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2017/055/results/ 2017-03-29 pass rate: 8484/8485, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2017/088/results/ 2017-04-05 pass rate: 8484/8485, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2017/095/results/ 2017-04-20 pass rate: 8484/8485, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2017/110/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From zhongwei.yao at linaro.org Fri Apr 21 04:33:22 2017 From: zhongwei.yao at linaro.org (Zhongwei Yao) Date: Fri, 21 Apr 2017 12:33:22 +0800 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> <89264c5c-da92-dbc3-c547-d1473d692460@redhat.com> Message-ID: Hi, Stuart, Thanks for your suggestions. The tests were running on dedicated clean machines. I don't think there were any non-negligible background processes. The physical memory is large enough (>32G), but we run this benchmark with default JVM heap configurations. We updated kernel/firmware in one of the test machines, and the result of these Dacapo benchmarks looks more stable, but still with relative high standard deviation. On 20 April 2017 at 18:39, Stuart Monteith wrote: > Zhongwei - I'd like you to check the OS as it is running. Are there > any background processes running? > What is the memory pressure like? > > Are there any errors in the kernel logs? > Does a pristine machine > exhibit the same behaviour? > I'm concerned there might not be the > controls necessary to get clean results. > > BR, > Stuart > > > On 20 April 2017 at 10:07, Andrew Haley wrote: > > On 20/04/17 03:03, Zhongwei Yao wrote: > >> On 19 April 2017 at 19:30, Andrew Haley wrote: > >> > >>> Looking at this some more, I can't tell which benchmarks are > >>> throughput (big is good) and which are time (small is good). This > >>> makes it very hard for me to see where community AArch64 is lagging > >>> performance. > >>> > >>> I think Dacapo is throughput? And TeraSort is time? > >>> > >>> The results for Partner B's hardware on Dacapo are so weird that I > >>> think there must be something wrong. lusearch didn't work at all, so > >>> there must be a code generation problem somewhere. > >> > >> On our Partner B's hardware, lusearch could run but it failed to > converge > >> at warmup stage at every time. So the result is set to 0 in our result. > >> > >> And for sunflow case, it is in similar case like lusearch. Sunflow could > >> run but it failed to converge at most time. I've checked it succeeds to > >> converge only once in our result. So the standard deviation is 0 > because of > >> there are only one. I should have added note for this case. Sorry for > >> confusion. > > > > OK, so I think we have to reject all of the results on Partner B's > hardware > > because something is severely broken. > > > > Andrew. > > > -- Best regards, Zhongwei From aph at redhat.com Fri Apr 21 07:20:23 2017 From: aph at redhat.com (Andrew Haley) Date: Fri, 21 Apr 2017 08:20:23 +0100 Subject: [aarch64-port-dev ] aarch64 and arm64 jdk benchmarks result sharing In-Reply-To: References: <961e44d3-c1a0-d02b-5ef5-7847ab99cc16@redhat.com> <89264c5c-da92-dbc3-c547-d1473d692460@redhat.com> Message-ID: <1a843c34-d972-da74-0ac0-8b69ba1feda7@redhat.com> On 21/04/17 05:33, Zhongwei Yao wrote: > We updated kernel/firmware in one of the test machines, and the result of > these Dacapo benchmarks looks more stable, but still with relative high > standard deviation. OK, so it would be good to have some results. If there are repeatable slowdowns I'd like to see them. Please send me the firmware version info offlist. Thanks, Andrew. From ci_notify at linaro.org Sat Apr 22 19:07:04 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sat, 22 Apr 2017 19:07:04 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <599279461.2129.1492888025817.JavaMail.jenkins@90c74440cc95> 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/111/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/15 pass: 1,387; fail: 6 Build 1: aarch64/2017/mar/17 pass: 1,390; fail: 6 Build 2: aarch64/2017/mar/19 pass: 1,391; fail: 5 Build 3: aarch64/2017/mar/21 pass: 1,391; fail: 5 Build 4: aarch64/2017/mar/25 pass: 1,393; fail: 4 Build 5: aarch64/2017/mar/27 pass: 1,393; fail: 4 Build 6: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 7: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 8: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 9: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 10: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 11: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 12: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 13: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 14: aarch64/2017/apr/21 pass: 1,401; fail: 7 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/15 pass: 7,283; fail: 693; error: 25 Build 1: aarch64/2017/mar/17 pass: 7,273; fail: 709; error: 20 Build 2: aarch64/2017/mar/19 pass: 7,253; fail: 727; error: 24 Build 3: aarch64/2017/mar/21 pass: 7,294; fail: 689; error: 21 Build 4: aarch64/2017/mar/25 pass: 7,278; fail: 713; error: 23 Build 5: aarch64/2017/mar/27 pass: 7,304; fail: 690; error: 20 Build 6: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 7: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 8: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 9: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 10: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 11: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 12: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 13: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 14: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/15 pass: 3,874; error: 4 Build 1: aarch64/2017/mar/17 pass: 3,878; error: 2 Build 2: aarch64/2017/mar/19 pass: 3,878; error: 2 Build 3: aarch64/2017/mar/21 pass: 3,876; error: 5 Build 4: aarch64/2017/mar/25 pass: 3,886; fail: 1 Build 5: aarch64/2017/mar/27 pass: 3,883; error: 4 Build 6: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 7: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 8: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 9: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 10: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 11: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 12: aarch64/2017/apr/15 pass: 3,891 Build 13: aarch64/2017/apr/17 pass: 3,891 Build 14: aarch64/2017/apr/21 pass: 3,894; error: 2 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/15 pass: 1,392; fail: 5 Build 1: aarch64/2017/mar/17 pass: 1,395; fail: 5 Build 2: aarch64/2017/mar/19 pass: 1,395; fail: 5 Build 3: aarch64/2017/mar/21 pass: 1,394; fail: 6 Build 4: aarch64/2017/mar/25 pass: 1,397; fail: 4 Build 5: aarch64/2017/mar/27 pass: 1,396; fail: 5 Build 6: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 7: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 8: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 9: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 10: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 11: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 12: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 13: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 14: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/15 pass: 7,285; fail: 697; error: 19 Build 1: aarch64/2017/mar/17 pass: 7,278; fail: 703; error: 21 Build 2: aarch64/2017/mar/19 pass: 7,261; fail: 723; error: 20 Build 3: aarch64/2017/mar/21 pass: 7,271; fail: 712; error: 21 Build 4: aarch64/2017/mar/25 pass: 7,284; fail: 708; error: 22 Build 5: aarch64/2017/mar/27 pass: 7,297; fail: 695; error: 22 Build 6: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 7: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 8: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 9: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 10: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 11: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 12: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 13: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 14: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/15 pass: 3,878 Build 1: aarch64/2017/mar/17 pass: 3,876; error: 4 Build 2: aarch64/2017/mar/19 pass: 3,876; error: 4 Build 3: aarch64/2017/mar/21 pass: 3,879; error: 2 Build 4: aarch64/2017/mar/25 pass: 3,885; error: 2 Build 5: aarch64/2017/mar/27 pass: 3,881; error: 6 Build 6: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 7: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 8: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 9: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 10: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 11: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 12: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 13: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 14: aarch64/2017/apr/21 pass: 3,891; fail: 1; 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): 0.88x Relative performance: Server critical-jOPS (nc): 0.68x 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: 116.65 Client 70.93 / Client 2014-04-01 (43.00): 1.65x Server 116.65 / Server 2014-04-01 (71.00): 1.64x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/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-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/ 2017-03-26 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/084/results/ 2017-03-28 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/086/results/ 2017-03-31 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/089/results/ 2017-04-02 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/091/results/ 2017-04-04 pass rate: 11550/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/093/results/ 2017-04-08 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/097/results/ 2017-04-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/101/results/ 2017-04-14 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/103/results/ 2017-04-16 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/105/results/ 2017-04-18 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/107/results/ 2017-04-22 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/111/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/ From ci_notify at linaro.org Mon Apr 24 19:22:16 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Mon, 24 Apr 2017 19:22:16 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <1653988532.2541.1493061737626.JavaMail.jenkins@90c74440cc95> 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/113/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/17 pass: 1,390; fail: 6 Build 1: aarch64/2017/mar/19 pass: 1,391; fail: 5 Build 2: aarch64/2017/mar/21 pass: 1,391; fail: 5 Build 3: aarch64/2017/mar/25 pass: 1,393; fail: 4 Build 4: aarch64/2017/mar/27 pass: 1,393; fail: 4 Build 5: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 6: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 7: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 8: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 9: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 10: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 11: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 12: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 13: aarch64/2017/apr/21 pass: 1,401; fail: 7 Build 14: aarch64/2017/apr/23 pass: 1,400; fail: 7; error: 1 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/17 pass: 7,273; fail: 709; error: 20 Build 1: aarch64/2017/mar/19 pass: 7,253; fail: 727; error: 24 Build 2: aarch64/2017/mar/21 pass: 7,294; fail: 689; error: 21 Build 3: aarch64/2017/mar/25 pass: 7,278; fail: 713; error: 23 Build 4: aarch64/2017/mar/27 pass: 7,304; fail: 690; error: 20 Build 5: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 6: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 7: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 8: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 9: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 10: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 11: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 12: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 13: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 Build 14: aarch64/2017/apr/23 pass: 7,315; fail: 712; error: 25 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/17 pass: 3,878; error: 2 Build 1: aarch64/2017/mar/19 pass: 3,878; error: 2 Build 2: aarch64/2017/mar/21 pass: 3,876; error: 5 Build 3: aarch64/2017/mar/25 pass: 3,886; fail: 1 Build 4: aarch64/2017/mar/27 pass: 3,883; error: 4 Build 5: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 6: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 7: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 8: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 9: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 10: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 11: aarch64/2017/apr/15 pass: 3,891 Build 12: aarch64/2017/apr/17 pass: 3,891 Build 13: aarch64/2017/apr/21 pass: 3,894; error: 2 Build 14: aarch64/2017/apr/23 pass: 3,894; error: 3 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/17 pass: 1,395; fail: 5 Build 1: aarch64/2017/mar/19 pass: 1,395; fail: 5 Build 2: aarch64/2017/mar/21 pass: 1,394; fail: 6 Build 3: aarch64/2017/mar/25 pass: 1,397; fail: 4 Build 4: aarch64/2017/mar/27 pass: 1,396; fail: 5 Build 5: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 6: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 7: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 8: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 9: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 10: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 11: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 12: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 13: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 Build 14: aarch64/2017/apr/23 pass: 1,404; fail: 7; error: 1 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/17 pass: 7,278; fail: 703; error: 21 Build 1: aarch64/2017/mar/19 pass: 7,261; fail: 723; error: 20 Build 2: aarch64/2017/mar/21 pass: 7,271; fail: 712; error: 21 Build 3: aarch64/2017/mar/25 pass: 7,284; fail: 708; error: 22 Build 4: aarch64/2017/mar/27 pass: 7,297; fail: 695; error: 22 Build 5: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 6: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 7: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 8: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 9: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 10: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 11: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 12: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 13: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 Build 14: aarch64/2017/apr/23 pass: 7,315; fail: 716; error: 21 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/17 pass: 3,876; error: 4 Build 1: aarch64/2017/mar/19 pass: 3,876; error: 4 Build 2: aarch64/2017/mar/21 pass: 3,879; error: 2 Build 3: aarch64/2017/mar/25 pass: 3,885; error: 2 Build 4: aarch64/2017/mar/27 pass: 3,881; error: 6 Build 5: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 6: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 7: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 8: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 9: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 10: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 11: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 12: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 13: aarch64/2017/apr/21 pass: 3,891; fail: 1; error: 4 Build 14: aarch64/2017/apr/23 pass: 3,893; 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): 0.88x Relative performance: Server critical-jOPS (nc): 0.74x 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.58, Server: 111.14 Client 70.58 / Client 2014-04-01 (43.00): 1.64x Server 111.14 / Server 2014-04-01 (71.00): 1.57x 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-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/ 2017-03-26 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/084/results/ 2017-03-28 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/086/results/ 2017-03-31 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/089/results/ 2017-04-02 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/091/results/ 2017-04-04 pass rate: 11550/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/093/results/ 2017-04-08 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/097/results/ 2017-04-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/101/results/ 2017-04-14 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/103/results/ 2017-04-16 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/105/results/ 2017-04-18 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/107/results/ 2017-04-22 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/111/results/ 2017-04-24 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/113/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/ From ci_notify at linaro.org Wed Apr 26 19:30:18 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Wed, 26 Apr 2017 19:30:18 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <2094671394.3339.1493235020112.JavaMail.jenkins@90c74440cc95> 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/115/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/19 pass: 1,391; fail: 5 Build 1: aarch64/2017/mar/21 pass: 1,391; fail: 5 Build 2: aarch64/2017/mar/25 pass: 1,393; fail: 4 Build 3: aarch64/2017/mar/27 pass: 1,393; fail: 4 Build 4: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 5: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 6: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 7: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 8: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 9: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 10: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 11: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 12: aarch64/2017/apr/21 pass: 1,401; fail: 7 Build 13: aarch64/2017/apr/23 pass: 1,400; fail: 7; error: 1 Build 14: aarch64/2017/apr/25 pass: 1,401; fail: 7 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/19 pass: 7,253; fail: 727; error: 24 Build 1: aarch64/2017/mar/21 pass: 7,294; fail: 689; error: 21 Build 2: aarch64/2017/mar/25 pass: 7,278; fail: 713; error: 23 Build 3: aarch64/2017/mar/27 pass: 7,304; fail: 690; error: 20 Build 4: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 5: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 6: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 7: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 8: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 9: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 10: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 11: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 12: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 Build 13: aarch64/2017/apr/23 pass: 7,315; fail: 712; error: 25 Build 14: aarch64/2017/apr/25 pass: 7,341; fail: 689; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/19 pass: 3,878; error: 2 Build 1: aarch64/2017/mar/21 pass: 3,876; error: 5 Build 2: aarch64/2017/mar/25 pass: 3,886; fail: 1 Build 3: aarch64/2017/mar/27 pass: 3,883; error: 4 Build 4: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 5: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 6: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 7: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 8: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 9: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 10: aarch64/2017/apr/15 pass: 3,891 Build 11: aarch64/2017/apr/17 pass: 3,891 Build 12: aarch64/2017/apr/21 pass: 3,894; error: 2 Build 13: aarch64/2017/apr/23 pass: 3,894; error: 3 Build 14: aarch64/2017/apr/25 pass: 3,895; error: 4 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/19 pass: 1,395; fail: 5 Build 1: aarch64/2017/mar/21 pass: 1,394; fail: 6 Build 2: aarch64/2017/mar/25 pass: 1,397; fail: 4 Build 3: aarch64/2017/mar/27 pass: 1,396; fail: 5 Build 4: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 5: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 6: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 7: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 8: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 9: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 10: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 11: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 12: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 Build 13: aarch64/2017/apr/23 pass: 1,404; fail: 7; error: 1 Build 14: aarch64/2017/apr/25 pass: 1,405; fail: 7 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/19 pass: 7,261; fail: 723; error: 20 Build 1: aarch64/2017/mar/21 pass: 7,271; fail: 712; error: 21 Build 2: aarch64/2017/mar/25 pass: 7,284; fail: 708; error: 22 Build 3: aarch64/2017/mar/27 pass: 7,297; fail: 695; error: 22 Build 4: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 5: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 6: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 7: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 8: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 9: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 10: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 11: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 12: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 Build 13: aarch64/2017/apr/23 pass: 7,315; fail: 716; error: 21 Build 14: aarch64/2017/apr/25 pass: 7,319; fail: 709; error: 25 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/19 pass: 3,876; error: 4 Build 1: aarch64/2017/mar/21 pass: 3,879; error: 2 Build 2: aarch64/2017/mar/25 pass: 3,885; error: 2 Build 3: aarch64/2017/mar/27 pass: 3,881; error: 6 Build 4: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 5: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 6: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 7: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 8: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 9: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 10: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 11: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 12: aarch64/2017/apr/21 pass: 3,891; fail: 1; error: 4 Build 13: aarch64/2017/apr/23 pass: 3,893; error: 4 Build 14: aarch64/2017/apr/25 pass: 3,895; 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): 0.29x Relative performance: Server critical-jOPS (nc): 0.68x 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: 69.19, Server: 107.75 Client 69.19 / Client 2014-04-01 (43.00): 1.61x Server 107.75 / Server 2014-04-01 (71.00): 1.52x 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-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/ 2017-03-26 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/084/results/ 2017-03-28 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/086/results/ 2017-03-31 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/089/results/ 2017-04-02 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/091/results/ 2017-04-04 pass rate: 11550/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/093/results/ 2017-04-08 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/097/results/ 2017-04-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/101/results/ 2017-04-14 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/103/results/ 2017-04-16 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/105/results/ 2017-04-18 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/107/results/ 2017-04-22 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/111/results/ 2017-04-24 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/113/results/ 2017-04-26 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/115/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/ From rwestrel at redhat.com Fri Apr 28 10:58:08 2017 From: rwestrel at redhat.com (Roland Westrelin) Date: Fri, 28 Apr 2017 12:58:08 +0200 Subject: [aarch64-port-dev ] [10] RFR(XS): 8169697: aarch64: vectorized MLA instruction not generated for some test cases In-Reply-To: References: <15b3b2dc-481f-98fd-c7db-f72f58d970e1@oracle.com> Message-ID: > The patch has been updated in > http://cr.openjdk.java.net/~njian/8169697/webrev.01/. That patch looks good to me. Can we have a sponsor for it (in jdk 10)? Roland. From ci_notify at linaro.org Fri Apr 28 20:43:57 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 28 Apr 2017 20:43:57 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <1676193223.3702.1493412239108.JavaMail.jenkins@90c74440cc95> 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/117/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/21 pass: 1,391; fail: 5 Build 1: aarch64/2017/mar/25 pass: 1,393; fail: 4 Build 2: aarch64/2017/mar/27 pass: 1,393; fail: 4 Build 3: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 4: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 5: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 6: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 7: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 8: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 9: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 10: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 11: aarch64/2017/apr/21 pass: 1,401; fail: 7 Build 12: aarch64/2017/apr/23 pass: 1,400; fail: 7; error: 1 Build 13: aarch64/2017/apr/25 pass: 1,401; fail: 7 Build 14: aarch64/2017/apr/27 pass: 1,400; fail: 8; error: 1 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/21 pass: 7,294; fail: 689; error: 21 Build 1: aarch64/2017/mar/25 pass: 7,278; fail: 713; error: 23 Build 2: aarch64/2017/mar/27 pass: 7,304; fail: 690; error: 20 Build 3: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 4: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 5: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 6: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 7: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 8: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 9: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 10: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 11: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 Build 12: aarch64/2017/apr/23 pass: 7,315; fail: 712; error: 25 Build 13: aarch64/2017/apr/25 pass: 7,341; fail: 689; error: 23 Build 14: aarch64/2017/apr/27 pass: 7,320; fail: 710; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/21 pass: 3,876; error: 5 Build 1: aarch64/2017/mar/25 pass: 3,886; fail: 1 Build 2: aarch64/2017/mar/27 pass: 3,883; error: 4 Build 3: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 4: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 5: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 6: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 7: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 8: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 9: aarch64/2017/apr/15 pass: 3,891 Build 10: aarch64/2017/apr/17 pass: 3,891 Build 11: aarch64/2017/apr/21 pass: 3,894; error: 2 Build 12: aarch64/2017/apr/23 pass: 3,894; error: 3 Build 13: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 14: aarch64/2017/apr/27 pass: 3,896; fail: 1; error: 4 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/21 pass: 1,394; fail: 6 Build 1: aarch64/2017/mar/25 pass: 1,397; fail: 4 Build 2: aarch64/2017/mar/27 pass: 1,396; fail: 5 Build 3: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 4: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 5: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 6: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 7: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 8: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 9: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 10: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 11: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 Build 12: aarch64/2017/apr/23 pass: 1,404; fail: 7; error: 1 Build 13: aarch64/2017/apr/25 pass: 1,405; fail: 7 Build 14: aarch64/2017/apr/27 pass: 1,405; fail: 7; error: 1 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/21 pass: 7,271; fail: 712; error: 21 Build 1: aarch64/2017/mar/25 pass: 7,284; fail: 708; error: 22 Build 2: aarch64/2017/mar/27 pass: 7,297; fail: 695; error: 22 Build 3: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 4: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 5: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 6: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 7: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 8: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 9: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 10: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 11: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 Build 12: aarch64/2017/apr/23 pass: 7,315; fail: 716; error: 21 Build 13: aarch64/2017/apr/25 pass: 7,319; fail: 709; error: 25 Build 14: aarch64/2017/apr/27 pass: 7,324; fail: 701; error: 28 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/21 pass: 3,879; error: 2 Build 1: aarch64/2017/mar/25 pass: 3,885; error: 2 Build 2: aarch64/2017/mar/27 pass: 3,881; error: 6 Build 3: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 4: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 5: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 6: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 7: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 8: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 9: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 10: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 11: aarch64/2017/apr/21 pass: 3,891; fail: 1; error: 4 Build 12: aarch64/2017/apr/23 pass: 3,893; error: 4 Build 13: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 14: aarch64/2017/apr/27 pass: 3,893; error: 8 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): 0.85x Relative performance: Server critical-jOPS (nc): 0.71x 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: 69.53, Server: 113.83 Client 69.53 / Client 2014-04-01 (43.00): 1.62x Server 113.83 / Server 2014-04-01 (71.00): 1.60x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/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-03-22 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/080/results/ 2017-03-26 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/084/results/ 2017-03-28 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/086/results/ 2017-03-31 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/089/results/ 2017-04-02 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/091/results/ 2017-04-04 pass rate: 11550/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/093/results/ 2017-04-08 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/097/results/ 2017-04-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/101/results/ 2017-04-14 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/103/results/ 2017-04-16 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/105/results/ 2017-04-18 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/107/results/ 2017-04-22 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/111/results/ 2017-04-24 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/113/results/ 2017-04-26 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/115/results/ 2017-04-28 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/117/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/ From ci_notify at linaro.org Sun Apr 30 20:40:00 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sun, 30 Apr 2017 20:40:00 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <2109967721.44.1493584801975.JavaMail.jenkins@53c6d05e7b7b> 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/119/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/25 pass: 1,393; fail: 4 Build 1: aarch64/2017/mar/27 pass: 1,393; fail: 4 Build 2: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 3: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 4: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 5: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 6: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 7: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 8: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 9: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 10: aarch64/2017/apr/21 pass: 1,401; fail: 7 Build 11: aarch64/2017/apr/23 pass: 1,400; fail: 7; error: 1 Build 12: aarch64/2017/apr/25 pass: 1,401; fail: 7 Build 13: aarch64/2017/apr/27 pass: 1,400; fail: 8; error: 1 Build 14: aarch64/2017/apr/29 pass: 1,401; fail: 7; error: 1 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/25 pass: 7,278; fail: 713; error: 23 Build 1: aarch64/2017/mar/27 pass: 7,304; fail: 690; error: 20 Build 2: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 3: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 4: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 5: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 6: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 7: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 8: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 9: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 10: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 Build 11: aarch64/2017/apr/23 pass: 7,315; fail: 712; error: 25 Build 12: aarch64/2017/apr/25 pass: 7,341; fail: 689; error: 23 Build 13: aarch64/2017/apr/27 pass: 7,320; fail: 710; error: 23 Build 14: aarch64/2017/apr/29 pass: 7,293; fail: 729; error: 32 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/25 pass: 3,886; fail: 1 Build 1: aarch64/2017/mar/27 pass: 3,883; error: 4 Build 2: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 3: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 4: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 5: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 6: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 7: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 8: aarch64/2017/apr/15 pass: 3,891 Build 9: aarch64/2017/apr/17 pass: 3,891 Build 10: aarch64/2017/apr/21 pass: 3,894; error: 2 Build 11: aarch64/2017/apr/23 pass: 3,894; error: 3 Build 12: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 13: aarch64/2017/apr/27 pass: 3,896; fail: 1; error: 4 Build 14: aarch64/2017/apr/29 pass: 3,899; error: 2 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/25 pass: 1,397; fail: 4 Build 1: aarch64/2017/mar/27 pass: 1,396; fail: 5 Build 2: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 3: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 4: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 5: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 6: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 7: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 8: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 9: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 10: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 Build 11: aarch64/2017/apr/23 pass: 1,404; fail: 7; error: 1 Build 12: aarch64/2017/apr/25 pass: 1,405; fail: 7 Build 13: aarch64/2017/apr/27 pass: 1,405; fail: 7; error: 1 Build 14: aarch64/2017/apr/29 pass: 1,406; fail: 7 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/25 pass: 7,284; fail: 708; error: 22 Build 1: aarch64/2017/mar/27 pass: 7,297; fail: 695; error: 22 Build 2: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 3: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 4: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 5: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 6: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 7: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 8: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 9: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 10: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 Build 11: aarch64/2017/apr/23 pass: 7,315; fail: 716; error: 21 Build 12: aarch64/2017/apr/25 pass: 7,319; fail: 709; error: 25 Build 13: aarch64/2017/apr/27 pass: 7,324; fail: 701; error: 28 Build 14: aarch64/2017/apr/29 pass: 7,340; fail: 686; error: 28 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/25 pass: 3,885; error: 2 Build 1: aarch64/2017/mar/27 pass: 3,881; error: 6 Build 2: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 3: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 4: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 5: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 6: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 7: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 8: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 9: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 10: aarch64/2017/apr/21 pass: 3,891; fail: 1; error: 4 Build 11: aarch64/2017/apr/23 pass: 3,893; error: 4 Build 12: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 13: aarch64/2017/apr/27 pass: 3,893; error: 8 Build 14: aarch64/2017/apr/29 pass: 3,896; error: 5 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): 0.88x Relative performance: Server critical-jOPS (nc): 0.73x 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: 71.29, Server: 112.92 Client 71.29 / Client 2014-04-01 (43.00): 1.66x Server 112.92 / Server 2014-04-01 (71.00): 1.59x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/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-03-26 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/084/results/ 2017-03-28 pass rate: 10524/11284, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/086/results/ 2017-03-31 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/089/results/ 2017-04-02 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/091/results/ 2017-04-04 pass rate: 11550/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/093/results/ 2017-04-08 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/097/results/ 2017-04-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/101/results/ 2017-04-14 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/103/results/ 2017-04-16 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/105/results/ 2017-04-18 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/107/results/ 2017-04-22 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/111/results/ 2017-04-24 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/113/results/ 2017-04-26 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/115/results/ 2017-04-28 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/117/results/ 2017-04-30 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/119/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/