From vladimir.kozlov at oracle.com Tue May 2 17:43:01 2017 From: vladimir.kozlov at oracle.com (Vladimir Kozlov) Date: Tue, 2 May 2017 10:43:01 -0700 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: <78d865ac-c85f-988d-f63e-7f0f65ff43f9@oracle.com> Changes look fine to me. I will run RBT testing but it only covers platforms supported by Oracle. You have to test it on other platforms. thanks, Vladimir On 4/28/17 3:58 AM, Roland Westrelin wrote: > >> 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 rwestrel at redhat.com Wed May 3 08:05:38 2017 From: rwestrel at redhat.com (Roland Westrelin) Date: Wed, 03 May 2017 10:05:38 +0200 Subject: [aarch64-port-dev ] [10] RFR(XS): 8169697: aarch64: vectorized MLA instruction not generated for some test cases In-Reply-To: <78d865ac-c85f-988d-f63e-7f0f65ff43f9@oracle.com> References: <15b3b2dc-481f-98fd-c7db-f72f58d970e1@oracle.com> <78d865ac-c85f-988d-f63e-7f0f65ff43f9@oracle.com> Message-ID: > Changes look fine to me. > > I will run RBT testing but it only covers platforms supported by > Oracle. You have to test it on other platforms. Sure. Thanks, Vladimir! Roland. From vladimir.kozlov at oracle.com Wed May 3 19:05:33 2017 From: vladimir.kozlov at oracle.com (Vladimir Kozlov) Date: Wed, 3 May 2017 12:05:33 -0700 Subject: [aarch64-port-dev ] [10] RFR(XS): 8169697: aarch64: vectorized MLA instruction not generated for some test cases In-Reply-To: <78d865ac-c85f-988d-f63e-7f0f65ff43f9@oracle.com> References: <15b3b2dc-481f-98fd-c7db-f72f58d970e1@oracle.com> <78d865ac-c85f-988d-f63e-7f0f65ff43f9@oracle.com> Message-ID: <65c075cd-6837-984d-db82-2d884b68052b@oracle.com> Testing passed. I will sponsor it after latest jdk10/jdk10 integrated into jdk10/hs today. Vladimir On 5/2/17 10:43 AM, Vladimir Kozlov wrote: > Changes look fine to me. > > I will run RBT testing but it only covers platforms supported by Oracle. You have to test it on other platforms. > > thanks, > Vladimir > > On 4/28/17 3:58 AM, Roland Westrelin wrote: >> >>> 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 ningsheng.jian at linaro.org Thu May 4 02:23:08 2017 From: ningsheng.jian at linaro.org (Ningsheng Jian) Date: Thu, 4 May 2017 10:23:08 +0800 Subject: [aarch64-port-dev ] [10] RFR(XS): 8169697: aarch64: vectorized MLA instruction not generated for some test cases In-Reply-To: <65c075cd-6837-984d-db82-2d884b68052b@oracle.com> References: <15b3b2dc-481f-98fd-c7db-f72f58d970e1@oracle.com> <78d865ac-c85f-988d-f63e-7f0f65ff43f9@oracle.com> <65c075cd-6837-984d-db82-2d884b68052b@oracle.com> Message-ID: Thanks, Vladimir and Roland! This patch has been contributed by yang.zhang at linaro.org. I updated this information in the commit message. Regards, Ningsheng On 4 May 2017 at 03:05, Vladimir Kozlov wrote: > Testing passed. I will sponsor it after latest jdk10/jdk10 integrated into > jdk10/hs today. > > Vladimir > > > On 5/2/17 10:43 AM, Vladimir Kozlov wrote: >> >> Changes look fine to me. >> >> I will run RBT testing but it only covers platforms supported by Oracle. >> You have to test it on other platforms. >> >> thanks, >> Vladimir >> >> On 4/28/17 3:58 AM, Roland Westrelin wrote: >>> >>> >>>> 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 Sat May 6 18:45:07 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sat, 6 May 2017 18:45:07 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <1955633073.891.1494096309515.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/125/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/27 pass: 1,393; fail: 4 Build 1: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 2: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 3: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 4: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 5: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 6: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 7: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 8: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 9: aarch64/2017/apr/21 pass: 1,401; fail: 7 Build 10: aarch64/2017/apr/23 pass: 1,400; fail: 7; error: 1 Build 11: aarch64/2017/apr/25 pass: 1,401; fail: 7 Build 12: aarch64/2017/apr/27 pass: 1,400; fail: 8; error: 1 Build 13: aarch64/2017/apr/29 pass: 1,401; fail: 7; error: 1 Build 14: aarch64/2017/may/05 pass: 1,402; fail: 7 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/27 pass: 7,304; fail: 690; error: 20 Build 1: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 2: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 3: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 4: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 5: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 6: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 7: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 8: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 9: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 Build 10: aarch64/2017/apr/23 pass: 7,315; fail: 712; error: 25 Build 11: aarch64/2017/apr/25 pass: 7,341; fail: 689; error: 23 Build 12: aarch64/2017/apr/27 pass: 7,320; fail: 710; error: 23 Build 13: aarch64/2017/apr/29 pass: 7,293; fail: 729; error: 32 Build 14: aarch64/2017/may/05 pass: 7,319; fail: 711; error: 28 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/27 pass: 3,883; error: 4 Build 1: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 2: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 3: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 4: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 5: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 6: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 7: aarch64/2017/apr/15 pass: 3,891 Build 8: aarch64/2017/apr/17 pass: 3,891 Build 9: aarch64/2017/apr/21 pass: 3,894; error: 2 Build 10: aarch64/2017/apr/23 pass: 3,894; error: 3 Build 11: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 12: aarch64/2017/apr/27 pass: 3,896; fail: 1; error: 4 Build 13: aarch64/2017/apr/29 pass: 3,899; error: 2 Build 14: aarch64/2017/may/05 pass: 3,897; error: 4 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/27 pass: 1,396; fail: 5 Build 1: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 2: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 3: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 4: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 5: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 6: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 7: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 8: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 9: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 Build 10: aarch64/2017/apr/23 pass: 1,404; fail: 7; error: 1 Build 11: aarch64/2017/apr/25 pass: 1,405; fail: 7 Build 12: aarch64/2017/apr/27 pass: 1,405; fail: 7; error: 1 Build 13: aarch64/2017/apr/29 pass: 1,406; fail: 7 Build 14: aarch64/2017/may/05 pass: 1,406; fail: 7 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/27 pass: 7,297; fail: 695; error: 22 Build 1: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 2: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 3: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 4: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 5: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 6: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 7: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 8: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 9: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 Build 10: aarch64/2017/apr/23 pass: 7,315; fail: 716; error: 21 Build 11: aarch64/2017/apr/25 pass: 7,319; fail: 709; error: 25 Build 12: aarch64/2017/apr/27 pass: 7,324; fail: 701; error: 28 Build 13: aarch64/2017/apr/29 pass: 7,340; fail: 686; error: 28 Build 14: aarch64/2017/may/05 pass: 7,332; fail: 702; error: 24 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/27 pass: 3,881; error: 6 Build 1: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 2: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 3: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 4: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 5: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 6: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 7: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 8: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 9: aarch64/2017/apr/21 pass: 3,891; fail: 1; error: 4 Build 10: aarch64/2017/apr/23 pass: 3,893; error: 4 Build 11: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 12: aarch64/2017/apr/27 pass: 3,893; error: 8 Build 13: aarch64/2017/apr/29 pass: 3,896; error: 5 Build 14: aarch64/2017/may/05 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.29x 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: 70.22, Server: 116.65 Client 70.22 / Client 2014-04-01 (43.00): 1.63x 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-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/ 2017-05-06 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/125/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 Tue May 9 16:59:18 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Tue, 9 May 2017 16:59:18 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <1981206017.1030.1494349160199.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/127/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/30 pass: 1,393; fail: 4 Build 1: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 2: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 3: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 4: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 5: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 6: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 7: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 8: aarch64/2017/apr/21 pass: 1,401; fail: 7 Build 9: aarch64/2017/apr/23 pass: 1,400; fail: 7; error: 1 Build 10: aarch64/2017/apr/25 pass: 1,401; fail: 7 Build 11: aarch64/2017/apr/27 pass: 1,400; fail: 8; error: 1 Build 12: aarch64/2017/apr/29 pass: 1,401; fail: 7; error: 1 Build 13: aarch64/2017/may/05 pass: 1,402; fail: 7 Build 14: aarch64/2017/may/07 pass: 1,402; fail: 7 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/30 pass: 7,302; fail: 691; error: 23 Build 1: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 2: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 3: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 4: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 5: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 6: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 7: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 8: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 Build 9: aarch64/2017/apr/23 pass: 7,315; fail: 712; error: 25 Build 10: aarch64/2017/apr/25 pass: 7,341; fail: 689; error: 23 Build 11: aarch64/2017/apr/27 pass: 7,320; fail: 710; error: 23 Build 12: aarch64/2017/apr/29 pass: 7,293; fail: 729; error: 32 Build 13: aarch64/2017/may/05 pass: 7,319; fail: 711; error: 28 Build 14: aarch64/2017/may/07 pass: 7,331; fail: 701; error: 26 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/30 pass: 3,883; fail: 3; error: 1 Build 1: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 2: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 3: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 4: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 5: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 6: aarch64/2017/apr/15 pass: 3,891 Build 7: aarch64/2017/apr/17 pass: 3,891 Build 8: aarch64/2017/apr/21 pass: 3,894; error: 2 Build 9: aarch64/2017/apr/23 pass: 3,894; error: 3 Build 10: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 11: aarch64/2017/apr/27 pass: 3,896; fail: 1; error: 4 Build 12: aarch64/2017/apr/29 pass: 3,899; error: 2 Build 13: aarch64/2017/may/05 pass: 3,897; error: 4 Build 14: aarch64/2017/may/07 pass: 3,895; error: 6 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/30 pass: 1,397; fail: 4 Build 1: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 2: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 3: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 4: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 5: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 6: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 7: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 8: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 Build 9: aarch64/2017/apr/23 pass: 1,404; fail: 7; error: 1 Build 10: aarch64/2017/apr/25 pass: 1,405; fail: 7 Build 11: aarch64/2017/apr/27 pass: 1,405; fail: 7; error: 1 Build 12: aarch64/2017/apr/29 pass: 1,406; fail: 7 Build 13: aarch64/2017/may/05 pass: 1,406; fail: 7 Build 14: aarch64/2017/may/07 pass: 1,405; fail: 7; error: 1 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/30 pass: 7,294; fail: 701; error: 21 Build 1: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 2: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 3: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 4: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 5: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 6: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 7: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 8: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 Build 9: aarch64/2017/apr/23 pass: 7,315; fail: 716; error: 21 Build 10: aarch64/2017/apr/25 pass: 7,319; fail: 709; error: 25 Build 11: aarch64/2017/apr/27 pass: 7,324; fail: 701; error: 28 Build 12: aarch64/2017/apr/29 pass: 7,340; fail: 686; error: 28 Build 13: aarch64/2017/may/05 pass: 7,332; fail: 702; error: 24 Build 14: aarch64/2017/may/07 pass: 7,350; fail: 687; error: 21 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/mar/30 pass: 3,879; fail: 2; error: 6 Build 1: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 2: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 3: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 4: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 5: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 6: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 7: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 8: aarch64/2017/apr/21 pass: 3,891; fail: 1; error: 4 Build 9: aarch64/2017/apr/23 pass: 3,893; error: 4 Build 10: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 11: aarch64/2017/apr/27 pass: 3,893; error: 8 Build 12: aarch64/2017/apr/29 pass: 3,896; error: 5 Build 13: aarch64/2017/may/05 pass: 3,896; error: 5 Build 14: aarch64/2017/may/07 pass: 3,895; fail: 1; 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.30x Relative performance: Server critical-jOPS (nc): 0.72x 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: 68.52, Server: 112.02 Client 68.52 / Client 2014-04-01 (43.00): 1.59x Server 112.02 / Server 2014-04-01 (71.00): 1.58x 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-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/ 2017-05-06 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/125/results/ 2017-05-09 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/127/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 Thu May 11 00:23:24 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Thu, 11 May 2017 00:23:24 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <1713338055.1157.1494462205844.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/129/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/01 pass: 1,396; fail: 4 Build 1: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 2: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 3: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 4: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 5: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 6: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 7: aarch64/2017/apr/21 pass: 1,401; fail: 7 Build 8: aarch64/2017/apr/23 pass: 1,400; fail: 7; error: 1 Build 9: aarch64/2017/apr/25 pass: 1,401; fail: 7 Build 10: aarch64/2017/apr/27 pass: 1,400; fail: 8; error: 1 Build 11: aarch64/2017/apr/29 pass: 1,401; fail: 7; error: 1 Build 12: aarch64/2017/may/05 pass: 1,402; fail: 7 Build 13: aarch64/2017/may/07 pass: 1,402; fail: 7 Build 14: aarch64/2017/may/09 pass: 1,401; fail: 7; error: 1 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/01 pass: 7,289; fail: 704; error: 23 Build 1: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 2: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 3: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 4: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 5: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 6: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 7: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 Build 8: aarch64/2017/apr/23 pass: 7,315; fail: 712; error: 25 Build 9: aarch64/2017/apr/25 pass: 7,341; fail: 689; error: 23 Build 10: aarch64/2017/apr/27 pass: 7,320; fail: 710; error: 23 Build 11: aarch64/2017/apr/29 pass: 7,293; fail: 729; error: 32 Build 12: aarch64/2017/may/05 pass: 7,319; fail: 711; error: 28 Build 13: aarch64/2017/may/07 pass: 7,331; fail: 701; error: 26 Build 14: aarch64/2017/may/09 pass: 7,326; fail: 702; error: 31 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/01 pass: 3,885; fail: 3 Build 1: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 2: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 3: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 4: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 5: aarch64/2017/apr/15 pass: 3,891 Build 6: aarch64/2017/apr/17 pass: 3,891 Build 7: aarch64/2017/apr/21 pass: 3,894; error: 2 Build 8: aarch64/2017/apr/23 pass: 3,894; error: 3 Build 9: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 10: aarch64/2017/apr/27 pass: 3,896; fail: 1; error: 4 Build 11: aarch64/2017/apr/29 pass: 3,899; error: 2 Build 12: aarch64/2017/may/05 pass: 3,897; error: 4 Build 13: aarch64/2017/may/07 pass: 3,895; error: 6 Build 14: aarch64/2017/may/09 pass: 3,897; error: 5 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/01 pass: 1,400; fail: 4 Build 1: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 2: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 3: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 4: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 5: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 6: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 7: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 Build 8: aarch64/2017/apr/23 pass: 1,404; fail: 7; error: 1 Build 9: aarch64/2017/apr/25 pass: 1,405; fail: 7 Build 10: aarch64/2017/apr/27 pass: 1,405; fail: 7; error: 1 Build 11: aarch64/2017/apr/29 pass: 1,406; fail: 7 Build 12: aarch64/2017/may/05 pass: 1,406; fail: 7 Build 13: aarch64/2017/may/07 pass: 1,405; fail: 7; error: 1 Build 14: aarch64/2017/may/09 pass: 1,406; fail: 7 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/01 pass: 7,305; fail: 686; error: 25 Build 1: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 2: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 3: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 4: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 5: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 6: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 7: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 Build 8: aarch64/2017/apr/23 pass: 7,315; fail: 716; error: 21 Build 9: aarch64/2017/apr/25 pass: 7,319; fail: 709; error: 25 Build 10: aarch64/2017/apr/27 pass: 7,324; fail: 701; error: 28 Build 11: aarch64/2017/apr/29 pass: 7,340; fail: 686; error: 28 Build 12: aarch64/2017/may/05 pass: 7,332; fail: 702; error: 24 Build 13: aarch64/2017/may/07 pass: 7,350; fail: 687; error: 21 Build 14: aarch64/2017/may/09 pass: 7,352; fail: 681; error: 26 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/01 pass: 3,884; fail: 2; error: 2 Build 1: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 2: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 3: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 4: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 5: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 6: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 7: aarch64/2017/apr/21 pass: 3,891; fail: 1; error: 4 Build 8: aarch64/2017/apr/23 pass: 3,893; error: 4 Build 9: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 10: aarch64/2017/apr/27 pass: 3,893; error: 8 Build 11: aarch64/2017/apr/29 pass: 3,896; error: 5 Build 12: aarch64/2017/may/05 pass: 3,896; error: 5 Build 13: aarch64/2017/may/07 pass: 3,895; fail: 1; error: 5 Build 14: aarch64/2017/may/09 pass: 3,896; fail: 1; 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.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: 67.86, Server: 108.58 Client 67.86 / Client 2014-04-01 (43.00): 1.58x Server 108.58 / Server 2014-04-01 (71.00): 1.53x 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-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/ 2017-05-06 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/125/results/ 2017-05-09 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/127/results/ 2017-05-11 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/129/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 Thu May 11 10:07:37 2017 From: zhongwei.yao at linaro.org (Zhongwei Yao) Date: Thu, 11 May 2017 18:07:37 +0800 Subject: [aarch64-port-dev ] RFR: 8179933: aarch64: incorrect match rule for immL_63 and immL_255 Message-ID: Hi, For now, "SubExtL_uxtb_and" instruction can not match following code: x -= (y & 255) where x and y are both long type integer due to incorrect rule definition of immL_255. Similar issue exists for immL_63. Bug: https://bugs.openjdk.java.net/browse/JDK-8179933 Webrev: http://cr.openjdk.java.net/~njian/8179933/webrev.00/ Please help to review it. -- Best regards, Zhongwei From aph at redhat.com Thu May 11 10:30:47 2017 From: aph at redhat.com (Andrew Haley) Date: Thu, 11 May 2017 11:30:47 +0100 Subject: [aarch64-port-dev ] RFR: 8179933: aarch64: incorrect match rule for immL_63 and immL_255 In-Reply-To: References: Message-ID: <88066719-4ac8-90c9-b0ac-60efbc326d31@redhat.com> On 11/05/17 11:07, Zhongwei Yao wrote: > Bug: > https://bugs.openjdk.java.net/browse/JDK-8179933 > > Webrev: > http://cr.openjdk.java.net/~njian/8179933/webrev.00/ Did you run a test case to see the difference in the generated code? If so, you should provide it. Andrew. From Derek.White at cavium.com Thu May 11 17:20:08 2017 From: Derek.White at cavium.com (White, Derek) Date: Thu, 11 May 2017 17:20:08 +0000 Subject: [aarch64-port-dev ] [OpenJDK8u] java.nio.Bits.unaligned() doesn't handle aarch64 Message-ID: In aarch64-port/jdk8u, java.nio.Bits.unaligned() only returns true for x86(s). This ends up being important because Apache Spark uses Bits.unaligned() to decide if it can use off-heap memory or not. In mainline jdk8u, this was updated to include PPC as well (See https://bugs.openjdk.java.net/browse/JDK-8165231). JDK9 has a much better fix that supports aarch64 already. Tested on Spark and off-heap memory was being used. Note: The PPC fix also patched sun/security/provider/ByteArrayAccess.java, but I didn't include this in the patch below (not sure if it matters, or how to test it). This is my first attempt at an aarch64-jdk8u patch. Please let me know if I'm not following protocol correctly. Thanks, - Derek Patch follows (in jdk/src). --- old/src/share/classes/java/nio/Bits.java 2017-05-11 13:10:31.916219496 -0400 +++ new/src/share/classes/java/nio/Bits.java 2017-05-11 13:10:31.832221728 -0400 @@ -614,7 +614,9 @@ String arch = AccessController.doPrivileged( new sun.security.action.GetPropertyAction("os.arch")); unaligned = arch.equals("i386") || arch.equals("x86") - || arch.equals("amd64") || arch.equals("x86_64"); + || arch.equals("amd64") || arch.equals("x86_64") + || arch.equals("ppc64") || arch.equals("ppc64le") + || arch.equals("aarch64"); unalignedKnown = true; return unaligned; } From aph at redhat.com Thu May 11 19:40:39 2017 From: aph at redhat.com (Andrew Haley) Date: Thu, 11 May 2017 20:40:39 +0100 Subject: [aarch64-port-dev ] [OpenJDK8u] java.nio.Bits.unaligned() doesn't handle aarch64 In-Reply-To: References: Message-ID: <63c8f30a-0408-cec6-9c9d-f99e7a3cffd2@redhat.com> On 11/05/17 18:20, White, Derek wrote: > In mainline jdk8u, this was updated to include PPC as well (See > https://bugs.openjdk.java.net/browse/JDK-8165231). JDK9 has a much > better fix that supports aarch64 already. > > Tested on Spark and off-heap memory was being used. Note: The PPC > fix also patched sun/security/provider/ByteArrayAccess.java, but I > didn't include this in the patch below (not sure if it matters, or > how to test it). It's not a great idea to introduce a patch that will conflict with a patch we haven't yet merged. We will get all the patches from jdk8u eventually, but we only merge from security updates and peroper releases. I think we should add aarch64 support now, given that upstream jdk8u will never support it. Andrew. From Derek.White at cavium.com Thu May 11 20:38:48 2017 From: Derek.White at cavium.com (White, Derek) Date: Thu, 11 May 2017 20:38:48 +0000 Subject: [aarch64-port-dev ] [OpenJDK8u] java.nio.Bits.unaligned() doesn't handle aarch64 In-Reply-To: <63c8f30a-0408-cec6-9c9d-f99e7a3cffd2@redhat.com> References: <63c8f30a-0408-cec6-9c9d-f99e7a3cffd2@redhat.com> Message-ID: Hi Andrew, No problem, but I'm not sure if you want me to remove the "ppc" code in my patch, or add the similar "aarch64" to the remainder of the ppc patch. Thanks! - Derek -----Original Message----- From: Andrew Haley [mailto:aph at redhat.com] Sent: Thursday, May 11, 2017 3:41 PM To: White, Derek ; aarch64-port-dev at openjdk.java.net Subject: Re: [aarch64-port-dev ] [OpenJDK8u] java.nio.Bits.unaligned() doesn't handle aarch64 On 11/05/17 18:20, White, Derek wrote: > In mainline jdk8u, this was updated to include PPC as well (See > https://bugs.openjdk.java.net/browse/JDK-8165231). JDK9 has a much > better fix that supports aarch64 already. > > Tested on Spark and off-heap memory was being used. Note: The PPC fix > also patched sun/security/provider/ByteArrayAccess.java, but I didn't > include this in the patch below (not sure if it matters, or how to > test it). It's not a great idea to introduce a patch that will conflict with a patch we haven't yet merged. We will get all the patches from jdk8u eventually, but we only merge from security updates and peroper releases. I think we should add aarch64 support now, given that upstream jdk8u will never support it. Andrew. From gnu.andrew at redhat.com Fri May 12 03:50:37 2017 From: gnu.andrew at redhat.com (Andrew Hughes) Date: Thu, 11 May 2017 23:50:37 -0400 (EDT) Subject: [aarch64-port-dev ] [OpenJDK8u] java.nio.Bits.unaligned() doesn't handle aarch64 In-Reply-To: <63c8f30a-0408-cec6-9c9d-f99e7a3cffd2@redhat.com> References: <63c8f30a-0408-cec6-9c9d-f99e7a3cffd2@redhat.com> Message-ID: <715717450.10734912.1494561036996.JavaMail.zimbra@redhat.com> ----- Original Message ----- > On 11/05/17 18:20, White, Derek wrote: > > > In mainline jdk8u, this was updated to include PPC as well (See > > https://bugs.openjdk.java.net/browse/JDK-8165231). JDK9 has a much > > better fix that supports aarch64 already. > > This was actually written by Andrew Haley, I believe. > > Tested on Spark and off-heap memory was being used. Note: The PPC > > fix also patched sun/security/provider/ByteArrayAccess.java, but I > > didn't include this in the patch below (not sure if it matters, or > > how to test it). > > It's not a great idea to introduce a patch that will conflict with a > patch we haven't yet merged. We will get all the patches from jdk8u > eventually, but we only merge from security updates and peroper > releases. I think we should add aarch64 support now, given that > upstream jdk8u will never support it. > The 8u one is https://bugs.openjdk.java.net/browse/JDK-8165231 It is one of a number I requested be added to Oracle's CPU releases, given there doesn't seem to be a feature release (currently referred to as 8u152) coming any time. This can be done by adding the 8u-CPU-critical-request tag. See https://bugs.openjdk.java.net/browse/JDK-8165231?jql=labels%20%3D%208u-CPU-critical-request It seems that some have now been accepted and some rejected, though with no explanation as to the reasoning behind either. Fortunately, 8165231 is one of the ones that has been approved and so will be in 8u141, which is released in July. https://bugs.openjdk.java.net/browse/JDK-8179839 > Andrew. > > -- 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 Fri May 12 04:04:12 2017 From: gnu.andrew at redhat.com (Andrew Hughes) Date: Fri, 12 May 2017 00:04:12 -0400 (EDT) Subject: [aarch64-port-dev ] [RFR] 8u131 Upstream Sync In-Reply-To: <370062456.10734983.1494561102787.JavaMail.zimbra@redhat.com> Message-ID: <525315924.10737670.1494561852822.JavaMail.zimbra@redhat.com> Hi, OpenJDK 8 was recently updated with a security update, u131. This webrev syncs our version in the aarch64/jdk8u repositories with the version released upstream in jdk8u, tagging the result as aarch64-jdk8u131-b13. http://cr.openjdk.java.net/~andrew/aarch64-8/u131/webrev.02/ To illustrate the actual changes, the merge changesets for each repository are also included: http://cr.openjdk.java.net/~andrew/aarch64-8/u131/webrev.02/corba/merge.changeset http://cr.openjdk.java.net/~andrew/aarch64-8/u131/webrev.02/jaxp/merge.changeset http://cr.openjdk.java.net/~andrew/aarch64-8/u131/webrev.02/jaxws/merge.changeset http://cr.openjdk.java.net/~andrew/aarch64-8/u131/webrev.02/jdk/merge.changeset http://cr.openjdk.java.net/~andrew/aarch64-8/u131/webrev.02/hotspot/merge.changeset http://cr.openjdk.java.net/~andrew/aarch64-8/u131/webrev.02/langtools/merge.changeset http://cr.openjdk.java.net/~andrew/aarch64-8/u131/webrev.02/nashorn/merge.changeset http://cr.openjdk.java.net/~andrew/aarch64-8/u131/webrev.02/root/merge.changeset Changes: - S6515172: Runtime.availableProcessors() ignores Linux taskset command - S8173030: Temporary backout fix #8035568 from 8u131-b03 - S8173031: Temporary backout fix #8171952 from 8u131-b03 diffstat: Checking . b/.hgtags | 12 ++++++++++++ 1 file changed, 12 insertions(+) Checking corba b/.hgtags | 12 ++++++++++++ 1 file changed, 12 insertions(+) Checking jaxp b/.hgtags | 12 ++++++++++++ 1 file changed, 12 insertions(+) Checking jaxws b/.hgtags | 12 ++++++++++++ 1 file changed, 12 insertions(+) Checking langtools b/.hgtags | 12 ++++++++++++ 1 file changed, 12 insertions(+) Checking hotspot b/.hgtags | 12 +++ b/src/os/linux/vm/globals_linux.hpp | 7 + b/src/os/linux/vm/os_linux.cpp | 50 ++++++++++++-- b/test/runtime/os/AvailableProcessors.java | 103 +++++++++++++++++++++++++++++ 4 files changed, 164 insertions(+), 8 deletions(-) Checking jdk b/.hgtags | 12 b/src/macosx/native/sun/awt/AWTWindow.m | 4 b/test/java/awt/Frame/FrameResize/ShowChildWhileResizingTest.java | 88 + b/test/java/io/Serializable/serialFilter/SerialFilterTest.java | 91 - b/test/java/lang/Thread/ITLConstructor.java | 107 + b/test/javax/swing/regtesthelpers/JRobot.java | 294 +++ b/test/javax/swing/regtesthelpers/SwingTestHelper.java | 862 ++++++++++ b/test/javax/swing/regtesthelpers/Test.java | 34 b/test/javax/swing/text/FlowView/LayoutTest.java | 90 + b/test/sun/net/ftp/FtpURLConnectionLeak.java | 155 + 10 files changed, 1707 insertions(+), 30 deletions(-) Checking nashorn b/.hgtags | 12 ++++++++++++ 1 file changed, 12 insertions(+) Ok to push? 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 aph at redhat.com Fri May 12 07:17:52 2017 From: aph at redhat.com (Andrew Haley) Date: Fri, 12 May 2017 08:17:52 +0100 Subject: [aarch64-port-dev ] [OpenJDK8u] java.nio.Bits.unaligned() doesn't handle aarch64 In-Reply-To: <715717450.10734912.1494561036996.JavaMail.zimbra@redhat.com> References: <63c8f30a-0408-cec6-9c9d-f99e7a3cffd2@redhat.com> <715717450.10734912.1494561036996.JavaMail.zimbra@redhat.com> Message-ID: <72c58007-832c-4795-797d-8bccb414b44c@redhat.com> On 12/05/17 04:50, Andrew Hughes wrote: > >>> Tested on Spark and off-heap memory was being used. Note: The PPC >>> fix also patched sun/security/provider/ByteArrayAccess.java, but I >>> didn't include this in the patch below (not sure if it matters, or >>> how to test it). >> >> It's not a great idea to introduce a patch that will conflict with a >> patch we haven't yet merged. We will get all the patches from jdk8u >> eventually, but we only merge from security updates and peroper >> releases. I think we should add aarch64 support now, given that >> upstream jdk8u will never support it. > > The 8u one is https://bugs.openjdk.java.net/browse/JDK-8165231 > > It is one of a number I requested be added to Oracle's CPU releases, > given there doesn't seem to be a feature release (currently referred to > as 8u152) coming any time. This can be done by adding the > 8u-CPU-critical-request tag. See > https://bugs.openjdk.java.net/browse/JDK-8165231?jql=labels%20%3D%208u-CPU-critical-request > > It seems that some have now been accepted and some rejected, though > with no explanation as to the reasoning behind either. Fortunately, > 8165231 is one of the ones that has been approved and so will be in > 8u141, which is released in July. > > https://bugs.openjdk.java.net/browse/JDK-8179839 OK. So would you like to handle Derek's change, please? I'll leave it up to you to decide if it's best to wait for 8u141. Andrew. From aph at redhat.com Fri May 12 07:21:42 2017 From: aph at redhat.com (Andrew Haley) Date: Fri, 12 May 2017 08:21:42 +0100 Subject: [aarch64-port-dev ] [OpenJDK8u] java.nio.Bits.unaligned() doesn't handle aarch64 In-Reply-To: <72c58007-832c-4795-797d-8bccb414b44c@redhat.com> References: <63c8f30a-0408-cec6-9c9d-f99e7a3cffd2@redhat.com> <715717450.10734912.1494561036996.JavaMail.zimbra@redhat.com> <72c58007-832c-4795-797d-8bccb414b44c@redhat.com> Message-ID: On 12/05/17 08:17, Andrew Haley wrote: > It seems that some have now been accepted and some rejected, though > with no explanation as to the reasoning behind either. Fortunately, > 8165231 is one of the ones that has been approved and so will be in > 8u141, which is released in July. We should discuss the rejected ones here. We can decide to include them if they're very important. Can you post them, please? Andrew. From zhongwei.yao at linaro.org Fri May 12 07:24:41 2017 From: zhongwei.yao at linaro.org (Zhongwei Yao) Date: Fri, 12 May 2017 15:24:41 +0800 Subject: [aarch64-port-dev ] RFR: 8179933: aarch64: incorrect match rule for immL_63 and immL_255 In-Reply-To: <88066719-4ac8-90c9-b0ac-60efbc326d31@redhat.com> References: <88066719-4ac8-90c9-b0ac-60efbc326d31@redhat.com> Message-ID: Hi, Andrew, Thanks. And I find immL_63's modification in the previous patch is incorrect. The original immL_63 definition is correct. I renamed immL_63 to the proper name: immI_63 in the updated patch. I've uploaded to the new webrev at: http://cr.openjdk.java.net/~njian/8179933/webrev.01/ ("hg export" looks better than the diff in webrev). And here is my test case for "SubExtL_uxtb_and" instruction. Case for "AddExtL_uxtb_and" is similar. java case: public static long subAnd255() { long acc1 = 0; for (long i = 0; i < 10000; i++) { acc1 -= (i & 255); } return acc1; } orignal generated code: 0xa0: add x19, x19, #0x1 0xa4: sub x20, x20, x11 0xa8: ldr wzr, [x10] 0xac: and x11, x19, #0xff 0xb0: mov x8, #0x2710 0xb4: cmp x19, x8 0xb8: b.lt 0xa0 generated code after applying this patch: 0x20: sub x20, x20, w19, uxtb 0x24: add x19, x19, #0x1 0x28: ldr wzr, [x10] 0x2c: mov x8, #0x2710 0x30: cmp x19, x8 0x34: b.lt 0x20 -- Best regards, Zhongwei On 11 May 2017 at 18:30, Andrew Haley wrote: > On 11/05/17 11:07, Zhongwei Yao wrote: > > Bug: > > https://bugs.openjdk.java.net/browse/JDK-8179933 > > > > Webrev: > > http://cr.openjdk.java.net/~njian/8179933/webrev.00/ > > Did you run a test case to see the difference in the generated code? > If so, you should provide it. > > Andrew. > > -- Best regards, Zhongwei From adinn at redhat.com Fri May 12 08:10:39 2017 From: adinn at redhat.com (Andrew Dinn) Date: Fri, 12 May 2017 09:10:39 +0100 Subject: [aarch64-port-dev ] RFR: 8179933: aarch64: incorrect match rule for immL_63 and immL_255 In-Reply-To: References: <88066719-4ac8-90c9-b0ac-60efbc326d31@redhat.com> Message-ID: <92073b8a-f295-492c-ad62-21e2e71e318b@redhat.com> On 12/05/17 08:24, Zhongwei Yao wrote: > And I find immL_63's modification in the previous patch is incorrect. The > original immL_63 definition is correct. I renamed immL_63 to the proper > name: immI_63 in the updated patch. > > I've uploaded to the new webrev at: > http://cr.openjdk.java.net/~njian/8179933/webrev.01/ > ("hg export" looks better than the diff in webrev). > > And here is my test case for "SubExtL_uxtb_and" instruction. Case for > "AddExtL_uxtb_and" is similar. > > java case: > public static long subAnd255() { > long acc1 = 0; > for (long i = 0; i < 10000; i++) { > acc1 -= (i & 255); > } > return acc1; > } > > orignal generated code: > 0xa0: add x19, x19, #0x1 > 0xa4: sub x20, x20, x11 > 0xa8: ldr wzr, [x10] > 0xac: and x11, x19, #0xff > 0xb0: mov x8, #0x2710 > 0xb4: cmp x19, x8 > 0xb8: b.lt 0xa0 > > generated code after applying this patch: > 0x20: sub x20, x20, w19, uxtb > 0x24: add x19, x19, #0x1 > 0x28: ldr wzr, [x10] > 0x2c: mov x8, #0x2710 > 0x30: cmp x19, x8 > 0x34: b.lt 0x20 Yes, the change in the definition of immL_255 is correct and so is the change in the name of immL_63 to immI_63. n.b. immL_255 is used to type the mask operand to an AndL which is of type long. So, its definition needs to match a long constant. immL_63 was being used to type the shiftcount operands to RShiftL and URShiftL which, of course, are ints. Since its definition already matches an int renaming to immI_63 is correct. The patch looks good to me. regards, Andrew Dinn ----------- Senior Principal Software Engineer Red Hat UK Ltd Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander From aph at redhat.com Fri May 12 08:14:55 2017 From: aph at redhat.com (Andrew Haley) Date: Fri, 12 May 2017 09:14:55 +0100 Subject: [aarch64-port-dev ] RFR: 8179933: aarch64: incorrect match rule for immL_63 and immL_255 In-Reply-To: <92073b8a-f295-492c-ad62-21e2e71e318b@redhat.com> References: <88066719-4ac8-90c9-b0ac-60efbc326d31@redhat.com> <92073b8a-f295-492c-ad62-21e2e71e318b@redhat.com> Message-ID: On 12/05/17 09:10, Andrew Dinn wrote: > > The patch looks good to me. While we're looking at aarch64.ad, I see this patch and it looks really, uh: 11149 instruct signExtractL(iRegLNoSp dst, iRegL src1, immI_63 div1, immI_63 div2) %{ 11150 match(Set dst (URShiftL (RShiftL src1 div1) div2)); 11151 ins_cost(INSN_COST); 11152 format %{ "lsr $dst, $src1, $div1" %} 11153 ins_encode %{ 11154 __ lsr(as_Register($dst$$reg), as_Register($src1$$reg), 63); 11155 %} 11156 ins_pipe(ialu_reg_shift); 11157 %} So it's ((aLong >> 63) >>> 63) This is so weird I don't know what to think about it. Andrew. From zhongwei.yao at linaro.org Fri May 12 09:14:44 2017 From: zhongwei.yao at linaro.org (Zhongwei Yao) Date: Fri, 12 May 2017 17:14:44 +0800 Subject: [aarch64-port-dev ] RFR: 8179933: aarch64: incorrect match rule for immL_63 and immL_255 In-Reply-To: References: <88066719-4ac8-90c9-b0ac-60efbc326d31@redhat.com> <92073b8a-f295-492c-ad62-21e2e71e318b@redhat.com> Message-ID: On 12 May 2017 at 16:14, Andrew Haley wrote: >So it's > > ((aLong >> 63) >>> 63) > >This is so weird I don't know what to think about it. Yeah, it is weird. I was thinking (aLong >>> 63) should be enough. Shall we just remove this pattern? -- Best regards, Zhongwei From aph at redhat.com Fri May 12 09:25:51 2017 From: aph at redhat.com (Andrew Haley) Date: Fri, 12 May 2017 10:25:51 +0100 Subject: [aarch64-port-dev ] RFR: 8179933: aarch64: incorrect match rule for immL_63 and immL_255 In-Reply-To: References: <88066719-4ac8-90c9-b0ac-60efbc326d31@redhat.com> <92073b8a-f295-492c-ad62-21e2e71e318b@redhat.com> Message-ID: <073dc684-7c96-6221-815e-521bde178078@redhat.com> On 12/05/17 10:14, Zhongwei Yao wrote: > On 12 May 2017 at 16:14, Andrew Haley wrote: >> So it's >> >> ((aLong >> 63) >>> 63) >> >> This is so weird I don't know what to think about it. > > Yeah, it is weird. I was thinking (aLong >>> 63) should be enough. Shall we > just remove this pattern? Well, maybe there was a reason for it. Andrew. From adinn at redhat.com Fri May 12 09:28:14 2017 From: adinn at redhat.com (Andrew Dinn) Date: Fri, 12 May 2017 10:28:14 +0100 Subject: [aarch64-port-dev ] RFR: 8179933: aarch64: incorrect match rule for immL_63 and immL_255 In-Reply-To: References: <88066719-4ac8-90c9-b0ac-60efbc326d31@redhat.com> <92073b8a-f295-492c-ad62-21e2e71e318b@redhat.com> Message-ID: On 12/05/17 10:14, Zhongwei Yao wrote: > On 12 May 2017 at 16:14, Andrew Haley > wrote: >>So it's >> >> ((aLong >> 63) >>> 63) >> >>This is so weird I don't know what to think about it. > > Yeah, it is weird. I was thinking (aLong >>> 63) should be enough. Shall > we just remove this pattern? The key question is who inserted this rule and for what reason? If the front end actually generates the node graph (URShiftL (RShiftL src1 63) 63)) then we need this rule to translate it to the minimal instruction sequence. Of course, an alternative might be to make the front end implement a generic optimization to simplify this pattern, say as an ideal transform on the rshift node (URShiftL (RShiftL X 63) 63)) ==> (URShiftL X 63) In fact, I think a more general transform would be ok (URShiftL (RShiftL X IConst) 63)) (for any value of IConst) ==> (URShiftL X 63) I can see how that second graph might be more likely to actually turn up in a compilation. Either way the important thing is to determine whether a subgraph of this form actually occurs. regards, Andrew Dinn ----------- Senior Principal Software Engineer Red Hat UK Ltd Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander From adinn at redhat.com Fri May 12 09:45:31 2017 From: adinn at redhat.com (Andrew Dinn) Date: Fri, 12 May 2017 10:45:31 +0100 Subject: [aarch64-port-dev ] RFR: 8179933: aarch64: incorrect match rule for immL_63 and immL_255 In-Reply-To: <073dc684-7c96-6221-815e-521bde178078@redhat.com> References: <88066719-4ac8-90c9-b0ac-60efbc326d31@redhat.com> <92073b8a-f295-492c-ad62-21e2e71e318b@redhat.com> <073dc684-7c96-6221-815e-521bde178078@redhat.com> Message-ID: <26173768-d87f-6ca5-3684-47bd851018fb@redhat.com> On 12/05/17 10:25, Andrew Haley wrote: > On 12/05/17 10:14, Zhongwei Yao wrote: >> On 12 May 2017 at 16:14, Andrew Haley wrote: >>> So it's >>> >>> ((aLong >> 63) >>> 63) >>> >>> This is so weird I don't know what to think about it. >> >> Yeah, it is weird. I was thinking (aLong >>> 63) should be enough. Shall we >> just remove this pattern? > > Well, maybe there was a reason for it. Ok, these rules were first introduced into jdk8 by Ed Nevill http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/1fcabae0e46f They were then imported into jdk9 as part of the wholesale upload. So, I think there is probably a good reason why they are there :-) regards, Andrew Dinn ----------- Senior Principal Software Engineer Red Hat UK Ltd Registered in England and Wales under Company Registration No. 03798903 Directors: Michael Cunningham, Michael ("Mike") O'Neill, Eric Shander From gnu.andrew at redhat.com Fri May 12 13:16:43 2017 From: gnu.andrew at redhat.com (Andrew Hughes) Date: Fri, 12 May 2017 09:16:43 -0400 (EDT) Subject: [aarch64-port-dev ] [OpenJDK8u] java.nio.Bits.unaligned() doesn't handle aarch64 In-Reply-To: References: <63c8f30a-0408-cec6-9c9d-f99e7a3cffd2@redhat.com> <715717450.10734912.1494561036996.JavaMail.zimbra@redhat.com> <72c58007-832c-4795-797d-8bccb414b44c@redhat.com> Message-ID: <841784249.10990409.1494595003665.JavaMail.zimbra@redhat.com> ----- Original Message ----- > On 12/05/17 08:17, Andrew Haley wrote: > > It seems that some have now been accepted and some rejected, though > > with no explanation as to the reasoning behind either. Fortunately, > > 8165231 is one of the ones that has been approved and so will be in > > 8u141, which is released in July. > > We should discuss the rejected ones here. We can decide to include > them if they're very important. Can you post them, please? > > Andrew. > > Sure. This is the full list: Approved for 8u141 in July: 8144566: Custom HostnameVerifier disables SNI extension 8155049: New tests from 8144566 fail with "No expected Server Name Indication" 8165231: java.nio.Bits.unaligned() doesn't return true on ppc 8174164: SafePointNode::_replaced_nodes breaks with irreducible loops 8174729: Race Condition in java.lang.reflect.WeakCache 8175097: [TESTBUG] 8174164 fix missed the test Rejected: 8173941: SA does not work if executable is DSO 8162384: Performance regression: bimorphic inlining may be bypassed by type speculation 8153711: [REDO] JDWP: Memory Leak: GlobalRefs never deleted when processing invokeMethod command All three rejected ones are included in our RPMs. The last two arose from reported customer issues. The DSO one is related to issues building on the latest versions of Fedora. -- 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 Fri May 12 13:19:44 2017 From: gnu.andrew at redhat.com (Andrew Hughes) Date: Fri, 12 May 2017 09:19:44 -0400 (EDT) Subject: [aarch64-port-dev ] [OpenJDK8u] java.nio.Bits.unaligned() doesn't handle aarch64 In-Reply-To: <72c58007-832c-4795-797d-8bccb414b44c@redhat.com> References: <63c8f30a-0408-cec6-9c9d-f99e7a3cffd2@redhat.com> <715717450.10734912.1494561036996.JavaMail.zimbra@redhat.com> <72c58007-832c-4795-797d-8bccb414b44c@redhat.com> Message-ID: <1934234706.10990895.1494595184194.JavaMail.zimbra@redhat.com> ----- Original Message ----- > On 12/05/17 04:50, Andrew Hughes wrote: > > > >>> Tested on Spark and off-heap memory was being used. Note: The PPC > >>> fix also patched sun/security/provider/ByteArrayAccess.java, but I > >>> didn't include this in the patch below (not sure if it matters, or > >>> how to test it). > >> > >> It's not a great idea to introduce a patch that will conflict with a > >> patch we haven't yet merged. We will get all the patches from jdk8u > >> eventually, but we only merge from security updates and peroper > >> releases. I think we should add aarch64 support now, given that > >> upstream jdk8u will never support it. > > > > The 8u one is https://bugs.openjdk.java.net/browse/JDK-8165231 > > > > It is one of a number I requested be added to Oracle's CPU releases, > > given there doesn't seem to be a feature release (currently referred to > > as 8u152) coming any time. This can be done by adding the > > 8u-CPU-critical-request tag. See > > https://bugs.openjdk.java.net/browse/JDK-8165231?jql=labels%20%3D%208u-CPU-critical-request > > > > It seems that some have now been accepted and some rejected, though > > with no explanation as to the reasoning behind either. Fortunately, > > 8165231 is one of the ones that has been approved and so will be in > > 8u141, which is released in July. > > > > https://bugs.openjdk.java.net/browse/JDK-8179839 > > OK. So would you like to handle Derek's change, please? I'll leave it > up to you to decide if it's best to wait for 8u141. > > Andrew. > > In that case, I'll add it after I've merged 8u141 if no-one has any objections. It'll then be part of our aarch64 version of 8u141 along with the PPC one. Doing it then will basically make it a one-liner: + || arch.equals("aarch64"); -- 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 Fri May 12 13:24:27 2017 From: gnu.andrew at redhat.com (Andrew Hughes) Date: Fri, 12 May 2017 09:24:27 -0400 (EDT) Subject: [aarch64-port-dev ] [OpenJDK8u] java.nio.Bits.unaligned() doesn't handle aarch64 In-Reply-To: <841784249.10990409.1494595003665.JavaMail.zimbra@redhat.com> References: <63c8f30a-0408-cec6-9c9d-f99e7a3cffd2@redhat.com> <715717450.10734912.1494561036996.JavaMail.zimbra@redhat.com> <72c58007-832c-4795-797d-8bccb414b44c@redhat.com> <841784249.10990409.1494595003665.JavaMail.zimbra@redhat.com> Message-ID: <1018695816.10991620.1494595467550.JavaMail.zimbra@redhat.com> ----- Original Message ----- > > > ----- Original Message ----- > > On 12/05/17 08:17, Andrew Haley wrote: > > > It seems that some have now been accepted and some rejected, though > > > with no explanation as to the reasoning behind either. Fortunately, > > > 8165231 is one of the ones that has been approved and so will be in > > > 8u141, which is released in July. > > > > We should discuss the rejected ones here. We can decide to include > > them if they're very important. Can you post them, please? > > > > Andrew. > > > > > > Sure. This is the full list: > > Approved for 8u141 in July: > > 8144566: Custom HostnameVerifier disables SNI extension > 8155049: New tests from 8144566 fail with "No expected Server Name > Indication" > 8165231: java.nio.Bits.unaligned() doesn't return true on ppc > 8174164: SafePointNode::_replaced_nodes breaks with irreducible loops > 8174729: Race Condition in java.lang.reflect.WeakCache > 8175097: [TESTBUG] 8174164 fix missed the test > > Rejected: > > 8173941: SA does not work if executable is DSO > 8162384: Performance regression: bimorphic inlining may be bypassed by type > speculation > 8153711: [REDO] JDWP: Memory Leak: GlobalRefs never deleted when processing > invokeMethod command > > All three rejected ones are included in our RPMs. The last two arose > from reported customer issues. The DSO one is related to issues building > on the latest versions of Fedora. > -- And now this one: 8151841: Build needs additional flags to compile with GCC 6 I fixed this over a year ago in 9 and then backported to 8 last summer. Yet it still hasn't seen the light of day. I have to manually apply it and then revert it every time I do a test build of aarch64/jdk8u. -- 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 edward.nevill at gmail.com Fri May 12 18:11:57 2017 From: edward.nevill at gmail.com (Edward Nevill) Date: Fri, 12 May 2017 19:11:57 +0100 Subject: [aarch64-port-dev ] RFR: 8179933: aarch64: incorrect match rule for immL_63 and immL_255 In-Reply-To: <26173768-d87f-6ca5-3684-47bd851018fb@redhat.com> References: <88066719-4ac8-90c9-b0ac-60efbc326d31@redhat.com> <92073b8a-f295-492c-ad62-21e2e71e318b@redhat.com> <073dc684-7c96-6221-815e-521bde178078@redhat.com> <26173768-d87f-6ca5-3684-47bd851018fb@redhat.com> Message-ID: <1494612717.3246.4.camel@gmail.com> On Fri, 2017-05-12 at 10:45 +0100, Andrew Dinn wrote: > On 12/05/17 10:25, Andrew Haley wrote: > > > > On 12/05/17 10:14, Zhongwei Yao wrote: > > > > > > On 12 May 2017 at 16:14, Andrew Haley wrote: > > > > > > > > So it's > > > > > > > > ???((aLong >> 63) >>> 63) > > > > > > > > This is so weird I don't know what to think about it. > > > Yeah, it is weird. I was thinking (aLong >>> 63) should be enough. Shall we > > > just remove this pattern? > > Well, maybe there was a reason for it. > Ok, these rules were first introduced into jdk8 by Ed Nevill > > ? http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/1fcabae0e46f > > They were then imported into jdk9 as part of the wholesale upload. > > So, I think there is probably a good reason why they are there :-) > Here is the original posting for the int case on aarch64-dev http://mail.openjdk.java.net/pipermail/aarch64-port-dev/2014-April/001047.html On Mon, 2014-05-12 at 13:10 +0100, Andrew Haley wrote: > Why is there no long version of this? So I added a long version http://mail.openjdk.java.net/pipermail/aarch64-port-dev/2014-May/001070.html Ed. From ci_notify at linaro.org Fri May 12 20:51:32 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 12 May 2017 20:51:32 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <1288266255.1454.1494622294763.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/131/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/03 pass: 1,396; fail: 4 Build 1: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 2: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 3: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 4: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 5: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 6: aarch64/2017/apr/21 pass: 1,401; fail: 7 Build 7: aarch64/2017/apr/23 pass: 1,400; fail: 7; error: 1 Build 8: aarch64/2017/apr/25 pass: 1,401; fail: 7 Build 9: aarch64/2017/apr/27 pass: 1,400; fail: 8; error: 1 Build 10: aarch64/2017/apr/29 pass: 1,401; fail: 7; error: 1 Build 11: aarch64/2017/may/05 pass: 1,402; fail: 7 Build 12: aarch64/2017/may/07 pass: 1,402; fail: 7 Build 13: aarch64/2017/may/09 pass: 1,401; fail: 7; error: 1 Build 14: aarch64/2017/may/11 pass: 1,401; fail: 7; error: 1 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/03 pass: 7,282; fail: 717; error: 18 Build 1: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 2: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 3: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 4: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 5: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 6: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 Build 7: aarch64/2017/apr/23 pass: 7,315; fail: 712; error: 25 Build 8: aarch64/2017/apr/25 pass: 7,341; fail: 689; error: 23 Build 9: aarch64/2017/apr/27 pass: 7,320; fail: 710; error: 23 Build 10: aarch64/2017/apr/29 pass: 7,293; fail: 729; error: 32 Build 11: aarch64/2017/may/05 pass: 7,319; fail: 711; error: 28 Build 12: aarch64/2017/may/07 pass: 7,331; fail: 701; error: 26 Build 13: aarch64/2017/may/09 pass: 7,326; fail: 702; error: 31 Build 14: aarch64/2017/may/11 pass: 7,340; fail: 693; error: 27 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/03 pass: 3,884; fail: 3; error: 1 Build 1: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 2: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 3: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 4: aarch64/2017/apr/15 pass: 3,891 Build 5: aarch64/2017/apr/17 pass: 3,891 Build 6: aarch64/2017/apr/21 pass: 3,894; error: 2 Build 7: aarch64/2017/apr/23 pass: 3,894; error: 3 Build 8: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 9: aarch64/2017/apr/27 pass: 3,896; fail: 1; error: 4 Build 10: aarch64/2017/apr/29 pass: 3,899; error: 2 Build 11: aarch64/2017/may/05 pass: 3,897; error: 4 Build 12: aarch64/2017/may/07 pass: 3,895; error: 6 Build 13: aarch64/2017/may/09 pass: 3,897; error: 5 Build 14: aarch64/2017/may/11 pass: 3,896; error: 6 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/03 pass: 1,400; fail: 4 Build 1: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 2: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 3: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 4: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 5: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 6: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 Build 7: aarch64/2017/apr/23 pass: 1,404; fail: 7; error: 1 Build 8: aarch64/2017/apr/25 pass: 1,405; fail: 7 Build 9: aarch64/2017/apr/27 pass: 1,405; fail: 7; error: 1 Build 10: aarch64/2017/apr/29 pass: 1,406; fail: 7 Build 11: aarch64/2017/may/05 pass: 1,406; fail: 7 Build 12: aarch64/2017/may/07 pass: 1,405; fail: 7; error: 1 Build 13: aarch64/2017/may/09 pass: 1,406; fail: 7 Build 14: aarch64/2017/may/11 pass: 1,405; fail: 7; error: 1 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/03 pass: 7,289; fail: 708; error: 20 Build 1: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 2: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 3: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 4: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 5: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 6: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 Build 7: aarch64/2017/apr/23 pass: 7,315; fail: 716; error: 21 Build 8: aarch64/2017/apr/25 pass: 7,319; fail: 709; error: 25 Build 9: aarch64/2017/apr/27 pass: 7,324; fail: 701; error: 28 Build 10: aarch64/2017/apr/29 pass: 7,340; fail: 686; error: 28 Build 11: aarch64/2017/may/05 pass: 7,332; fail: 702; error: 24 Build 12: aarch64/2017/may/07 pass: 7,350; fail: 687; error: 21 Build 13: aarch64/2017/may/09 pass: 7,352; fail: 681; error: 26 Build 14: aarch64/2017/may/11 pass: 7,330; fail: 705; error: 25 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/03 pass: 3,885; fail: 2; error: 1 Build 1: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 2: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 3: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 4: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 5: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 6: aarch64/2017/apr/21 pass: 3,891; fail: 1; error: 4 Build 7: aarch64/2017/apr/23 pass: 3,893; error: 4 Build 8: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 9: aarch64/2017/apr/27 pass: 3,893; error: 8 Build 10: aarch64/2017/apr/29 pass: 3,896; error: 5 Build 11: aarch64/2017/may/05 pass: 3,896; error: 5 Build 12: aarch64/2017/may/07 pass: 3,895; fail: 1; error: 5 Build 13: aarch64/2017/may/09 pass: 3,896; fail: 1; error: 5 Build 14: aarch64/2017/may/11 pass: 3,897; 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.72x 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.88, Server: 113.83 Client 69.88 / Client 2014-04-01 (43.00): 1.63x 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-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/ 2017-05-06 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/125/results/ 2017-05-09 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/127/results/ 2017-05-11 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/129/results/ 2017-05-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/131/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 May 15 02:47:32 2017 From: zhongwei.yao at linaro.org (Zhongwei Yao) Date: Mon, 15 May 2017 10:47:32 +0800 Subject: [aarch64-port-dev ] RFR: 8179933: aarch64: incorrect match rule for immL_63 and immL_255 In-Reply-To: <1494612717.3246.4.camel@gmail.com> References: <88066719-4ac8-90c9-b0ac-60efbc326d31@redhat.com> <92073b8a-f295-492c-ad62-21e2e71e318b@redhat.com> <073dc684-7c96-6221-815e-521bde178078@redhat.com> <26173768-d87f-6ca5-3684-47bd851018fb@redhat.com> <1494612717.3246.4.camel@gmail.com> Message-ID: Hi, Edward, Thanks for pointing out. And I've checked the generated nodes of dst = src / 2, (y and x are both long) in current c2 is: RShiftL (AddL src (URShiftL (RShiftL src immI_63) immI_63)) On 13 May 2017 at 02:11, Edward Nevill wrote: > On Fri, 2017-05-12 at 10:45 +0100, Andrew Dinn wrote: > > On 12/05/17 10:25, Andrew Haley wrote: > > > > > > On 12/05/17 10:14, Zhongwei Yao wrote: > > > > > > > > On 12 May 2017 at 16:14, Andrew Haley wrote: > > > > > > > > > > So it's > > > > > > > > > > ((aLong >> 63) >>> 63) > > > > > > > > > > This is so weird I don't know what to think about it. > > > > Yeah, it is weird. I was thinking (aLong >>> 63) should be enough. > Shall we > > > > just remove this pattern? > > > Well, maybe there was a reason for it. > > Ok, these rules were first introduced into jdk8 by Ed Nevill > > > > http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/1fcabae0e46f > > > > They were then imported into jdk9 as part of the wholesale upload. > > > > So, I think there is probably a good reason why they are there :-) > > > > Here is the original posting for the int case on aarch64-dev > > http://mail.openjdk.java.net/pipermail/aarch64-port-dev/ > 2014-April/001047.html > > On Mon, 2014-05-12 at 13:10 +0100, Andrew Haley wrote: > > > Why is there no long version of this? > > So I added a long version > > http://mail.openjdk.java.net/pipermail/aarch64-port-dev/ > 2014-May/001070.html > > Ed. > > -- Best regards, Zhongwei From ci_notify at linaro.org Sun May 14 22:51:22 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sun, 14 May 2017 22:51:22 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <1798624375.1516.1494802283650.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/133/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/07 pass: 1,396; fail: 4 Build 1: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 2: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 3: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 4: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 5: aarch64/2017/apr/21 pass: 1,401; fail: 7 Build 6: aarch64/2017/apr/23 pass: 1,400; fail: 7; error: 1 Build 7: aarch64/2017/apr/25 pass: 1,401; fail: 7 Build 8: aarch64/2017/apr/27 pass: 1,400; fail: 8; error: 1 Build 9: aarch64/2017/apr/29 pass: 1,401; fail: 7; error: 1 Build 10: aarch64/2017/may/05 pass: 1,402; fail: 7 Build 11: aarch64/2017/may/07 pass: 1,402; fail: 7 Build 12: aarch64/2017/may/09 pass: 1,401; fail: 7; error: 1 Build 13: aarch64/2017/may/11 pass: 1,401; fail: 7; error: 1 Build 14: aarch64/2017/may/13 pass: 1,401; fail: 7; error: 1 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/07 pass: 7,286; fail: 718; error: 20 Build 1: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 2: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 3: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 4: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 5: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 Build 6: aarch64/2017/apr/23 pass: 7,315; fail: 712; error: 25 Build 7: aarch64/2017/apr/25 pass: 7,341; fail: 689; error: 23 Build 8: aarch64/2017/apr/27 pass: 7,320; fail: 710; error: 23 Build 9: aarch64/2017/apr/29 pass: 7,293; fail: 729; error: 32 Build 10: aarch64/2017/may/05 pass: 7,319; fail: 711; error: 28 Build 11: aarch64/2017/may/07 pass: 7,331; fail: 701; error: 26 Build 12: aarch64/2017/may/09 pass: 7,326; fail: 702; error: 31 Build 13: aarch64/2017/may/11 pass: 7,340; fail: 693; error: 27 Build 14: aarch64/2017/may/13 pass: 7,344; fail: 693; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/07 pass: 3,889; error: 2 Build 1: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 2: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 3: aarch64/2017/apr/15 pass: 3,891 Build 4: aarch64/2017/apr/17 pass: 3,891 Build 5: aarch64/2017/apr/21 pass: 3,894; error: 2 Build 6: aarch64/2017/apr/23 pass: 3,894; error: 3 Build 7: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 8: aarch64/2017/apr/27 pass: 3,896; fail: 1; error: 4 Build 9: aarch64/2017/apr/29 pass: 3,899; error: 2 Build 10: aarch64/2017/may/05 pass: 3,897; error: 4 Build 11: aarch64/2017/may/07 pass: 3,895; error: 6 Build 12: aarch64/2017/may/09 pass: 3,897; error: 5 Build 13: aarch64/2017/may/11 pass: 3,896; error: 6 Build 14: aarch64/2017/may/13 pass: 3,898; error: 5 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/07 pass: 1,400; fail: 4 Build 1: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 2: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 3: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 4: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 5: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 Build 6: aarch64/2017/apr/23 pass: 1,404; fail: 7; error: 1 Build 7: aarch64/2017/apr/25 pass: 1,405; fail: 7 Build 8: aarch64/2017/apr/27 pass: 1,405; fail: 7; error: 1 Build 9: aarch64/2017/apr/29 pass: 1,406; fail: 7 Build 10: aarch64/2017/may/05 pass: 1,406; fail: 7 Build 11: aarch64/2017/may/07 pass: 1,405; fail: 7; error: 1 Build 12: aarch64/2017/may/09 pass: 1,406; fail: 7 Build 13: aarch64/2017/may/11 pass: 1,405; fail: 7; error: 1 Build 14: aarch64/2017/may/13 pass: 1,405; fail: 7; error: 1 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/07 pass: 7,311; fail: 695; error: 18 Build 1: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 2: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 3: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 4: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 5: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 Build 6: aarch64/2017/apr/23 pass: 7,315; fail: 716; error: 21 Build 7: aarch64/2017/apr/25 pass: 7,319; fail: 709; error: 25 Build 8: aarch64/2017/apr/27 pass: 7,324; fail: 701; error: 28 Build 9: aarch64/2017/apr/29 pass: 7,340; fail: 686; error: 28 Build 10: aarch64/2017/may/05 pass: 7,332; fail: 702; error: 24 Build 11: aarch64/2017/may/07 pass: 7,350; fail: 687; error: 21 Build 12: aarch64/2017/may/09 pass: 7,352; fail: 681; error: 26 Build 13: aarch64/2017/may/11 pass: 7,330; fail: 705; error: 25 Build 14: aarch64/2017/may/13 pass: 7,350; fail: 683; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/07 pass: 3,889; fail: 1; error: 1 Build 1: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 2: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 3: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 4: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 5: aarch64/2017/apr/21 pass: 3,891; fail: 1; error: 4 Build 6: aarch64/2017/apr/23 pass: 3,893; error: 4 Build 7: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 8: aarch64/2017/apr/27 pass: 3,893; error: 8 Build 9: aarch64/2017/apr/29 pass: 3,896; error: 5 Build 10: aarch64/2017/may/05 pass: 3,896; error: 5 Build 11: aarch64/2017/may/07 pass: 3,895; fail: 1; error: 5 Build 12: aarch64/2017/may/09 pass: 3,896; fail: 1; error: 5 Build 13: aarch64/2017/may/11 pass: 3,897; fail: 1; error: 4 Build 14: aarch64/2017/may/13 pass: 3,899; 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.89x 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: 69.53, Server: 116.65 Client 69.53 / Client 2014-04-01 (43.00): 1.62x 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-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/ 2017-05-06 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/125/results/ 2017-05-09 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/127/results/ 2017-05-11 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/129/results/ 2017-05-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/131/results/ 2017-05-14 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/133/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 Tue May 16 22:45:49 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Tue, 16 May 2017 22:45:49 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <1893926867.1699.1494974751109.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/135/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/11 pass: 1,399; fail: 7 Build 1: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 2: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 3: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 4: aarch64/2017/apr/21 pass: 1,401; fail: 7 Build 5: aarch64/2017/apr/23 pass: 1,400; fail: 7; error: 1 Build 6: aarch64/2017/apr/25 pass: 1,401; fail: 7 Build 7: aarch64/2017/apr/27 pass: 1,400; fail: 8; error: 1 Build 8: aarch64/2017/apr/29 pass: 1,401; fail: 7; error: 1 Build 9: aarch64/2017/may/05 pass: 1,402; fail: 7 Build 10: aarch64/2017/may/07 pass: 1,402; fail: 7 Build 11: aarch64/2017/may/09 pass: 1,401; fail: 7; error: 1 Build 12: aarch64/2017/may/11 pass: 1,401; fail: 7; error: 1 Build 13: aarch64/2017/may/13 pass: 1,401; fail: 7; error: 1 Build 14: aarch64/2017/may/15 pass: 1,401; fail: 7; error: 1 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/11 pass: 7,293; fail: 706; error: 25 Build 1: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 2: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 3: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 4: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 Build 5: aarch64/2017/apr/23 pass: 7,315; fail: 712; error: 25 Build 6: aarch64/2017/apr/25 pass: 7,341; fail: 689; error: 23 Build 7: aarch64/2017/apr/27 pass: 7,320; fail: 710; error: 23 Build 8: aarch64/2017/apr/29 pass: 7,293; fail: 729; error: 32 Build 9: aarch64/2017/may/05 pass: 7,319; fail: 711; error: 28 Build 10: aarch64/2017/may/07 pass: 7,331; fail: 701; error: 26 Build 11: aarch64/2017/may/09 pass: 7,326; fail: 702; error: 31 Build 12: aarch64/2017/may/11 pass: 7,340; fail: 693; error: 27 Build 13: aarch64/2017/may/13 pass: 7,344; fail: 693; error: 23 Build 14: aarch64/2017/may/15 pass: 7,349; fail: 681; error: 30 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/11 pass: 3,889; fail: 1; error: 1 Build 1: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 2: aarch64/2017/apr/15 pass: 3,891 Build 3: aarch64/2017/apr/17 pass: 3,891 Build 4: aarch64/2017/apr/21 pass: 3,894; error: 2 Build 5: aarch64/2017/apr/23 pass: 3,894; error: 3 Build 6: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 7: aarch64/2017/apr/27 pass: 3,896; fail: 1; error: 4 Build 8: aarch64/2017/apr/29 pass: 3,899; error: 2 Build 9: aarch64/2017/may/05 pass: 3,897; error: 4 Build 10: aarch64/2017/may/07 pass: 3,895; error: 6 Build 11: aarch64/2017/may/09 pass: 3,897; error: 5 Build 12: aarch64/2017/may/11 pass: 3,896; error: 6 Build 13: aarch64/2017/may/13 pass: 3,898; error: 5 Build 14: aarch64/2017/may/15 pass: 3,899; error: 4 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/11 pass: 1,403; fail: 7 Build 1: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 2: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 3: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 4: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 Build 5: aarch64/2017/apr/23 pass: 1,404; fail: 7; error: 1 Build 6: aarch64/2017/apr/25 pass: 1,405; fail: 7 Build 7: aarch64/2017/apr/27 pass: 1,405; fail: 7; error: 1 Build 8: aarch64/2017/apr/29 pass: 1,406; fail: 7 Build 9: aarch64/2017/may/05 pass: 1,406; fail: 7 Build 10: aarch64/2017/may/07 pass: 1,405; fail: 7; error: 1 Build 11: aarch64/2017/may/09 pass: 1,406; fail: 7 Build 12: aarch64/2017/may/11 pass: 1,405; fail: 7; error: 1 Build 13: aarch64/2017/may/13 pass: 1,405; fail: 7; error: 1 Build 14: aarch64/2017/may/15 pass: 1,405; fail: 7; error: 1 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/11 pass: 7,312; fail: 708; error: 22 Build 1: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 2: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 3: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 4: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 Build 5: aarch64/2017/apr/23 pass: 7,315; fail: 716; error: 21 Build 6: aarch64/2017/apr/25 pass: 7,319; fail: 709; error: 25 Build 7: aarch64/2017/apr/27 pass: 7,324; fail: 701; error: 28 Build 8: aarch64/2017/apr/29 pass: 7,340; fail: 686; error: 28 Build 9: aarch64/2017/may/05 pass: 7,332; fail: 702; error: 24 Build 10: aarch64/2017/may/07 pass: 7,350; fail: 687; error: 21 Build 11: aarch64/2017/may/09 pass: 7,352; fail: 681; error: 26 Build 12: aarch64/2017/may/11 pass: 7,330; fail: 705; error: 25 Build 13: aarch64/2017/may/13 pass: 7,350; fail: 683; error: 27 Build 14: aarch64/2017/may/15 pass: 7,329; fail: 700; error: 31 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/11 pass: 3,888; fail: 1; error: 2 Build 1: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 2: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 3: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 4: aarch64/2017/apr/21 pass: 3,891; fail: 1; error: 4 Build 5: aarch64/2017/apr/23 pass: 3,893; error: 4 Build 6: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 7: aarch64/2017/apr/27 pass: 3,893; error: 8 Build 8: aarch64/2017/apr/29 pass: 3,896; error: 5 Build 9: aarch64/2017/may/05 pass: 3,896; error: 5 Build 10: aarch64/2017/may/07 pass: 3,895; fail: 1; error: 5 Build 11: aarch64/2017/may/09 pass: 3,896; fail: 1; error: 5 Build 12: aarch64/2017/may/11 pass: 3,897; fail: 1; error: 4 Build 13: aarch64/2017/may/13 pass: 3,899; error: 4 Build 14: aarch64/2017/may/15 pass: 3,898; 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.27x Relative performance: Server critical-jOPS (nc): 0.57x 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: 66.9, Server: 103.03 Client 66.9 / Client 2014-04-01 (43.00): 1.56x Server 103.03 / Server 2014-04-01 (71.00): 1.45x 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-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/ 2017-05-06 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/125/results/ 2017-05-09 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/127/results/ 2017-05-11 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/129/results/ 2017-05-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/131/results/ 2017-05-14 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/133/results/ 2017-05-16 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/135/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 Fri May 19 00:13:38 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 19 May 2017 00:13:38 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <407657555.2665.1495152820129.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/137/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/13 pass: 1,400; fail: 7 Build 1: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 2: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 3: aarch64/2017/apr/21 pass: 1,401; fail: 7 Build 4: aarch64/2017/apr/23 pass: 1,400; fail: 7; error: 1 Build 5: aarch64/2017/apr/25 pass: 1,401; fail: 7 Build 6: aarch64/2017/apr/27 pass: 1,400; fail: 8; error: 1 Build 7: aarch64/2017/apr/29 pass: 1,401; fail: 7; error: 1 Build 8: aarch64/2017/may/05 pass: 1,402; fail: 7 Build 9: aarch64/2017/may/07 pass: 1,402; fail: 7 Build 10: aarch64/2017/may/09 pass: 1,401; fail: 7; error: 1 Build 11: aarch64/2017/may/11 pass: 1,401; fail: 7; error: 1 Build 12: aarch64/2017/may/13 pass: 1,401; fail: 7; error: 1 Build 13: aarch64/2017/may/15 pass: 1,401; fail: 7; error: 1 Build 14: aarch64/2017/may/17 pass: 1,401; fail: 8 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/13 pass: 7,315; fail: 706; error: 22 Build 1: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 2: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 3: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 Build 4: aarch64/2017/apr/23 pass: 7,315; fail: 712; error: 25 Build 5: aarch64/2017/apr/25 pass: 7,341; fail: 689; error: 23 Build 6: aarch64/2017/apr/27 pass: 7,320; fail: 710; error: 23 Build 7: aarch64/2017/apr/29 pass: 7,293; fail: 729; error: 32 Build 8: aarch64/2017/may/05 pass: 7,319; fail: 711; error: 28 Build 9: aarch64/2017/may/07 pass: 7,331; fail: 701; error: 26 Build 10: aarch64/2017/may/09 pass: 7,326; fail: 702; error: 31 Build 11: aarch64/2017/may/11 pass: 7,340; fail: 693; error: 27 Build 12: aarch64/2017/may/13 pass: 7,344; fail: 693; error: 23 Build 13: aarch64/2017/may/15 pass: 7,349; fail: 681; error: 30 Build 14: aarch64/2017/may/17 pass: 7,370; fail: 663; error: 27 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/13 pass: 3,889; fail: 1; error: 1 Build 1: aarch64/2017/apr/15 pass: 3,891 Build 2: aarch64/2017/apr/17 pass: 3,891 Build 3: aarch64/2017/apr/21 pass: 3,894; error: 2 Build 4: aarch64/2017/apr/23 pass: 3,894; error: 3 Build 5: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 6: aarch64/2017/apr/27 pass: 3,896; fail: 1; error: 4 Build 7: aarch64/2017/apr/29 pass: 3,899; error: 2 Build 8: aarch64/2017/may/05 pass: 3,897; error: 4 Build 9: aarch64/2017/may/07 pass: 3,895; error: 6 Build 10: aarch64/2017/may/09 pass: 3,897; error: 5 Build 11: aarch64/2017/may/11 pass: 3,896; error: 6 Build 12: aarch64/2017/may/13 pass: 3,898; error: 5 Build 13: aarch64/2017/may/15 pass: 3,899; error: 4 Build 14: aarch64/2017/may/17 pass: 3,895; fail: 1; error: 7 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/13 pass: 1,404; fail: 7 Build 1: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 2: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 3: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 Build 4: aarch64/2017/apr/23 pass: 1,404; fail: 7; error: 1 Build 5: aarch64/2017/apr/25 pass: 1,405; fail: 7 Build 6: aarch64/2017/apr/27 pass: 1,405; fail: 7; error: 1 Build 7: aarch64/2017/apr/29 pass: 1,406; fail: 7 Build 8: aarch64/2017/may/05 pass: 1,406; fail: 7 Build 9: aarch64/2017/may/07 pass: 1,405; fail: 7; error: 1 Build 10: aarch64/2017/may/09 pass: 1,406; fail: 7 Build 11: aarch64/2017/may/11 pass: 1,405; fail: 7; error: 1 Build 12: aarch64/2017/may/13 pass: 1,405; fail: 7; error: 1 Build 13: aarch64/2017/may/15 pass: 1,405; fail: 7; error: 1 Build 14: aarch64/2017/may/17 pass: 1,406; fail: 7 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/13 pass: 7,341; fail: 682; error: 20 Build 1: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 2: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 3: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 Build 4: aarch64/2017/apr/23 pass: 7,315; fail: 716; error: 21 Build 5: aarch64/2017/apr/25 pass: 7,319; fail: 709; error: 25 Build 6: aarch64/2017/apr/27 pass: 7,324; fail: 701; error: 28 Build 7: aarch64/2017/apr/29 pass: 7,340; fail: 686; error: 28 Build 8: aarch64/2017/may/05 pass: 7,332; fail: 702; error: 24 Build 9: aarch64/2017/may/07 pass: 7,350; fail: 687; error: 21 Build 10: aarch64/2017/may/09 pass: 7,352; fail: 681; error: 26 Build 11: aarch64/2017/may/11 pass: 7,330; fail: 705; error: 25 Build 12: aarch64/2017/may/13 pass: 7,350; fail: 683; error: 27 Build 13: aarch64/2017/may/15 pass: 7,329; fail: 700; error: 31 Build 14: aarch64/2017/may/17 pass: 7,349; fail: 681; error: 30 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/13 pass: 3,890; error: 1 Build 1: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 2: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 3: aarch64/2017/apr/21 pass: 3,891; fail: 1; error: 4 Build 4: aarch64/2017/apr/23 pass: 3,893; error: 4 Build 5: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 6: aarch64/2017/apr/27 pass: 3,893; error: 8 Build 7: aarch64/2017/apr/29 pass: 3,896; error: 5 Build 8: aarch64/2017/may/05 pass: 3,896; error: 5 Build 9: aarch64/2017/may/07 pass: 3,895; fail: 1; error: 5 Build 10: aarch64/2017/may/09 pass: 3,896; fail: 1; error: 5 Build 11: aarch64/2017/may/11 pass: 3,897; fail: 1; error: 4 Build 12: aarch64/2017/may/13 pass: 3,899; error: 4 Build 13: aarch64/2017/may/15 pass: 3,898; fail: 1; error: 4 Build 14: aarch64/2017/may/17 pass: 3,894; fail: 1; 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.70x Relative performance: Server critical-jOPS (nc): 0.58x 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: 64.16, Server: 106.13 Client 64.16 / Client 2014-04-01 (43.00): 1.49x Server 106.13 / Server 2014-04-01 (71.00): 1.49x 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-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/ 2017-05-06 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/125/results/ 2017-05-09 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/127/results/ 2017-05-11 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/129/results/ 2017-05-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/131/results/ 2017-05-14 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/133/results/ 2017-05-16 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/135/results/ 2017-05-19 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/137/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 Sat May 20 22:39:01 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sat, 20 May 2017 22:39:01 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <343063161.3050.1495319942650.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/139/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/15 pass: 1,400; fail: 7 Build 1: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 2: aarch64/2017/apr/21 pass: 1,401; fail: 7 Build 3: aarch64/2017/apr/23 pass: 1,400; fail: 7; error: 1 Build 4: aarch64/2017/apr/25 pass: 1,401; fail: 7 Build 5: aarch64/2017/apr/27 pass: 1,400; fail: 8; error: 1 Build 6: aarch64/2017/apr/29 pass: 1,401; fail: 7; error: 1 Build 7: aarch64/2017/may/05 pass: 1,402; fail: 7 Build 8: aarch64/2017/may/07 pass: 1,402; fail: 7 Build 9: aarch64/2017/may/09 pass: 1,401; fail: 7; error: 1 Build 10: aarch64/2017/may/11 pass: 1,401; fail: 7; error: 1 Build 11: aarch64/2017/may/13 pass: 1,401; fail: 7; error: 1 Build 12: aarch64/2017/may/15 pass: 1,401; fail: 7; error: 1 Build 13: aarch64/2017/may/17 pass: 1,401; fail: 8 Build 14: aarch64/2017/may/19 pass: 1,402; fail: 7 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/15 pass: 7,319; fail: 712; error: 22 Build 1: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 2: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 Build 3: aarch64/2017/apr/23 pass: 7,315; fail: 712; error: 25 Build 4: aarch64/2017/apr/25 pass: 7,341; fail: 689; error: 23 Build 5: aarch64/2017/apr/27 pass: 7,320; fail: 710; error: 23 Build 6: aarch64/2017/apr/29 pass: 7,293; fail: 729; error: 32 Build 7: aarch64/2017/may/05 pass: 7,319; fail: 711; error: 28 Build 8: aarch64/2017/may/07 pass: 7,331; fail: 701; error: 26 Build 9: aarch64/2017/may/09 pass: 7,326; fail: 702; error: 31 Build 10: aarch64/2017/may/11 pass: 7,340; fail: 693; error: 27 Build 11: aarch64/2017/may/13 pass: 7,344; fail: 693; error: 23 Build 12: aarch64/2017/may/15 pass: 7,349; fail: 681; error: 30 Build 13: aarch64/2017/may/17 pass: 7,370; fail: 663; error: 27 Build 14: aarch64/2017/may/19 pass: 7,326; fail: 706; error: 28 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/15 pass: 3,891 Build 1: aarch64/2017/apr/17 pass: 3,891 Build 2: aarch64/2017/apr/21 pass: 3,894; error: 2 Build 3: aarch64/2017/apr/23 pass: 3,894; error: 3 Build 4: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 5: aarch64/2017/apr/27 pass: 3,896; fail: 1; error: 4 Build 6: aarch64/2017/apr/29 pass: 3,899; error: 2 Build 7: aarch64/2017/may/05 pass: 3,897; error: 4 Build 8: aarch64/2017/may/07 pass: 3,895; error: 6 Build 9: aarch64/2017/may/09 pass: 3,897; error: 5 Build 10: aarch64/2017/may/11 pass: 3,896; error: 6 Build 11: aarch64/2017/may/13 pass: 3,898; error: 5 Build 12: aarch64/2017/may/15 pass: 3,899; error: 4 Build 13: aarch64/2017/may/17 pass: 3,895; fail: 1; error: 7 Build 14: aarch64/2017/may/19 pass: 3,896; error: 7 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/15 pass: 1,404; fail: 7 Build 1: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 2: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 Build 3: aarch64/2017/apr/23 pass: 1,404; fail: 7; error: 1 Build 4: aarch64/2017/apr/25 pass: 1,405; fail: 7 Build 5: aarch64/2017/apr/27 pass: 1,405; fail: 7; error: 1 Build 6: aarch64/2017/apr/29 pass: 1,406; fail: 7 Build 7: aarch64/2017/may/05 pass: 1,406; fail: 7 Build 8: aarch64/2017/may/07 pass: 1,405; fail: 7; error: 1 Build 9: aarch64/2017/may/09 pass: 1,406; fail: 7 Build 10: aarch64/2017/may/11 pass: 1,405; fail: 7; error: 1 Build 11: aarch64/2017/may/13 pass: 1,405; fail: 7; error: 1 Build 12: aarch64/2017/may/15 pass: 1,405; fail: 7; error: 1 Build 13: aarch64/2017/may/17 pass: 1,406; fail: 7 Build 14: aarch64/2017/may/19 pass: 1,406; fail: 7 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/15 pass: 7,334; fail: 699; error: 20 Build 1: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 2: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 Build 3: aarch64/2017/apr/23 pass: 7,315; fail: 716; error: 21 Build 4: aarch64/2017/apr/25 pass: 7,319; fail: 709; error: 25 Build 5: aarch64/2017/apr/27 pass: 7,324; fail: 701; error: 28 Build 6: aarch64/2017/apr/29 pass: 7,340; fail: 686; error: 28 Build 7: aarch64/2017/may/05 pass: 7,332; fail: 702; error: 24 Build 8: aarch64/2017/may/07 pass: 7,350; fail: 687; error: 21 Build 9: aarch64/2017/may/09 pass: 7,352; fail: 681; error: 26 Build 10: aarch64/2017/may/11 pass: 7,330; fail: 705; error: 25 Build 11: aarch64/2017/may/13 pass: 7,350; fail: 683; error: 27 Build 12: aarch64/2017/may/15 pass: 7,329; fail: 700; error: 31 Build 13: aarch64/2017/may/17 pass: 7,349; fail: 681; error: 30 Build 14: aarch64/2017/may/19 pass: 7,340; fail: 691; error: 29 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/15 pass: 3,888; fail: 1; error: 2 Build 1: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 2: aarch64/2017/apr/21 pass: 3,891; fail: 1; error: 4 Build 3: aarch64/2017/apr/23 pass: 3,893; error: 4 Build 4: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 5: aarch64/2017/apr/27 pass: 3,893; error: 8 Build 6: aarch64/2017/apr/29 pass: 3,896; error: 5 Build 7: aarch64/2017/may/05 pass: 3,896; error: 5 Build 8: aarch64/2017/may/07 pass: 3,895; fail: 1; error: 5 Build 9: aarch64/2017/may/09 pass: 3,896; fail: 1; error: 5 Build 10: aarch64/2017/may/11 pass: 3,897; fail: 1; error: 4 Build 11: aarch64/2017/may/13 pass: 3,899; error: 4 Build 12: aarch64/2017/may/15 pass: 3,898; fail: 1; error: 4 Build 13: aarch64/2017/may/17 pass: 3,894; fail: 1; error: 8 Build 14: aarch64/2017/may/19 pass: 3,894; fail: 1; 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.27x Relative performance: Server critical-jOPS (nc): 0.57x 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: 63.87, Server: 102.28 Client 63.87 / Client 2014-04-01 (43.00): 1.49x Server 102.28 / Server 2014-04-01 (71.00): 1.44x 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-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/ 2017-05-06 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/125/results/ 2017-05-09 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/127/results/ 2017-05-11 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/129/results/ 2017-05-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/131/results/ 2017-05-14 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/133/results/ 2017-05-16 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/135/results/ 2017-05-19 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/137/results/ 2017-05-20 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/139/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 May 24 23:33:05 2017 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Wed, 24 May 2017 23:33:05 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 9 on AArch64 Message-ID: <1508320345.3732.1495668786869.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/143/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/17 pass: 1,400; fail: 7 Build 1: aarch64/2017/apr/21 pass: 1,401; fail: 7 Build 2: aarch64/2017/apr/23 pass: 1,400; fail: 7; error: 1 Build 3: aarch64/2017/apr/25 pass: 1,401; fail: 7 Build 4: aarch64/2017/apr/27 pass: 1,400; fail: 8; error: 1 Build 5: aarch64/2017/apr/29 pass: 1,401; fail: 7; error: 1 Build 6: aarch64/2017/may/05 pass: 1,402; fail: 7 Build 7: aarch64/2017/may/07 pass: 1,402; fail: 7 Build 8: aarch64/2017/may/09 pass: 1,401; fail: 7; error: 1 Build 9: aarch64/2017/may/11 pass: 1,401; fail: 7; error: 1 Build 10: aarch64/2017/may/13 pass: 1,401; fail: 7; error: 1 Build 11: aarch64/2017/may/15 pass: 1,401; fail: 7; error: 1 Build 12: aarch64/2017/may/17 pass: 1,401; fail: 8 Build 13: aarch64/2017/may/19 pass: 1,402; fail: 7 Build 14: aarch64/2017/may/23 pass: 1,401; fail: 7; error: 1 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/17 pass: 7,327; fail: 703; error: 23 Build 1: aarch64/2017/apr/21 pass: 7,300; fail: 724; error: 28 Build 2: aarch64/2017/apr/23 pass: 7,315; fail: 712; error: 25 Build 3: aarch64/2017/apr/25 pass: 7,341; fail: 689; error: 23 Build 4: aarch64/2017/apr/27 pass: 7,320; fail: 710; error: 23 Build 5: aarch64/2017/apr/29 pass: 7,293; fail: 729; error: 32 Build 6: aarch64/2017/may/05 pass: 7,319; fail: 711; error: 28 Build 7: aarch64/2017/may/07 pass: 7,331; fail: 701; error: 26 Build 8: aarch64/2017/may/09 pass: 7,326; fail: 702; error: 31 Build 9: aarch64/2017/may/11 pass: 7,340; fail: 693; error: 27 Build 10: aarch64/2017/may/13 pass: 7,344; fail: 693; error: 23 Build 11: aarch64/2017/may/15 pass: 7,349; fail: 681; error: 30 Build 12: aarch64/2017/may/17 pass: 7,370; fail: 663; error: 27 Build 13: aarch64/2017/may/19 pass: 7,326; fail: 706; error: 28 Build 14: aarch64/2017/may/23 pass: 7,325; fail: 706; error: 29 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/17 pass: 3,891 Build 1: aarch64/2017/apr/21 pass: 3,894; error: 2 Build 2: aarch64/2017/apr/23 pass: 3,894; error: 3 Build 3: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 4: aarch64/2017/apr/27 pass: 3,896; fail: 1; error: 4 Build 5: aarch64/2017/apr/29 pass: 3,899; error: 2 Build 6: aarch64/2017/may/05 pass: 3,897; error: 4 Build 7: aarch64/2017/may/07 pass: 3,895; error: 6 Build 8: aarch64/2017/may/09 pass: 3,897; error: 5 Build 9: aarch64/2017/may/11 pass: 3,896; error: 6 Build 10: aarch64/2017/may/13 pass: 3,898; error: 5 Build 11: aarch64/2017/may/15 pass: 3,899; error: 4 Build 12: aarch64/2017/may/17 pass: 3,895; fail: 1; error: 7 Build 13: aarch64/2017/may/19 pass: 3,896; error: 7 Build 14: aarch64/2017/may/23 pass: 3,900; error: 3 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/17 pass: 1,404; fail: 7 Build 1: aarch64/2017/apr/21 pass: 1,404; fail: 7; error: 1 Build 2: aarch64/2017/apr/23 pass: 1,404; fail: 7; error: 1 Build 3: aarch64/2017/apr/25 pass: 1,405; fail: 7 Build 4: aarch64/2017/apr/27 pass: 1,405; fail: 7; error: 1 Build 5: aarch64/2017/apr/29 pass: 1,406; fail: 7 Build 6: aarch64/2017/may/05 pass: 1,406; fail: 7 Build 7: aarch64/2017/may/07 pass: 1,405; fail: 7; error: 1 Build 8: aarch64/2017/may/09 pass: 1,406; fail: 7 Build 9: aarch64/2017/may/11 pass: 1,405; fail: 7; error: 1 Build 10: aarch64/2017/may/13 pass: 1,405; fail: 7; error: 1 Build 11: aarch64/2017/may/15 pass: 1,405; fail: 7; error: 1 Build 12: aarch64/2017/may/17 pass: 1,406; fail: 7 Build 13: aarch64/2017/may/19 pass: 1,406; fail: 7 Build 14: aarch64/2017/may/23 pass: 1,405; fail: 7; error: 1 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/17 pass: 7,364; fail: 667; error: 22 Build 1: aarch64/2017/apr/21 pass: 7,334; fail: 696; error: 22 Build 2: aarch64/2017/apr/23 pass: 7,315; fail: 716; error: 21 Build 3: aarch64/2017/apr/25 pass: 7,319; fail: 709; error: 25 Build 4: aarch64/2017/apr/27 pass: 7,324; fail: 701; error: 28 Build 5: aarch64/2017/apr/29 pass: 7,340; fail: 686; error: 28 Build 6: aarch64/2017/may/05 pass: 7,332; fail: 702; error: 24 Build 7: aarch64/2017/may/07 pass: 7,350; fail: 687; error: 21 Build 8: aarch64/2017/may/09 pass: 7,352; fail: 681; error: 26 Build 9: aarch64/2017/may/11 pass: 7,330; fail: 705; error: 25 Build 10: aarch64/2017/may/13 pass: 7,350; fail: 683; error: 27 Build 11: aarch64/2017/may/15 pass: 7,329; fail: 700; error: 31 Build 12: aarch64/2017/may/17 pass: 7,349; fail: 681; error: 30 Build 13: aarch64/2017/may/19 pass: 7,340; fail: 691; error: 29 Build 14: aarch64/2017/may/23 pass: 7,320; fail: 695; error: 45 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2017/apr/17 pass: 3,890; error: 1 Build 1: aarch64/2017/apr/21 pass: 3,891; fail: 1; error: 4 Build 2: aarch64/2017/apr/23 pass: 3,893; error: 4 Build 3: aarch64/2017/apr/25 pass: 3,895; error: 4 Build 4: aarch64/2017/apr/27 pass: 3,893; error: 8 Build 5: aarch64/2017/apr/29 pass: 3,896; error: 5 Build 6: aarch64/2017/may/05 pass: 3,896; error: 5 Build 7: aarch64/2017/may/07 pass: 3,895; fail: 1; error: 5 Build 8: aarch64/2017/may/09 pass: 3,896; fail: 1; error: 5 Build 9: aarch64/2017/may/11 pass: 3,897; fail: 1; error: 4 Build 10: aarch64/2017/may/13 pass: 3,899; error: 4 Build 11: aarch64/2017/may/15 pass: 3,898; fail: 1; error: 4 Build 12: aarch64/2017/may/17 pass: 3,894; fail: 1; error: 8 Build 13: aarch64/2017/may/19 pass: 3,894; fail: 1; error: 8 Build 14: aarch64/2017/may/23 pass: 3,896; error: 7 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.27x Relative performance: Server critical-jOPS (nc): 0.54x 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: 66.58, Server: 100.11 Client 66.58 / Client 2014-04-01 (43.00): 1.55x Server 100.11 / Server 2014-04-01 (71.00): 1.41x 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-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/ 2017-05-06 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/125/results/ 2017-05-09 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/127/results/ 2017-05-11 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/129/results/ 2017-05-12 pass rate: 11551/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/131/results/ 2017-05-14 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/133/results/ 2017-05-16 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/135/results/ 2017-05-19 pass rate: 11553/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/137/results/ 2017-05-20 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/139/results/ 2017-05-24 pass rate: 11552/11554, results: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/2017/143/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk9/jcstress-nightly-runs/