From ci_notify at linaro.org Thu Aug 1 00:21:32 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Thu, 1 Aug 2019 00:21:32 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <853913550.4006.1564618892820.JavaMail.jenkins@6e40b75d9e9e> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2019/212/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/28 pass: 5,649; fail: 3 Build 1: aarch64/2019/jul/01 pass: 5,650; fail: 4 Build 2: aarch64/2019/jul/03 pass: 5,654; fail: 2 Build 3: aarch64/2019/jul/05 pass: 5,653; fail: 3 Build 4: aarch64/2019/jul/09 pass: 5,695; fail: 3 Build 5: aarch64/2019/jul/11 pass: 5,696; fail: 3 Build 6: aarch64/2019/jul/12 pass: 5,695; fail: 5 Build 7: aarch64/2019/jul/15 pass: 5,699; fail: 1 Build 8: aarch64/2019/jul/17 pass: 5,700; fail: 1; error: 1 Build 9: aarch64/2019/jul/19 pass: 5,699; fail: 3; error: 1 Build 10: aarch64/2019/jul/22 pass: 5,705; fail: 2 Build 11: aarch64/2019/jul/24 pass: 5,706; fail: 1 Build 12: aarch64/2019/jul/26 pass: 5,707; fail: 2 Build 13: aarch64/2019/jul/29 pass: 5,705; fail: 4 Build 14: aarch64/2019/jul/31 pass: 5,711; fail: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/28 pass: 8,596; fail: 529; error: 27 Build 1: aarch64/2019/jul/01 pass: 8,601; fail: 536; error: 17 Build 2: aarch64/2019/jul/03 pass: 8,609; fail: 525; error: 21 Build 3: aarch64/2019/jul/05 pass: 8,612; fail: 515; error: 28 Build 4: aarch64/2019/jul/09 pass: 8,604; fail: 532; error: 19 Build 5: aarch64/2019/jul/11 pass: 8,598; fail: 529; error: 31 Build 6: aarch64/2019/jul/12 pass: 8,601; fail: 528; error: 29 Build 7: aarch64/2019/jul/15 pass: 8,602; fail: 533; error: 25 Build 8: aarch64/2019/jul/17 pass: 8,614; fail: 522; error: 24 Build 9: aarch64/2019/jul/19 pass: 8,611; fail: 526; error: 26 Build 10: aarch64/2019/jul/22 pass: 8,628; fail: 511; error: 24 Build 11: aarch64/2019/jul/24 pass: 8,617; fail: 538; error: 26 Build 12: aarch64/2019/jul/26 pass: 8,649; fail: 518; error: 17 Build 13: aarch64/2019/jul/29 pass: 8,640; fail: 520; error: 26 Build 14: aarch64/2019/jul/31 pass: 8,640; fail: 526; error: 24 5 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/28 pass: 3,964 Build 1: aarch64/2019/jul/01 pass: 3,964 Build 2: aarch64/2019/jul/03 pass: 3,964 Build 3: aarch64/2019/jul/05 pass: 3,965 Build 4: aarch64/2019/jul/09 pass: 3,967 Build 5: aarch64/2019/jul/11 pass: 3,968 Build 6: aarch64/2019/jul/12 pass: 3,968 Build 7: aarch64/2019/jul/15 pass: 3,968 Build 8: aarch64/2019/jul/17 pass: 3,968 Build 9: aarch64/2019/jul/19 pass: 3,969 Build 10: aarch64/2019/jul/22 pass: 3,969 Build 11: aarch64/2019/jul/24 pass: 3,970 Build 12: aarch64/2019/jul/26 pass: 3,970 Build 13: aarch64/2019/jul/29 pass: 3,970 Build 14: aarch64/2019/jul/31 pass: 3,970 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.64x Relative performance: Server critical-jOPS (nc): 9.53x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 204.57 Server 204.57 / Server 2014-04-01 (71.00): 2.88x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-01-01 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/365/results/ 2019-06-29 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/179/results/ 2019-07-01 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/182/results/ 2019-07-04 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/184/results/ 2019-07-05 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/186/results/ 2019-07-10 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/190/results/ 2019-07-12 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/192/results/ 2019-07-15 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/196/results/ 2019-07-17 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/198/results/ 2019-07-20 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/200/results/ 2019-07-22 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/203/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/205/results/ 2019-07-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/207/results/ 2019-07-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/210/results/ 2019-08-01 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/212/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From aph at redhat.com Thu Aug 1 00:41:44 2019 From: aph at redhat.com (Andrew Haley) Date: Wed, 31 Jul 2019 17:41:44 -0700 Subject: [aarch64-port-dev ] [11u] RFR 8228400: Remove built-in AArch64 simulator In-Reply-To: <741a213c-2745-d242-d2bb-367d28f04cd3@redhat.com> References: <5e246f51-4cb9-03a2-d4f2-bf0f7bf440f6@redhat.com> <390b1088-6194-bcd8-a1c5-d8cf07a65fd8@redhat.com> <741a213c-2745-d242-d2bb-367d28f04cd3@redhat.com> Message-ID: <5b5c30a1-e6d8-3e6d-7209-dded08d95307@redhat.com> On 7/31/19 7:32 PM, Aleksey Shipilev wrote: > I thought we would remove it in 8u-aarch64, in preparation for > eventual upstreaming. It that case, it makes sense to have all > releases share the same code shape to simplify future backporting. > Simulator is already removed in 14, and assuming we are doing it in > 8u-aarch64, 11u would be the only release left with the built-in > simulator. I see. So, your proposal to do this in order to minimize the size of the aarch64 patch to be imported into 8u? I didn't remove the builtin sim when the AArch64 port was contributed to mainline because it seemed to me to be a pointless change, and it still does. It's not simply laziness, I considered doing this and rejected it. I don't think it aids maintainability. In general, I don't think that source code cleanups should be done to old releases; apart from anything else it messes up the diffs. We don't fix whitespace in old code for the same reason. However, there is a point I accept: one could argue that in a sense the 8u backport is "new", so perhaps a cleanup is justified for that reason. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From vivek.r.deshpande at intel.com Thu Aug 1 00:43:30 2019 From: vivek.r.deshpande at intel.com (Deshpande, Vivek R) Date: Thu, 1 Aug 2019 00:43:30 +0000 Subject: [aarch64-port-dev ] The result of Math.log(3.0) is different on x86_64 and aarch64? In-Reply-To: <12e94f29-c295-678b-98bc-55e02666ffc9@redhat.com> References: <551d3025-1876-acbf-8633-9dada14f3176@redhat.com> <12e94f29-c295-678b-98bc-55e02666ffc9@redhat.com> Message-ID: <53E8E64DB2403849AFD89B7D4DAC8B2AAB6BE17A@fmsmsx121.amr.corp.intel.com> Hi Andrew We have used the assembly code generated from the Intel Libm Math library as intrinsics and they follow the Spec as you have mentioned in your earlier email. Let me know if need any more information. Regards, Vivek -----Original Message----- From: Andrew Dinn [mailto:adinn at redhat.com] Sent: Monday, July 29, 2019 7:44 AM To: Martin Buchholz Cc: Pengfei Li (Arm Technology China) ; bo zhaobo ; Tianhua huang ; Deshpande, Vivek R ; nd ; jdk-dev at openjdk.java.net; aarch64-port-dev at openjdk.java.net Subject: Re: The result of Math.log(3.0) is different on x86_64 and aarch64? On 29/07/2019 15:25, Martin Buchholz wrote: > I was surprised to see the doc of Math.log make it explicit: > > https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/lang > /Math.html#log(double) > > """The computed result must be within 1 ulp of the exact result. > Results must be semi-monotonic.""" Yes, indeed. I had to look up semi-monotonic even though I really ought to have known what it meant :-) Anyway, there is no surprise really once you correlate the thoroughness of that documentation (and the rest ...) with the inestimably efficient purring of the engine that is Joe Darcy's brain. This is one area that really can be nailed down by spec and it is very nice to see that it has been. regards, Andrew Dinn ----------- From adinn at redhat.com Thu Aug 1 07:41:53 2019 From: adinn at redhat.com (Andrew Dinn) Date: Thu, 1 Aug 2019 08:41:53 +0100 Subject: [aarch64-port-dev ] [11u] RFR 8228400: Remove built-in AArch64 simulator In-Reply-To: <5b5c30a1-e6d8-3e6d-7209-dded08d95307@redhat.com> References: <5e246f51-4cb9-03a2-d4f2-bf0f7bf440f6@redhat.com> <390b1088-6194-bcd8-a1c5-d8cf07a65fd8@redhat.com> <741a213c-2745-d242-d2bb-367d28f04cd3@redhat.com> <5b5c30a1-e6d8-3e6d-7209-dded08d95307@redhat.com> Message-ID: <0eddb0ed-094f-89be-068b-ed8a28ade037@redhat.com> On 01/08/2019 01:41, Andrew Haley wrote: > In general, I don't think that source code cleanups should be done to > old releases; apart from anything else it messes up the diffs. We > don't fix whitespace in old code for the same reason. In this case I don't think that applies (in full force) for the reason you gave next ... > However, there is a point I accept: one could argue that in a sense > the 8u backport is "new", so perhaps a cleanup is justified for that > reason. You are correct that applying these changes to 11u will add differences when comparing old and new 11u code around the removal. However, it will also avoid such differences when backporting upstream fixes through 11u into 8u. I think the latter is the more important side of the equation. 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 shade at redhat.com Thu Aug 1 08:17:43 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Thu, 1 Aug 2019 10:17:43 +0200 Subject: [aarch64-port-dev ] [11u] RFR 8228400: Remove built-in AArch64 simulator In-Reply-To: <5b5c30a1-e6d8-3e6d-7209-dded08d95307@redhat.com> References: <5e246f51-4cb9-03a2-d4f2-bf0f7bf440f6@redhat.com> <390b1088-6194-bcd8-a1c5-d8cf07a65fd8@redhat.com> <741a213c-2745-d242-d2bb-367d28f04cd3@redhat.com> <5b5c30a1-e6d8-3e6d-7209-dded08d95307@redhat.com> Message-ID: <82829029-facf-3d9e-cee4-ca35a6d151f7@redhat.com> On 8/1/19 2:41 AM, Andrew Haley wrote: > On 7/31/19 7:32 PM, Aleksey Shipilev wrote: >> I thought we would remove it in 8u-aarch64, in preparation for >> eventual upstreaming. It that case, it makes sense to have all >> releases share the same code shape to simplify future backporting. >> Simulator is already removed in 14, and assuming we are doing it in >> 8u-aarch64, 11u would be the only release left with the built-in >> simulator. > > I see. So, your proposal to do this in order to minimize the size of > the aarch64 patch to be imported into 8u? Yes. That is the whole reason for my recent aarch64-port work. > I didn't remove the builtin sim when the AArch64 port was contributed to mainline because it > seemed to me to be a pointless change, and it still does. It's not simply laziness, I considered > doing this and rejected it. I don't think it aids maintainability. I disagree. You might be affected by close familiarity with that code. However, I have actually read the entire 8u-aarch64-vs-8u-upstream webrev, and having dead code there does not improve that experience. Neither does it improve backporting, as I see review threads asking "what do we do with BUILTIN_SIM paths" with aarch64 maintainers having to step in and telling to ignore those paths. If those paths are that irrelevant, they have to be removed to eliminate confusion. That is what "aiding maintainability" is. > However, there is a point I accept: one could argue that in a sense > the 8u backport is "new", so perhaps a cleanup is justified for that > reason. Yes, so as I said, that would leave 11u in the awkward position of being different with both 8u-aarch64 and jdk14+. Shenandoah experience tells us the effort taken to maintain similar code shape pays back for future backports: most backports would apply cleanly then, requiring no additional review. Anyway, I have formally requested the backport of JDK-8228400 with jdk11u-fix-request. If you still feel it should not be in 11u, please formally reject it with jdk11u-fix-no. I would then give up here, and move on backporting this removal to 8u-aarch64. -- Thanks, -Aleksey From adinn at redhat.com Thu Aug 1 09:55:40 2019 From: adinn at redhat.com (Andrew Dinn) Date: Thu, 1 Aug 2019 10:55:40 +0100 Subject: [aarch64-port-dev ] The result of Math.log(3.0) is different on x86_64 and aarch64? In-Reply-To: <53E8E64DB2403849AFD89B7D4DAC8B2AAB6BE17A@fmsmsx121.amr.corp.intel.com> References: <551d3025-1876-acbf-8633-9dada14f3176@redhat.com> <12e94f29-c295-678b-98bc-55e02666ffc9@redhat.com> <53E8E64DB2403849AFD89B7D4DAC8B2AAB6BE17A@fmsmsx121.amr.corp.intel.com> Message-ID: Hi Vivek, On 01/08/2019 01:43, Deshpande, Vivek R wrote: > Hi Andrew > > We have used the assembly code generated from the Intel Libm Math > library as intrinsics and they follow the Spec as you have mentioned > in your earlier email. Let me know if need any more information. Thanks for explaining the provenance of this code. I am fine with that explanation (and most of all with you maintaining it ;-). 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 Thu Aug 1 16:47:50 2019 From: gnu.andrew at redhat.com (Andrew John Hughes) Date: Thu, 1 Aug 2019 17:47:50 +0100 Subject: [aarch64-port-dev ] [RFR] [8u] 8u232-b01 Upstream Sync Message-ID: <1cf9062f-d369-d1f4-0a5b-b6c099bab636@redhat.com> Webrevs: https://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/ Merge changesets: http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/corba/b09.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jaxp/b09.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jaxws/b09.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jdk/b09.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/hotspot/b09.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/langtools/b09.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/nashorn/b09.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/root/b09.changeset Changes in aarch64-shenandoah-jdk8u232-b01: - S6913047: Long term memory leak when using PKCS11 and JCE exceeds 32 bit process address space - S6946830: javax.crypto.Cipher.doFinal behavior differs depending on platform - S6996807: FieldReflectorKey hash code computation can be improved - S8030993: Check jdk/src/share/native/common/jni_util.c for JNI pending exceptions - S8075136: Unnecessary sign extension for byte array access - S8075544: Add tiered testing definitions to the jdk repo - S8075573: Add jdk_other and jdk_svc to jdk tier 2 test definition - S8151486: Class.forName causes memory leak - S8152856: Xcode 7.3 -Wshift-negative-value compile failure on Mac OS X - S8168417: Pending exceptions in java.base/windows/native/libnio - S8170494: JNI exception pending in PlainDatagramSocketImpl.c - S8182999: SunEC throws ProviderException on invalid curves - S8185900: hotspot build failed with gcc version Red Hat 4.4.7-3 - S8185979: PPC64: Implement SHA2 intrinsic - S8197930: JNI exception pending in initializeEncoding of jni_util.c - S8202353: os::readdir should use readdir instead of readdir_r - S8205587: Implicit function declaration in jni_util.c - S8210761: libjsig is being compiled without optimization - S8214002: Cannot use italic font style if the font has embedded bitmap - S8218721: C1's CEE optimization produces safepoint poll with invalid debug information - S8218854: FontMetrics.getMaxAdvance may be less than the maximum FontMetrics.charWidth - S8219807: C2 crash in IfNode::up_one_dom(Node*, bool) - S8221304: Problem list java/awt/FontMetrics/MaxAdvanceIsMax.java - S8223219: Backport of JDK-8199552 to OpenJDK 8 leads to duplicate -fstack-protector flags, overriding --with-extra-cflags - S8225636: SA can't handle prelinked libraries - S8226392: Launcher should not enable legacy stdio streams on GNU/Linux (glibc) - S8226870: OpenJDK 8u JRE contains clhsdb and hsdb launchers - S8226928: [TESTBUG] test/java/net/NetworkInterface/IPv4Only.java fails intermittently on AIX - S8227018: CompletableFuture should not call Runtime.availableProcessors on fast path - S8228405: Incorrect format strings in PhaseIdealLoop::rc_predicate - S8228406: Superfluous change in chaitin.hpp Main issues of note: Some manual merging needed for the architecture case statements in test/compiler/intrinsics/sha/cli/testcases/GenericTestCaseForOtherCPU.java and test/compiler/testlibrary/sha/predicate/IntrinsicPredicates.java diffstat for root b/.hgtags | 3 +++ b/common/autoconf/flags.m4 | 16 ++-------------- b/common/autoconf/generated-configure.sh | 18 +++--------------- 3 files changed, 8 insertions(+), 29 deletions(-) diffstat for corba b/.hgtags | 3 +++ 1 file changed, 3 insertions(+) diffstat for jaxp b/.hgtags | 3 +++ 1 file changed, 3 insertions(+) diffstat for jaxws b/.hgtags | 3 +++ 1 file changed, 3 insertions(+) diffstat for langtools b/.hgtags | 3 +++ 1 file changed, 3 insertions(+) diffstat for nashorn b/.hgtags | 3 +++ 1 file changed, 3 insertions(+) diffstat for jdk b/.hgtags | 3 b/make/Images.gmk | 4 b/make/mapfiles/launchers/mapfile-x86 | 5 b/make/mapfiles/libj2pkcs11/mapfile-vers | 2 b/src/share/classes/java/io/ObjectStreamClass.java | 16 b/src/share/classes/java/lang/ClassLoader.java | 7 b/src/share/classes/java/util/concurrent/CompletableFuture.java | 17 b/src/share/classes/sun/security/pkcs11/P11Cipher.java | 126 +- b/src/share/classes/sun/security/pkcs11/P11DHKeyFactory.java | 16 b/src/share/classes/sun/security/pkcs11/P11DSAKeyFactory.java | 16 b/src/share/classes/sun/security/pkcs11/P11Digest.java | 10 b/src/share/classes/sun/security/pkcs11/P11ECDHKeyAgreement.java | 14 b/src/share/classes/sun/security/pkcs11/P11ECKeyFactory.java | 12 b/src/share/classes/sun/security/pkcs11/P11Key.java | 294 +++++- b/src/share/classes/sun/security/pkcs11/P11KeyAgreement.java | 15 b/src/share/classes/sun/security/pkcs11/P11KeyStore.java | 20 b/src/share/classes/sun/security/pkcs11/P11Mac.java | 117 +- b/src/share/classes/sun/security/pkcs11/P11RSACipher.java | 153 ++- b/src/share/classes/sun/security/pkcs11/P11RSAKeyFactory.java | 23 b/src/share/classes/sun/security/pkcs11/P11SecretKeyFactory.java | 10 b/src/share/classes/sun/security/pkcs11/P11Signature.java | 101 +- b/src/share/classes/sun/security/pkcs11/P11TlsKeyMaterialGenerator.java | 10 b/src/share/classes/sun/security/pkcs11/P11TlsMasterSecretGenerator.java | 7 b/src/share/classes/sun/security/pkcs11/P11TlsPrfGenerator.java | 18 b/src/share/classes/sun/security/pkcs11/wrapper/PKCS11.java | 42 b/src/share/lib/security/java.policy | 2 b/src/share/native/common/jni_util.c | 55 - b/src/share/native/sun/font/freetypeScaler.c | 24 b/src/share/native/sun/security/pkcs11/wrapper/p11_keymgmt.c | 438 ++++++++++ b/src/share/native/sun/security/pkcs11/wrapper/pkcs11t.h | 1 b/src/share/native/sun/security/pkcs11/wrapper/pkcs11wrapper.h | 2 b/src/solaris/native/java/net/PlainDatagramSocketImpl.c | 1 b/src/windows/native/sun/nio/ch/FileDispatcherImpl.c | 2 b/test/ProblemList.txt | 3 b/test/TEST.groups | 27 b/test/java/awt/FontMetrics/MaxAdvanceIsMax.java | 143 +++ b/test/java/awt/font/TextLayout/FontGlyphCompare.java | 89 ++ b/test/java/lang/ClassLoader/forNameLeak/ClassForName.java | 45 + b/test/java/lang/ClassLoader/forNameLeak/ClassForNameLeak.java | 123 ++ b/test/java/lang/ClassLoader/forNameLeak/test.policy | 6 b/test/java/net/NetworkInterface/IPv4Only.java | 6 b/test/javax/crypto/Cipher/EmptyFinalBuffer.java | 85 + 42 files changed, 1758 insertions(+), 352 deletions(-) diffstat for hotspot b/.hgtags | 3 b/agent/src/os/linux/ps_core.c | 51 b/make/aix/makefiles/jsig.make | 7 b/make/bsd/makefiles/jsig.make | 7 b/make/linux/makefiles/jsig.make | 7 b/make/solaris/makefiles/jsig.make | 7 b/src/cpu/ppc/vm/assembler_ppc.hpp | 7 b/src/cpu/ppc/vm/assembler_ppc.inline.hpp | 19 b/src/cpu/ppc/vm/macroAssembler_ppc.hpp | 34 b/src/cpu/ppc/vm/macroAssembler_ppc_sha.cpp | 1136 ++++++++++ b/src/cpu/ppc/vm/stubGenerator_ppc.cpp | 31 b/src/cpu/ppc/vm/stubRoutines_ppc_64.hpp | 2 b/src/cpu/ppc/vm/vm_version_ppc.cpp | 41 b/src/cpu/ppc/vm/vm_version_ppc.hpp | 3 b/src/os/aix/vm/os_aix.cpp | 3 b/src/os/aix/vm/os_aix.inline.hpp | 35 b/src/os/aix/vm/perfMemory_aix.cpp | 13 b/src/os/bsd/vm/os_bsd.cpp | 3 b/src/os/bsd/vm/os_bsd.inline.hpp | 33 b/src/os/bsd/vm/perfMemory_bsd.cpp | 13 b/src/os/linux/vm/os_linux.cpp | 3 b/src/os/linux/vm/os_linux.inline.hpp | 33 b/src/os/linux/vm/perfMemory_linux.cpp | 14 b/src/os/posix/vm/os_posix.cpp | 15 b/src/os/solaris/vm/os_solaris.cpp | 4 b/src/os/solaris/vm/os_solaris.inline.hpp | 31 b/src/os/solaris/vm/perfMemory_solaris.cpp | 13 b/src/os/windows/vm/os_windows.cpp | 8 b/src/os/windows/vm/os_windows.inline.hpp | 8 b/src/os/windows/vm/perfMemory_windows.cpp | 12 b/src/share/vm/c1/c1_Optimizer.cpp | 8 b/src/share/vm/oops/instanceKlass.cpp | 4 b/src/share/vm/oops/klass.hpp | 3 b/src/share/vm/opto/ifnode.cpp | 2 b/src/share/vm/opto/library_call.cpp | 20 b/src/share/vm/opto/runtime.cpp | 22 b/src/share/vm/runtime/arguments.cpp | 12 b/src/share/vm/runtime/os.hpp | 3 b/src/share/vm/services/classLoadingService.cpp | 4 b/test/compiler/c1/TestGotoIf.jasm | 171 + b/test/compiler/c1/TestGotoIfMain.java | 46 b/test/compiler/c2/TestIfWithDeadRegion.java | 57 b/test/compiler/intrinsics/sha/cli/testcases/GenericTestCaseForOtherCPU.java | 3 b/test/compiler/testlibrary/sha/predicate/IntrinsicPredicates.java | 23 44 files changed, 1719 insertions(+), 255 deletions(-) Successfully built on x86, x86_64, s390, s390x, ppc, ppc64, ppc64le & aarch64. Ok to push? -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 https://keybase.io/gnu_andrew From shade at redhat.com Thu Aug 1 17:19:24 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Thu, 1 Aug 2019 19:19:24 +0200 Subject: [aarch64-port-dev ] [RFR] [8u] 8u232-b01 Upstream Sync In-Reply-To: <1cf9062f-d369-d1f4-0a5b-b6c099bab636@redhat.com> References: <1cf9062f-d369-d1f4-0a5b-b6c099bab636@redhat.com> Message-ID: <66da71a4-6035-0e02-616b-c0e7b275bcbe@redhat.com> The links to changesets below are broken, they are not "b09.changeset", but rather "$project.patch". Anyway: On 8/1/19 6:47 PM, Andrew John Hughes wrote: > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/corba/b09.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jaxp/b09.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jaxws/b09.changeset Look trivially good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jdk/b09.changeset Looks good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/hotspot/b09.changeset I don't understand where change to chaitin.hpp is coming from, really: http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/hotspot/src/share/vm/opto/chaitin.hpp.sdiff.html It seems both sides of the merge have the "if" branch removed: http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/file/bfff0a0ccb0e/src/share/vm/opto/chaitin.hpp#l323 http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/file/7570e7d49957/src/share/vm/opto/chaitin.hpp#l323 Maybe I don't understand how webrev was generated. Otherwise looks good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/langtools/b09.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/nashorn/b09.changeset Look trivially good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/root/b09.changeset Looks good. -- Thanks, -Aleksey From aph at redhat.com Thu Aug 1 17:31:52 2019 From: aph at redhat.com (Andrew Haley) Date: Thu, 1 Aug 2019 10:31:52 -0700 Subject: [aarch64-port-dev ] [11u] RFR 8228400: Remove built-in AArch64 simulator In-Reply-To: <0eddb0ed-094f-89be-068b-ed8a28ade037@redhat.com> References: <5e246f51-4cb9-03a2-d4f2-bf0f7bf440f6@redhat.com> <390b1088-6194-bcd8-a1c5-d8cf07a65fd8@redhat.com> <741a213c-2745-d242-d2bb-367d28f04cd3@redhat.com> <5b5c30a1-e6d8-3e6d-7209-dded08d95307@redhat.com> <0eddb0ed-094f-89be-068b-ed8a28ade037@redhat.com> Message-ID: <42ec36c4-e4e8-6cd0-be63-65dc4aaab549@redhat.com> On 8/1/19 8:41 AM, Andrew Dinn wrote: > On 01/08/2019 01:41, Andrew Haley wrote: >> In general, I don't think that source code cleanups should be done to >> old releases; apart from anything else it messes up the diffs. We >> don't fix whitespace in old code for the same reason. > > In this case I don't think that applies (in full force) for the reason > you gave next ... Yep. That's why I wrote it: this is a dilemma. >> However, there is a point I accept: one could argue that in a sense >> the 8u backport is "new", so perhaps a cleanup is justified for that >> reason. > You are correct that applying these changes to 11u will add differences > when comparing old and new 11u code around the removal. However, it will > also avoid such differences when backporting upstream fixes through 11u > into 8u. I think the latter is the more important side of the equation. Argh. OK, I'll withdraw my objection in this special case, and because the code in question is aarch64-port, not mainline 8u. But please, let's not do this any more. No "cleanups" to historically-archived code. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Thu Aug 1 17:54:01 2019 From: aph at redhat.com (Andrew Haley) Date: Thu, 1 Aug 2019 10:54:01 -0700 Subject: [aarch64-port-dev ] [11u] RFR 8228400: Remove built-in AArch64 simulator In-Reply-To: <82829029-facf-3d9e-cee4-ca35a6d151f7@redhat.com> References: <5e246f51-4cb9-03a2-d4f2-bf0f7bf440f6@redhat.com> <390b1088-6194-bcd8-a1c5-d8cf07a65fd8@redhat.com> <741a213c-2745-d242-d2bb-367d28f04cd3@redhat.com> <5b5c30a1-e6d8-3e6d-7209-dded08d95307@redhat.com> <82829029-facf-3d9e-cee4-ca35a6d151f7@redhat.com> Message-ID: <52cc6d46-3bfd-edda-bb7e-c2b59aa36d72@redhat.com> On 8/1/19 9:17 AM, Aleksey Shipilev wrote: > On 8/1/19 2:41 AM, Andrew Haley wrote: >> On 7/31/19 7:32 PM, Aleksey Shipilev wrote: >>> I thought we would remove it in 8u-aarch64, in preparation for >>> eventual upstreaming. It that case, it makes sense to have all >>> releases share the same code shape to simplify future backporting. >>> Simulator is already removed in 14, and assuming we are doing it in >>> 8u-aarch64, 11u would be the only release left with the built-in >>> simulator. >> >> I see. So, your proposal to do this in order to minimize the size of >> the aarch64 patch to be imported into 8u? > > Yes. That is the whole reason for my recent aarch64-port work. OK. >> I didn't remove the builtin sim when the AArch64 port was >> contributed to mainline because it seemed to me to be a pointless >> change, and it still does. It's not simply laziness, I considered >> doing this and rejected it. I don't think it aids maintainability. > I disagree. Yes, I get that. :-) > You might be affected by close familiarity with that code. However, > I have actually read the entire 8u-aarch64-vs-8u-upstream webrev, > and having dead code there does not improve that experience. Neither > does it improve backporting, as I see review threads asking "what do > we do with BUILTIN_SIM paths" with aarch64 maintainers having to > step in and telling to ignore those paths. If those paths are that > irrelevant, they have to be removed to eliminate confusion. That is > what "aiding maintainability" is. It's one aspect of maintainability. Clean history is another. >> However, there is a point I accept: one could argue that in a sense >> the 8u backport is "new", so perhaps a cleanup is justified for that >> reason. > > Yes, so as I said, that would leave 11u in the awkward position of > being different with both 8u-aarch64 and jdk14+. Shenandoah > experience tells us the effort taken to maintain similar code shape > pays back for future backports: most backports would apply cleanly > then, requiring no additional review. Sure, but this means that code cleanups always have this disadvantage, that of making backports harder. One black mark against cleanups, I guess. > Anyway, I have formally requested the backport of JDK-8228400 with > jdk11u-fix-request. If you still feel it should not be in 11u, > please formally reject it with jdk11u-fix-no. I would then give up > here, and move on backporting this removal to 8u-aarch64. I'll think some more. I can see both sides of this, and I guess the builtin sim is a special case. I am certainly not going to treat this as a precedent for future cleanups. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Fri Aug 2 07:30:19 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 2 Aug 2019 07:30:19 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 13 on AArch64 Message-ID: <979464380.4264.1564731020304.JavaMail.jenkins@6e40b75d9e9e> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk13/openjdk-jtreg-nightly-tests/summary/2019/213/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/20 pass: 5,645; fail: 2; error: 1 Build 1: aarch64/2019/jun/22 pass: 5,645; fail: 3 Build 2: aarch64/2019/jun/25 pass: 5,644; fail: 2; error: 1 Build 3: aarch64/2019/jun/27 pass: 5,645; fail: 2 Build 4: aarch64/2019/jun/29 pass: 5,644; fail: 3 Build 5: aarch64/2019/jul/02 pass: 5,645; fail: 2 Build 6: aarch64/2019/jul/04 pass: 5,644; fail: 2; error: 1 Build 7: aarch64/2019/jul/09 pass: 5,643; fail: 4 Build 8: aarch64/2019/jul/16 pass: 5,646; fail: 1 Build 9: aarch64/2019/jul/18 pass: 5,644; fail: 2; error: 1 Build 10: aarch64/2019/jul/20 pass: 5,645; fail: 1; error: 1 Build 11: aarch64/2019/jul/23 pass: 5,644; fail: 3 Build 12: aarch64/2019/jul/25 pass: 5,644; fail: 3 Build 13: aarch64/2019/jul/30 pass: 5,645; fail: 2 Build 14: aarch64/2019/aug/01 pass: 5,646; fail: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/20 pass: 8,592; fail: 524; error: 30 Build 1: aarch64/2019/jun/22 pass: 8,599; fail: 523; error: 24 Build 2: aarch64/2019/jun/25 pass: 8,603; fail: 525; error: 18 Build 3: aarch64/2019/jun/27 pass: 8,609; fail: 512; error: 26 Build 4: aarch64/2019/jun/29 pass: 8,601; fail: 520; error: 29 Build 5: aarch64/2019/jul/02 pass: 8,604; fail: 521; error: 25 Build 6: aarch64/2019/jul/04 pass: 8,601; fail: 523; error: 26 Build 7: aarch64/2019/jul/09 pass: 8,606; fail: 515; error: 29 Build 8: aarch64/2019/jul/16 pass: 8,593; fail: 531; error: 30 Build 9: aarch64/2019/jul/18 pass: 8,618; fail: 527; error: 26 Build 10: aarch64/2019/jul/20 pass: 8,619; fail: 519; error: 33 Build 11: aarch64/2019/jul/23 pass: 8,616; fail: 525; error: 30 Build 12: aarch64/2019/jul/25 pass: 8,620; fail: 528; error: 23 Build 13: aarch64/2019/jul/30 pass: 8,610; fail: 529; error: 32 Build 14: aarch64/2019/aug/01 pass: 8,620; fail: 527; error: 24 4 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/20 pass: 3,962 Build 1: aarch64/2019/jun/22 pass: 3,962 Build 2: aarch64/2019/jun/25 pass: 3,962 Build 3: aarch64/2019/jun/27 pass: 3,962 Build 4: aarch64/2019/jun/29 pass: 3,962 Build 5: aarch64/2019/jul/02 pass: 3,962 Build 6: aarch64/2019/jul/04 pass: 3,962 Build 7: aarch64/2019/jul/09 pass: 3,962 Build 8: aarch64/2019/jul/16 pass: 3,963 Build 9: aarch64/2019/jul/18 pass: 3,964 Build 10: aarch64/2019/jul/20 pass: 3,964 Build 11: aarch64/2019/jul/23 pass: 3,964 Build 12: aarch64/2019/jul/25 pass: 3,964 Build 13: aarch64/2019/jul/30 pass: 3,964 Build 14: aarch64/2019/aug/01 pass: 3,964 Previous results can be found here: http://openjdk.linaro.org/jdk13/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.71x Relative performance: Server critical-jOPS (nc): 6.93x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk13/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 204.57 Server 204.57 / Server 2014-04-01 (71.00): 2.88x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk13/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-06-21 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/171/results/ 2019-06-23 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/173/results/ 2019-06-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/176/results/ 2019-06-28 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/178/results/ 2019-06-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/180/results/ 2019-07-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/183/results/ 2019-07-04 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/185/results/ 2019-07-10 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/190/results/ 2019-07-16 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/197/results/ 2019-07-19 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/199/results/ 2019-07-21 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/201/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/204/results/ 2019-07-26 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/211/results/ 2019-08-02 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/213/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/ From ci_notify at linaro.org Fri Aug 2 07:32:22 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 2 Aug 2019 07:32:22 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <1193129241.4266.1564731142889.JavaMail.jenkins@6e40b75d9e9e> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/summary/2019/213/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/feb/14 pass: 799; fail: 9; error: 3 Build 1: aarch64/2019/feb/26 pass: 799; fail: 9; error: 3 Build 2: aarch64/2019/feb/28 pass: 803; fail: 9; error: 2 Build 3: aarch64/2019/mar/26 pass: 799; fail: 13; error: 2 Build 4: aarch64/2019/apr/09 pass: 807; fail: 9; error: 2 Build 5: aarch64/2019/apr/18 pass: 815; fail: 10 Build 6: aarch64/2019/apr/30 pass: 797; fail: 23; error: 9 Build 7: aarch64/2019/may/02 pass: 814; fail: 14; error: 2 Build 8: aarch64/2019/jun/15 pass: 815; fail: 22; error: 1 Build 9: aarch64/2019/jun/20 pass: 820; fail: 16; error: 2 Build 10: aarch64/2019/jun/29 pass: 807; fail: 25; error: 6 Build 11: aarch64/2019/jul/19 pass: 814; fail: 20; error: 4 Build 12: aarch64/2019/jul/25 pass: 802; fail: 25; error: 11 Build 13: aarch64/2019/jul/30 pass: 787; fail: 40; error: 11 Build 14: aarch64/2019/aug/01 pass: 800; fail: 26; error: 12 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/feb/14 pass: 5,761; fail: 257; error: 24 Build 1: aarch64/2019/feb/26 pass: 5,756; fail: 259; error: 27 Build 2: aarch64/2019/feb/28 pass: 5,749; fail: 268; error: 26 Build 3: aarch64/2019/mar/26 pass: 5,768; fail: 246; error: 29 Build 4: aarch64/2019/apr/09 pass: 5,763; fail: 267; error: 24 Build 5: aarch64/2019/apr/18 pass: 5,784; fail: 259; error: 25 Build 6: aarch64/2019/apr/30 pass: 5,779; fail: 262; error: 27 Build 7: aarch64/2019/may/02 pass: 5,784; fail: 262; error: 22 Build 8: aarch64/2019/jun/15 pass: 5,827; fail: 242; error: 22 Build 9: aarch64/2019/jun/20 pass: 5,821; fail: 244; error: 26 Build 10: aarch64/2019/jun/29 pass: 5,799; fail: 265; error: 27 Build 11: aarch64/2019/jul/19 pass: 5,940; fail: 278; error: 22 Build 12: aarch64/2019/jul/25 pass: 5,938; fail: 276; error: 26 Build 13: aarch64/2019/jul/30 pass: 5,942; fail: 273; error: 25 Build 14: aarch64/2019/aug/01 pass: 5,945; fail: 271; error: 24 ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/feb/14 pass: 3,114; fail: 2 Build 1: aarch64/2019/feb/26 pass: 3,114; fail: 2 Build 2: aarch64/2019/feb/28 pass: 3,114; fail: 2 Build 3: aarch64/2019/mar/26 pass: 3,114; fail: 2 Build 4: aarch64/2019/apr/09 pass: 3,115; fail: 2 Build 5: aarch64/2019/apr/18 pass: 3,115; fail: 2 Build 6: aarch64/2019/apr/30 pass: 3,115; fail: 2 Build 7: aarch64/2019/may/02 pass: 3,115; fail: 2 Build 8: aarch64/2019/jun/15 pass: 3,116; fail: 2 Build 9: aarch64/2019/jun/20 pass: 3,116; fail: 2 Build 10: aarch64/2019/jun/29 pass: 3,116; fail: 2 Build 11: aarch64/2019/jul/19 pass: 3,116; fail: 2 Build 12: aarch64/2019/jul/25 pass: 3,116; fail: 2 Build 13: aarch64/2019/jul/30 pass: 3,116; fail: 2 Build 14: aarch64/2019/aug/01 pass: 3,116; fail: 2 Previous results can be found here: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 6.57x Relative performance: Server critical-jOPS (nc): 7.82x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 174.26 Server 174.26 / Server 2014-04-01 (71.00): 2.45x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-02-14 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/045/results/ 2019-02-27 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/057/results/ 2019-02-28 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/059/results/ 2019-03-26 pass rate: 8490/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/085/results/ 2019-04-09 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/099/results/ 2019-04-19 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/108/results/ 2019-04-30 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/120/results/ 2019-05-02 pass rate: 8490/8490, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/122/results/ 2019-06-16 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/166/results/ 2019-06-21 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/171/results/ 2019-06-30 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/180/results/ 2019-07-20 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/200/results/ 2019-07-26 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/211/results/ 2019-08-02 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/213/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From gnu.andrew at redhat.com Fri Aug 2 14:12:02 2019 From: gnu.andrew at redhat.com (Andrew John Hughes) Date: Fri, 2 Aug 2019 15:12:02 +0100 Subject: [aarch64-port-dev ] [RFR] [8u] 8u232-b01 Upstream Sync In-Reply-To: <66da71a4-6035-0e02-616b-c0e7b275bcbe@redhat.com> References: <1cf9062f-d369-d1f4-0a5b-b6c099bab636@redhat.com> <66da71a4-6035-0e02-616b-c0e7b275bcbe@redhat.com> Message-ID: <2dd57c4a-91e5-a6f8-771a-5c5d337beb44@redhat.com> On 01/08/2019 18:19, Aleksey Shipilev wrote: > The links to changesets below are broken, they are not "b09.changeset", but rather "$project.patch". Knew I shouldn't have copied from the joint e-mail. No, they should be merge.changeset. The others are the webrev patch files, which there's no point in linking to separately. http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/corba/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jaxp/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jaxws/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jdk/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/hotspot/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/langtools/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/nashorn/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/root/merge.changeset > Anyway: > > On 8/1/19 6:47 PM, Andrew John Hughes wrote: >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/corba/b09.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jaxp/b09.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jaxws/b09.changeset > > Look trivially good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jdk/b09.changeset > > Looks good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/hotspot/b09.changeset > > I don't understand where change to chaitin.hpp is coming from, really: > > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/hotspot/src/share/vm/opto/chaitin.hpp.sdiff.html > > It seems both sides of the merge have the "if" branch removed: > http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/file/bfff0a0ccb0e/src/share/vm/opto/chaitin.hpp#l323 > > http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/file/7570e7d49957/src/share/vm/opto/chaitin.hpp#l323 > > Maybe I don't understand how webrev was generated. > There isn't one in this merge: https://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/hotspot/merge.changeset diffstat for hotspot b/.hgtags | 3 b/agent/src/os/linux/ps_core.c | 51 b/make/aix/makefiles/jsig.make | 7 b/make/bsd/makefiles/jsig.make | 7 b/make/linux/makefiles/jsig.make | 7 b/make/solaris/makefiles/jsig.make | 7 b/src/cpu/ppc/vm/assembler_ppc.hpp | 7 b/src/cpu/ppc/vm/assembler_ppc.inline.hpp | 19 b/src/cpu/ppc/vm/macroAssembler_ppc.hpp | 34 b/src/cpu/ppc/vm/macroAssembler_ppc_sha.cpp | 1136 ++++++++++ b/src/cpu/ppc/vm/stubGenerator_ppc.cpp | 31 b/src/cpu/ppc/vm/stubRoutines_ppc_64.hpp | 2 b/src/cpu/ppc/vm/vm_version_ppc.cpp | 41 b/src/cpu/ppc/vm/vm_version_ppc.hpp | 3 b/src/os/aix/vm/os_aix.cpp | 3 b/src/os/aix/vm/os_aix.inline.hpp | 35 b/src/os/aix/vm/perfMemory_aix.cpp | 13 b/src/os/bsd/vm/os_bsd.cpp | 3 b/src/os/bsd/vm/os_bsd.inline.hpp | 33 b/src/os/bsd/vm/perfMemory_bsd.cpp | 13 b/src/os/linux/vm/os_linux.cpp | 3 b/src/os/linux/vm/os_linux.inline.hpp | 33 b/src/os/linux/vm/perfMemory_linux.cpp | 14 b/src/os/posix/vm/os_posix.cpp | 15 b/src/os/solaris/vm/os_solaris.cpp | 4 b/src/os/solaris/vm/os_solaris.inline.hpp | 31 b/src/os/solaris/vm/perfMemory_solaris.cpp | 13 b/src/os/windows/vm/os_windows.cpp | 8 b/src/os/windows/vm/os_windows.inline.hpp | 8 b/src/os/windows/vm/perfMemory_windows.cpp | 12 b/src/share/vm/c1/c1_Optimizer.cpp | 8 b/src/share/vm/oops/instanceKlass.cpp | 4 b/src/share/vm/oops/klass.hpp | 3 b/src/share/vm/opto/ifnode.cpp | 2 b/src/share/vm/opto/library_call.cpp | 20 b/src/share/vm/opto/runtime.cpp | 22 b/src/share/vm/runtime/arguments.cpp | 12 b/src/share/vm/runtime/os.hpp | 3 b/src/share/vm/services/classLoadingService.cpp | 4 b/test/compiler/c1/TestGotoIf.jasm | 171 + b/test/compiler/c1/TestGotoIfMain.java | 46 b/test/compiler/c2/TestIfWithDeadRegion.java | 57 b/test/compiler/intrinsics/sha/cli/testcases/GenericTestCaseForOtherCPU.java | 3 b/test/compiler/testlibrary/sha/predicate/IntrinsicPredicates.java | 23 44 files changed, 1719 insertions(+), 255 deletions(-) This is precisely why I provide the merge changesets and diffstat info. webrev is probably confused by some previous merge or other. > Otherwise looks good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/langtools/b09.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/nashorn/b09.changeset > > Look trivially good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/root/b09.changeset > Looks good. > -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 https://keybase.io/gnu_andrew From shade at redhat.com Fri Aug 2 16:19:43 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Fri, 2 Aug 2019 18:19:43 +0200 Subject: [aarch64-port-dev ] [RFR] [8u] 8u232-b01 Upstream Sync In-Reply-To: <2dd57c4a-91e5-a6f8-771a-5c5d337beb44@redhat.com> References: <1cf9062f-d369-d1f4-0a5b-b6c099bab636@redhat.com> <66da71a4-6035-0e02-616b-c0e7b275bcbe@redhat.com> <2dd57c4a-91e5-a6f8-771a-5c5d337beb44@redhat.com> Message-ID: On 8/2/19 4:12 PM, Andrew John Hughes wrote: > On 01/08/2019 18:19, Aleksey Shipilev wrote: >> The links to changesets below are broken, they are not "b09.changeset", but rather "$project.patch". > > Knew I shouldn't have copied from the joint e-mail. > No, they should be merge.changeset. The others are the webrev patch > files, which there's no point in linking to separately. > > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/corba/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jaxp/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jaxws/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/jdk/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/hotspot/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/langtools/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/nashorn/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b01/root/merge.changeset All right, hotspot merge looks fine. Thumbs up! -- Thanks, -Aleksey From gnu.andrew at redhat.com Fri Aug 2 16:34:57 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 02 Aug 2019 16:34:57 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah: 7 new changesets Message-ID: <201908021634.x72GYvkX024107@aojmv0008.oracle.com> Changeset: bb03d4e1088a Author: andrew Date: 2019-07-16 22:10 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/bb03d4e1088a Added tag jdk8u222-ga for changeset eeeabadc6bf0 ! .hgtags Changeset: df18f5e6b647 Author: andrew Date: 2019-07-17 20:41 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/df18f5e6b647 Added tag jdk8u232-b00 for changeset 8f29b4acc5d2 ! .hgtags Changeset: abf33bbd954c Author: andrew Date: 2019-07-17 21:18 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/abf33bbd954c Merge ! .hgtags Changeset: ef88239d3d16 Author: andrew Date: 2019-07-24 03:18 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/ef88239d3d16 8223219: Backport of JDK-8199552 to OpenJDK 8 leads to duplicate -fstack-protector flags, overriding --with-extra-cflags Summary: Apply -fstack-protector to all archs and remove duplication in JDK build Reviewed-by: sgehwolf ! common/autoconf/flags.m4 ! common/autoconf/generated-configure.sh Changeset: d932feeb203d Author: andrew Date: 2019-07-25 16:23 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/d932feeb203d Added tag jdk8u232-b01 for changeset ef88239d3d16 ! .hgtags Changeset: 84a12886fd4c Author: andrew Date: 2019-07-25 17:40 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/84a12886fd4c Merge jdk8u232-b01 ! .hgtags ! common/autoconf/flags.m4 ! common/autoconf/generated-configure.sh Changeset: 44d0a01671da Author: andrew Date: 2019-07-25 17:54 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/44d0a01671da Added tag aarch64-shenandoah-jdk8u232-b01 for changeset 84a12886fd4c ! .hgtags From gnu.andrew at redhat.com Fri Aug 2 16:37:28 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 02 Aug 2019 16:37:28 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/corba: 6 new changesets Message-ID: <201908021637.x72GbSuH027028@aojmv0008.oracle.com> Changeset: a7b8e960cd8a Author: andrew Date: 2019-07-16 22:10 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/a7b8e960cd8a Added tag jdk8u222-ga for changeset d44170c2cece ! .hgtags Changeset: 1deafc078e4d Author: andrew Date: 2019-07-17 20:41 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/1deafc078e4d Added tag jdk8u232-b00 for changeset 5837b825d94b ! .hgtags Changeset: 2c9e12886322 Author: andrew Date: 2019-07-17 21:18 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/2c9e12886322 Merge ! .hgtags Changeset: 63cfd6362001 Author: andrew Date: 2019-07-25 16:23 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/63cfd6362001 Added tag jdk8u232-b01 for changeset 2c9e12886322 ! .hgtags Changeset: ac410b54cc93 Author: andrew Date: 2019-07-25 17:40 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/ac410b54cc93 Merge jdk8u232-b01 ! .hgtags Changeset: 15958fc88f47 Author: andrew Date: 2019-07-25 17:54 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/15958fc88f47 Added tag aarch64-shenandoah-jdk8u232-b01 for changeset ac410b54cc93 ! .hgtags From gnu.andrew at redhat.com Fri Aug 2 16:37:43 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 02 Aug 2019 16:37:43 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxp: 6 new changesets Message-ID: <201908021637.x72GbhaO027274@aojmv0008.oracle.com> Changeset: b257fe295194 Author: andrew Date: 2019-07-16 22:10 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/b257fe295194 Added tag jdk8u222-ga for changeset 268ffbdb01e1 ! .hgtags Changeset: 2b206ca07d51 Author: andrew Date: 2019-07-17 20:41 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/2b206ca07d51 Added tag jdk8u232-b00 for changeset de624afa6e75 ! .hgtags Changeset: 30e9e09bb155 Author: andrew Date: 2019-07-17 21:18 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/30e9e09bb155 Merge ! .hgtags Changeset: ff1df33b41f4 Author: andrew Date: 2019-07-25 16:23 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/ff1df33b41f4 Added tag jdk8u232-b01 for changeset 30e9e09bb155 ! .hgtags Changeset: d4b1222b3d09 Author: andrew Date: 2019-07-25 17:40 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/d4b1222b3d09 Merge jdk8u232-b01 ! .hgtags Changeset: badd14300357 Author: andrew Date: 2019-07-25 17:54 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/badd14300357 Added tag aarch64-shenandoah-jdk8u232-b01 for changeset d4b1222b3d09 ! .hgtags From gnu.andrew at redhat.com Fri Aug 2 16:39:30 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 02 Aug 2019 16:39:30 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxws: 6 new changesets Message-ID: <201908021639.x72GdUjZ000124@aojmv0008.oracle.com> Changeset: 84332572ca78 Author: andrew Date: 2019-07-16 22:10 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/84332572ca78 Added tag jdk8u222-ga for changeset 3a4dd1917fc5 ! .hgtags Changeset: 07a737dc86ff Author: andrew Date: 2019-07-17 20:41 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/07a737dc86ff Added tag jdk8u232-b00 for changeset bd5323b37905 ! .hgtags Changeset: 44958f6d06d7 Author: andrew Date: 2019-07-17 21:18 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/44958f6d06d7 Merge ! .hgtags Changeset: dc445b545ab7 Author: andrew Date: 2019-07-25 16:23 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/dc445b545ab7 Added tag jdk8u232-b01 for changeset 44958f6d06d7 ! .hgtags Changeset: aaf0d20a847f Author: andrew Date: 2019-07-25 17:40 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/aaf0d20a847f Merge jdk8u232-b01 ! .hgtags Changeset: 501136065fb1 Author: andrew Date: 2019-07-25 17:54 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/501136065fb1 Added tag aarch64-shenandoah-jdk8u232-b01 for changeset aaf0d20a847f ! .hgtags From gnu.andrew at redhat.com Fri Aug 2 16:39:48 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 02 Aug 2019 16:39:48 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/nashorn: 6 new changesets Message-ID: <201908021639.x72Gdm8A000295@aojmv0008.oracle.com> Changeset: 4e54b87c9c6f Author: andrew Date: 2019-07-16 22:10 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/4e54b87c9c6f Added tag jdk8u222-ga for changeset 0a5ba9e191cf ! .hgtags Changeset: 61e8cca16e76 Author: andrew Date: 2019-07-17 20:42 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/61e8cca16e76 Added tag jdk8u232-b00 for changeset 22144dab9c5d ! .hgtags Changeset: 3f4a6f52aac0 Author: andrew Date: 2019-07-17 21:19 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/3f4a6f52aac0 Merge ! .hgtags Changeset: 908754951075 Author: andrew Date: 2019-07-25 16:23 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/908754951075 Added tag jdk8u232-b01 for changeset 3f4a6f52aac0 ! .hgtags Changeset: 1dc991764c0b Author: andrew Date: 2019-07-25 17:40 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/1dc991764c0b Merge jdk8u232-b01 ! .hgtags Changeset: fcf1cb28f567 Author: andrew Date: 2019-07-25 17:54 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/fcf1cb28f567 Added tag aarch64-shenandoah-jdk8u232-b01 for changeset 1dc991764c0b ! .hgtags From gnu.andrew at redhat.com Fri Aug 2 16:40:12 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 02 Aug 2019 16:40:12 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/langtools: 6 new changesets Message-ID: <201908021640.x72GeCUR000720@aojmv0008.oracle.com> Changeset: 74039619a940 Author: andrew Date: 2019-07-16 22:10 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/74039619a940 Added tag jdk8u222-ga for changeset 32df4483e2e3 ! .hgtags Changeset: b0454f56a70e Author: andrew Date: 2019-07-17 20:41 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/b0454f56a70e Added tag jdk8u232-b00 for changeset 2ad39b194cc1 ! .hgtags Changeset: d859443cacf8 Author: andrew Date: 2019-07-17 21:18 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/d859443cacf8 Merge ! .hgtags Changeset: 05e1bf131eba Author: andrew Date: 2019-07-25 16:23 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/05e1bf131eba Added tag jdk8u232-b01 for changeset d859443cacf8 ! .hgtags Changeset: 2d4ca3a4196a Author: andrew Date: 2019-07-25 17:40 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/2d4ca3a4196a Merge jdk8u232-b01 ! .hgtags Changeset: 1f76adced46a Author: andrew Date: 2019-07-25 17:54 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/1f76adced46a Added tag aarch64-shenandoah-jdk8u232-b01 for changeset 2d4ca3a4196a ! .hgtags From gnu.andrew at redhat.com Fri Aug 2 16:40:39 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 02 Aug 2019 16:40:39 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jdk: 35 new changesets Message-ID: <201908021640.x72GeeqM000931@aojmv0008.oracle.com> Changeset: e859d56516da Author: andrew Date: 2019-07-16 22:10 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/e859d56516da Added tag jdk8u222-ga for changeset 2a9bea6e5e03 ! .hgtags Changeset: 0afa589e56f9 Author: sveerabhadra Date: 2018-06-25 14:32 +0530 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/0afa589e56f9 8153732: Windows remote printer changes do not reflect in lookupPrintServices() Reviewed-by: prr, psadhukhan ! src/windows/classes/sun/print/PrintServiceLookupProvider.java ! src/windows/native/sun/windows/WPrinterJob.cpp + test/jdk/java/awt/print/RemotePrinterStatusRefresh/RemotePrinterStatusRefresh.java Changeset: c31d489a4c5d Author: sveerabhadra Date: 2019-02-25 11:02 +0530 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/c31d489a4c5d 8212202: [Windows] Exception if no printers are installed. Reviewed-by: prr ! src/windows/classes/sun/print/PrintServiceLookupProvider.java ! src/windows/native/sun/windows/WPrinterJob.cpp ! test/jdk/java/awt/print/RemotePrinterStatusRefresh/RemotePrinterStatusRefresh.java Changeset: 6be31c5c1807 Author: aivanov Date: 2019-04-09 08:50 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/6be31c5c1807 8221263: [TEST_BUG] RemotePrinterStatusRefresh test is hard to use Reviewed-by: serb, prr ! test/jdk/java/awt/print/RemotePrinterStatusRefresh/RemotePrinterStatusRefresh.java Changeset: e06784459c2c Author: zgu Date: 2019-06-12 13:03 -0400 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/e06784459c2c 8221263: [TEST_BUG] RemotePrinterStatusRefresh test is hard to use Reviewed-by: serb, prr ! test/jdk/java/awt/print/RemotePrinterStatusRefresh/RemotePrinterStatusRefresh.java Changeset: 38badfb0300f Author: aivanov Date: 2019-03-28 14:52 +0000 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/38badfb0300f 8221412: lookupPrintServices() does not always update the list of Windows remote printers Reviewed-by: prr, serb ! src/windows/classes/sun/print/PrintServiceLookupProvider.java ! src/windows/native/sun/windows/WPrinterJob.cpp Changeset: 9941714bd1bc Author: rriggs Date: 2014-02-05 10:59 -0500 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/9941714bd1bc 8030993: Check jdk/src/share/native/common/jni_util.c for JNI pending exceptions Summary: Check for pending exceptions Reviewed-by: alanb, chegar ! src/share/native/common/jni_util.c Changeset: 2df1d6f6fdf6 Author: rriggs Date: 2018-06-12 13:07 -0400 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/2df1d6f6fdf6 8197930: JNI exception pending in initializeEncoding of jni_util.c Reviewed-by: mchung, stuefe ! src/share/native/common/jni_util.c Changeset: cfd0218da0af Author: igerasim Date: 2019-03-21 12:28 -0700 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/cfd0218da0af 8170494: JNI exception pending in PlainDatagramSocketImpl.c Reviewed-by: clanger, vtewari ! src/solaris/native/java/net/PlainDatagramSocketImpl.c Changeset: 87a71ca14dff Author: andrew Date: 2018-06-25 02:52 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/87a71ca14dff 8205587: Implicit function declaration in jni_util.c Reviewed-by: omajid ! src/share/native/common/jni_util.c Changeset: a2c492c8b883 Author: andrew Date: 2019-06-17 16:46 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/a2c492c8b883 8182999: SunEC throws ProviderException on invalid curves Reviewed-by: vinnie ! make/mapfiles/libsunec/mapfile-vers ! src/share/classes/sun/security/ec/ECKeyPairGenerator.java ! src/share/classes/sun/security/util/ECUtil.java ! src/share/native/sun/security/ec/ECC_JNI.cpp + test/sun/security/ec/InvalidCurve.java Changeset: 6b678425fbbb Author: andrew Date: 2019-06-17 17:19 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/6b678425fbbb Merge Changeset: 93883f2d74eb Author: prappo Date: 2016-10-21 12:31 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/93883f2d74eb 8168417: Pending exceptions in java.base/windows/native/libnio Reviewed-by: chegar, alanb ! src/windows/native/sun/nio/ch/FileDispatcherImpl.c Changeset: 3de016c65a06 Author: igerasim Date: 2019-01-02 15:33 -0800 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/3de016c65a06 6996807: FieldReflectorKey hash code computation can be improved Reviewed-by: rriggs ! src/share/classes/java/io/ObjectStreamClass.java Changeset: 180cd8fe6c51 Author: sgehwolf Date: 2019-06-19 19:05 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/180cd8fe6c51 8226392: Launcher should not enable legacy stdio streams on GNU/Linux (glibc) Summary: Ensure _IO_stdin_used gets exported via linker version script Reviewed-by: andrew, fweimer ! make/mapfiles/launchers/mapfile-x86 Changeset: f879433510b7 Author: sgehwolf Date: 2019-06-28 10:31 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f879433510b7 8226928: [TESTBUG] test/java/net/NetworkInterface/IPv4Only.java fails intermittently on AIX Summary: Set the property on the command line as the JDK 11 version Reviewed-by: clanger, andrew, chegar ! test/java/net/NetworkInterface/IPv4Only.java Changeset: bc278b0ebfad Author: sgehwolf Date: 2019-06-27 10:52 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/bc278b0ebfad 8226870: OpenJDK 8u JRE contains clhsdb and hsdb launchers Summary: Add clhsdb and hsdb to NOT_JRE_BIN_FILES exclude list Reviewed-by: shade ! make/Images.gmk Changeset: 31d3c2937dcb Author: shade Date: 2019-07-05 16:22 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/31d3c2937dcb 8227018: CompletableFuture should not call Runtime.availableProcessors on fast path Reviewed-by: dl, martin ! src/share/classes/java/util/concurrent/CompletableFuture.java Changeset: 6e1a1f54e7ef Author: bchristi Date: 2016-10-07 12:01 -0700 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/6e1a1f54e7ef 8151486: Class.forName causes memory leak Summary: Remove ClassLoader.domains Reviewed-by: coleenp, dholmes, mchung, naoto ! src/share/classes/java/lang/ClassLoader.java + test/java/lang/ClassLoader/forNameLeak/ClassForName.java + test/java/lang/ClassLoader/forNameLeak/ClassForNameLeak.java + test/java/lang/ClassLoader/forNameLeak/test.policy Changeset: 5cf8e52254c2 Author: andrew Date: 2019-07-01 20:26 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/5cf8e52254c2 8218781: Localized names for Japanese era Reiwa in COMPAT provider Reviewed-by: naoto, aph, phh ! src/share/classes/sun/text/resources/ar/FormatData_ar.java ! src/share/classes/sun/text/resources/ar/JavaTimeSupplementary_ar.java ! src/share/classes/sun/text/resources/hi/JavaTimeSupplementary_hi_IN.java ! src/share/classes/sun/text/resources/ko/FormatData_ko.java ! src/share/classes/sun/text/resources/ko/JavaTimeSupplementary_ko.java ! src/share/classes/sun/text/resources/ru/JavaTimeSupplementary_ru.java ! src/share/classes/sun/text/resources/sr/JavaTimeSupplementary_sr.java ! src/share/classes/sun/text/resources/th/FormatData_th.java ! src/share/classes/sun/text/resources/th/JavaTimeSupplementary_th.java ! src/share/classes/sun/text/resources/zh/FormatData_zh.java ! src/share/classes/sun/text/resources/zh/JavaTimeSupplementary_zh.java ! src/share/classes/sun/text/resources/zh/JavaTimeSupplementary_zh_TW.java + test/java/util/Calendar/JapanEraNameCompatTest.java Changeset: 2361895a718a Author: andrew Date: 2019-07-06 19:18 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/2361895a718a Merge - src/share/classes/sun/util/locale/LocaleEquivalentMaps.java - test/java/util/Locale/tools/EquivMapsGenerator.java - test/java/util/Locale/tools/language-subtag-registry.txt ! test/jdk/java/awt/print/RemotePrinterStatusRefresh/RemotePrinterStatusRefresh.java Changeset: b3e86d31e517 Author: darcy Date: 2015-03-19 13:18 -0700 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/b3e86d31e517 8075544: Add tiered testing definitions to the jdk repo Reviewed-by: alanb ! test/TEST.groups Changeset: 16350fc6cc1c Author: darcy Date: 2015-03-20 10:00 -0700 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/16350fc6cc1c 8075573: Add jdk_other and jdk_svc to jdk tier 2 test definition Reviewed-by: mchung ! test/TEST.groups Changeset: f83fd6026556 Author: okutsu Date: 2016-08-30 14:16 +0900 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f83fd6026556 8157792: After Integrating tzdata2016d the test/sun/util/calendar/zi/TestZoneInfo310.java fails for "Asia/Oral" and "Asia/Qyzylorda" Timezones Reviewed-by: peytoia ! test/sun/util/calendar/zi/TestZoneInfo310.java ! test/sun/util/calendar/zi/Zoneinfo.java Changeset: 2eb10dde7a68 Author: rpatil Date: 2019-07-10 18:34 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/2eb10dde7a68 8224560: (tz) Upgrade time-zone data to tzdata2019a 8215982: (tz) Upgrade time-zone data to tzdata2018i 8225580: tzdata2018i integration causes test failures on jdk-13 Reviewed-by: andrew, naoto ! make/data/tzdata/VERSION ! make/data/tzdata/africa ! make/data/tzdata/asia ! make/data/tzdata/australasia ! make/data/tzdata/backward ! make/data/tzdata/etcetera ! make/data/tzdata/europe ! make/data/tzdata/iso3166.tab ! make/data/tzdata/leapseconds ! make/data/tzdata/northamerica ! make/data/tzdata/zone.tab ! src/share/classes/sun/util/calendar/ZoneInfoFile.java ! src/share/classes/sun/util/resources/TimeZoneNames.java ! src/share/classes/sun/util/resources/de/TimeZoneNames_de.java ! src/share/classes/sun/util/resources/es/TimeZoneNames_es.java ! src/share/classes/sun/util/resources/fr/TimeZoneNames_fr.java ! src/share/classes/sun/util/resources/it/TimeZoneNames_it.java ! src/share/classes/sun/util/resources/ja/TimeZoneNames_ja.java ! src/share/classes/sun/util/resources/ko/TimeZoneNames_ko.java ! src/share/classes/sun/util/resources/pt/TimeZoneNames_pt_BR.java ! src/share/classes/sun/util/resources/sv/TimeZoneNames_sv.java ! src/share/classes/sun/util/resources/zh/TimeZoneNames_zh_CN.java ! src/share/classes/sun/util/resources/zh/TimeZoneNames_zh_TW.java ! test/sun/util/calendar/zi/TestZoneInfo310.java ! test/sun/util/calendar/zi/tzdata/VERSION ! test/sun/util/calendar/zi/tzdata/africa ! test/sun/util/calendar/zi/tzdata/asia ! test/sun/util/calendar/zi/tzdata/australasia ! test/sun/util/calendar/zi/tzdata/backward ! test/sun/util/calendar/zi/tzdata/etcetera ! test/sun/util/calendar/zi/tzdata/europe ! test/sun/util/calendar/zi/tzdata/iso3166.tab ! test/sun/util/calendar/zi/tzdata/leapseconds ! test/sun/util/calendar/zi/tzdata/northamerica ! test/sun/util/calendar/zi/tzdata/zone.tab Changeset: 6434138b69af Author: andrew Date: 2019-07-17 20:41 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/6434138b69af Added tag jdk8u232-b00 for changeset 887c8314411d ! .hgtags Changeset: 2783fe5be9a1 Author: andrew Date: 2019-07-17 21:18 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/2783fe5be9a1 Merge ! .hgtags Changeset: 12d3c4d2cf37 Author: itakiguchi Date: 2018-12-05 12:59 -0800 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/12d3c4d2cf37 8214002: Cannot use italic font style if the font has embedded bitmap Reviewed-by: prr ! src/share/native/sun/font/freetypeScaler.c + test/java/awt/font/TextLayout/FontGlyphCompare.java Changeset: d754c9f8ba4a Author: mbalao Date: 2019-03-01 12:21 -0300 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/d754c9f8ba4a 8218854: FontMetrics.getMaxAdvance may be less than the maximum FontMetrics.charWidth Summary: Consider algorithmic bold in FontMetrics.getMaxAdvance value and update obliqueness. Reviewed-by: prr, serb ! src/share/native/sun/font/freetypeScaler.c + test/java/awt/FontMetrics/MaxAdvanceIsMax.java Changeset: 010d44fe3c85 Author: prr Date: 2019-03-21 21:37 -0700 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/010d44fe3c85 8221304: Problem list java/awt/FontMetrics/MaxAdvanceIsMax.java Reviewed-by: serb ! test/ProblemList.txt Changeset: e357f543924b Author: andrew Date: 2019-07-24 04:14 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/e357f543924b 6946830: javax.crypto.Cipher.doFinal behavior differs depending on platform Summary: Updated SunPKCS11 provider with SunJCE provider behavior Reviewed-by: xuelei ! src/share/classes/sun/security/pkcs11/P11Cipher.java + test/javax/crypto/Cipher/EmptyFinalBuffer.java Changeset: 54dbc9006d37 Author: mbalao Date: 2018-11-29 13:36 -0300 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/54dbc9006d37 6913047: Long term memory leak when using PKCS11 and JCE exceeds 32 bit process address space Summary: Extract cryptographic keys within NSS PKCS11 software tokens for memory management purposes. Reviewed-by: valeriep ! make/mapfiles/libj2pkcs11/mapfile-vers ! src/share/classes/sun/security/pkcs11/P11Cipher.java ! src/share/classes/sun/security/pkcs11/P11DHKeyFactory.java ! src/share/classes/sun/security/pkcs11/P11DSAKeyFactory.java ! src/share/classes/sun/security/pkcs11/P11Digest.java ! src/share/classes/sun/security/pkcs11/P11ECDHKeyAgreement.java ! src/share/classes/sun/security/pkcs11/P11ECKeyFactory.java ! src/share/classes/sun/security/pkcs11/P11Key.java ! src/share/classes/sun/security/pkcs11/P11KeyAgreement.java ! src/share/classes/sun/security/pkcs11/P11KeyStore.java ! src/share/classes/sun/security/pkcs11/P11Mac.java ! src/share/classes/sun/security/pkcs11/P11RSACipher.java ! src/share/classes/sun/security/pkcs11/P11RSAKeyFactory.java ! src/share/classes/sun/security/pkcs11/P11SecretKeyFactory.java ! src/share/classes/sun/security/pkcs11/P11Signature.java ! src/share/classes/sun/security/pkcs11/P11TlsKeyMaterialGenerator.java ! src/share/classes/sun/security/pkcs11/P11TlsMasterSecretGenerator.java ! src/share/classes/sun/security/pkcs11/P11TlsPrfGenerator.java ! src/share/classes/sun/security/pkcs11/wrapper/PKCS11.java ! src/share/lib/security/java.policy ! src/share/native/sun/security/pkcs11/wrapper/p11_keymgmt.c ! src/share/native/sun/security/pkcs11/wrapper/pkcs11t.h ! src/share/native/sun/security/pkcs11/wrapper/pkcs11wrapper.h Changeset: 23c77bdc49fc Author: andrew Date: 2019-07-25 16:23 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/23c77bdc49fc Added tag jdk8u232-b01 for changeset 54dbc9006d37 ! .hgtags Changeset: b7bdc478e2a6 Author: andrew Date: 2019-07-25 17:40 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/b7bdc478e2a6 Merge jdk8u232-b01 ! .hgtags ! make/Images.gmk ! src/share/classes/java/io/ObjectStreamClass.java ! src/share/classes/java/lang/ClassLoader.java ! src/share/classes/sun/security/pkcs11/P11DHKeyFactory.java ! src/share/classes/sun/security/pkcs11/P11DSAKeyFactory.java ! src/share/classes/sun/security/pkcs11/P11ECKeyFactory.java ! src/share/classes/sun/security/pkcs11/P11Key.java ! src/share/classes/sun/security/pkcs11/P11RSAKeyFactory.java ! src/share/classes/sun/security/pkcs11/wrapper/PKCS11.java ! src/share/native/sun/font/freetypeScaler.c ! src/solaris/native/java/net/PlainDatagramSocketImpl.c ! test/ProblemList.txt ! test/TEST.groups Changeset: 5b19b7d6ebc1 Author: andrew Date: 2019-07-25 17:54 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/5b19b7d6ebc1 Added tag aarch64-shenandoah-jdk8u232-b01 for changeset b7bdc478e2a6 ! .hgtags From gnu.andrew at redhat.com Fri Aug 2 16:46:43 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 02 Aug 2019 16:46:43 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 19 new changesets Message-ID: <201908021646.x72GkhZr002881@aojmv0008.oracle.com> Changeset: da3a1f729b2b Author: andrew Date: 2019-07-16 22:10 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/da3a1f729b2b Added tag jdk8u222-ga for changeset adfdce09acc3 ! .hgtags Changeset: 5d306df084eb Author: thartmann Date: 2019-04-30 14:49 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/5d306df084eb 8219807: C2 crash in IfNode::up_one_dom(Node*, bool) Summary: Guard against regions degraded to copies. Reviewed-by: kvn ! src/share/vm/opto/ifnode.cpp + test/compiler/c2/TestIfWithDeadRegion.java Changeset: 0f2fe7d37d8c Author: andrew Date: 2019-06-17 16:41 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/0f2fe7d37d8c 8202353: os::readdir should use readdir instead of readdir_r Summary: Summary: os::readdir uses POSIX readdir, drop buffer arg, fix JFR uses. Reviewed-by: coleenp, tschatzl, bsrbnd, shade, phh ! src/os/aix/vm/os_aix.cpp ! src/os/aix/vm/os_aix.inline.hpp ! src/os/aix/vm/perfMemory_aix.cpp ! src/os/bsd/vm/os_bsd.cpp ! src/os/bsd/vm/os_bsd.inline.hpp ! src/os/bsd/vm/perfMemory_bsd.cpp ! src/os/linux/vm/os_linux.cpp ! src/os/linux/vm/os_linux.inline.hpp ! src/os/linux/vm/perfMemory_linux.cpp ! src/os/posix/vm/os_posix.cpp ! src/os/solaris/vm/os_solaris.cpp ! src/os/solaris/vm/os_solaris.inline.hpp ! src/os/solaris/vm/perfMemory_solaris.cpp ! src/os/windows/vm/os_windows.cpp ! src/os/windows/vm/os_windows.inline.hpp ! src/os/windows/vm/perfMemory_windows.cpp ! src/share/vm/runtime/arguments.cpp ! src/share/vm/runtime/os.hpp Changeset: d7e1e002b496 Author: andrew Date: 2019-06-17 17:20 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/d7e1e002b496 Merge Changeset: c4567d28f31f Author: ogatak Date: 2019-06-18 09:33 -0400 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/c4567d28f31f 8185979: PPC64: Implement SHA2 intrinsic Reviewed-by: mdoerr, goetz Contributed-by: Bruno Rosa , Gustavo Serra Scalet , Igor Nunes , Martin Doerr ! src/cpu/ppc/vm/assembler_ppc.hpp ! src/cpu/ppc/vm/assembler_ppc.inline.hpp ! src/cpu/ppc/vm/macroAssembler_ppc.hpp + src/cpu/ppc/vm/macroAssembler_ppc_sha.cpp ! src/cpu/ppc/vm/stubGenerator_ppc.cpp ! src/cpu/ppc/vm/stubRoutines_ppc_64.hpp ! src/cpu/ppc/vm/vm_version_ppc.cpp ! src/cpu/ppc/vm/vm_version_ppc.hpp ! src/share/vm/opto/library_call.cpp ! src/share/vm/opto/runtime.cpp ! test/compiler/intrinsics/sha/cli/testcases/GenericTestCaseForOtherCPU.java ! test/compiler/testlibrary/sha/predicate/IntrinsicPredicates.java Changeset: e49125a0c77c Author: ysuenaga Date: 2019-06-19 09:42 +0900 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/e49125a0c77c 8225636: SA can't handle prelinked libraries Reviewed-by: sspitsyn, cjplummer ! agent/src/os/linux/ps_core.c Changeset: e0e66aba375a Author: thartmann Date: 2019-02-19 08:58 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/e0e66aba375a 8218721: C1's CEE optimization produces safepoint poll with invalid debug information Summary: Bail out of CEE if one of the gotos is a safepoint but the if is not. Reviewed-by: vlivanov, mdoerr ! src/share/vm/c1/c1_Optimizer.cpp + test/compiler/c1/TestGotoIf.jasm + test/compiler/c1/TestGotoIfMain.java Changeset: adaa0f3c6c59 Author: andrew Date: 2019-07-06 19:18 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/adaa0f3c6c59 Merge Changeset: 23845b8c4b4b Author: sgehwolf Date: 2018-09-21 16:58 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/23845b8c4b4b 8210761: libjsig is being compiled without optimization Reviewed-by: clanger, andrew ! make/aix/makefiles/jsig.make ! make/bsd/makefiles/jsig.make ! make/linux/makefiles/jsig.make ! make/solaris/makefiles/jsig.make Changeset: 45db069363be Author: andrew Date: 2019-07-17 20:41 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/45db069363be Added tag jdk8u232-b00 for changeset 1ec20e8a3d8a ! .hgtags Changeset: 4fcf5ea9b9de Author: andrew Date: 2019-07-17 21:18 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/4fcf5ea9b9de Merge ! .hgtags Changeset: 67dddb025b7b Author: gziemski Date: 2016-05-24 12:42 -0500 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/67dddb025b7b 8152856: Xcode 7.3 -Wshift-negative-value compile failure on Mac OS X Summary: Implement _lh_array_tag_type_value as const, not enum. Reviewed-by: vlivanov, minqi ! src/share/vm/oops/klass.hpp ! src/share/vm/opto/library_call.cpp Changeset: 78c11f573795 Author: sgehwolf Date: 2017-08-07 12:19 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/78c11f573795 8185900: hotspot build failed with gcc version Red Hat 4.4.7-3 Summary: Cast to void* within DTRACE_CLASS* macros. Reviewed-by: coleenp, shade ! src/share/vm/oops/instanceKlass.cpp ! src/share/vm/services/classLoadingService.cpp Changeset: b893d11d147f Author: shade Date: 2019-07-24 21:43 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/b893d11d147f 8228405: Incorrect format strings in PhaseIdealLoop::rc_predicate Reviewed-by: andrew, phh ! src/share/vm/opto/loopPredicate.cpp Changeset: afa42cf8d060 Author: thartmann Date: 2015-03-23 10:15 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/afa42cf8d060 8075136: Unnecessary sign extension for byte array access Summary: Added C2 matching rules to remove unnecessary sign extension for byte array access. Reviewed-by: roland, kvn, aph, adinn ! src/cpu/x86/vm/x86_64.ad Changeset: bfff0a0ccb0e Author: andrew Date: 2019-07-25 16:23 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/bfff0a0ccb0e Added tag jdk8u232-b01 for changeset afa42cf8d060 ! .hgtags Changeset: eaa9fc3d8b61 Author: andrew Date: 2019-07-25 17:40 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/eaa9fc3d8b61 Merge jdk8u232-b01 ! .hgtags ! agent/src/os/linux/ps_core.c ! make/bsd/makefiles/jsig.make ! src/cpu/x86/vm/x86_64.ad ! src/os/bsd/vm/os_bsd.cpp ! src/os/linux/vm/os_linux.cpp ! src/os/linux/vm/os_linux.inline.hpp ! src/share/vm/c1/c1_Optimizer.cpp ! src/share/vm/oops/instanceKlass.cpp ! src/share/vm/oops/klass.hpp ! src/share/vm/opto/ifnode.cpp ! src/share/vm/opto/library_call.cpp ! src/share/vm/opto/loopPredicate.cpp ! src/share/vm/opto/runtime.cpp ! src/share/vm/runtime/arguments.cpp ! src/share/vm/runtime/os.hpp ! src/share/vm/services/classLoadingService.cpp ! test/compiler/intrinsics/sha/cli/testcases/GenericTestCaseForOtherCPU.java ! test/compiler/testlibrary/sha/predicate/IntrinsicPredicates.java Changeset: 7c087d2cfdb7 Author: andrew Date: 2019-07-25 17:54 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/7c087d2cfdb7 Added tag aarch64-shenandoah-jdk8u232-b01 for changeset eaa9fc3d8b61 ! .hgtags Changeset: adc4d59a4073 Author: andrew Date: 2019-08-02 17:46 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/adc4d59a4073 Merge ! src/share/vm/oops/instanceKlass.cpp From ci_notify at linaro.org Sat Aug 3 00:18:28 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sat, 3 Aug 2019 00:18:28 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <41151408.4424.1564791508466.JavaMail.jenkins@6e40b75d9e9e> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2019/214/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/01 pass: 5,650; fail: 4 Build 1: aarch64/2019/jul/03 pass: 5,654; fail: 2 Build 2: aarch64/2019/jul/05 pass: 5,653; fail: 3 Build 3: aarch64/2019/jul/09 pass: 5,695; fail: 3 Build 4: aarch64/2019/jul/11 pass: 5,696; fail: 3 Build 5: aarch64/2019/jul/12 pass: 5,695; fail: 5 Build 6: aarch64/2019/jul/15 pass: 5,699; fail: 1 Build 7: aarch64/2019/jul/17 pass: 5,700; fail: 1; error: 1 Build 8: aarch64/2019/jul/19 pass: 5,699; fail: 3; error: 1 Build 9: aarch64/2019/jul/22 pass: 5,705; fail: 2 Build 10: aarch64/2019/jul/24 pass: 5,706; fail: 1 Build 11: aarch64/2019/jul/26 pass: 5,707; fail: 2 Build 12: aarch64/2019/jul/29 pass: 5,705; fail: 4 Build 13: aarch64/2019/jul/31 pass: 5,711; fail: 1 Build 14: aarch64/2019/aug/02 pass: 5,711; fail: 2 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/01 pass: 8,601; fail: 536; error: 17 Build 1: aarch64/2019/jul/03 pass: 8,609; fail: 525; error: 21 Build 2: aarch64/2019/jul/05 pass: 8,612; fail: 515; error: 28 Build 3: aarch64/2019/jul/09 pass: 8,604; fail: 532; error: 19 Build 4: aarch64/2019/jul/11 pass: 8,598; fail: 529; error: 31 Build 5: aarch64/2019/jul/12 pass: 8,601; fail: 528; error: 29 Build 6: aarch64/2019/jul/15 pass: 8,602; fail: 533; error: 25 Build 7: aarch64/2019/jul/17 pass: 8,614; fail: 522; error: 24 Build 8: aarch64/2019/jul/19 pass: 8,611; fail: 526; error: 26 Build 9: aarch64/2019/jul/22 pass: 8,628; fail: 511; error: 24 Build 10: aarch64/2019/jul/24 pass: 8,617; fail: 538; error: 26 Build 11: aarch64/2019/jul/26 pass: 8,649; fail: 518; error: 17 Build 12: aarch64/2019/jul/29 pass: 8,640; fail: 520; error: 26 Build 13: aarch64/2019/jul/31 pass: 8,640; fail: 526; error: 24 Build 14: aarch64/2019/aug/02 pass: 8,637; fail: 524; error: 29 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/01 pass: 3,964 Build 1: aarch64/2019/jul/03 pass: 3,964 Build 2: aarch64/2019/jul/05 pass: 3,965 Build 3: aarch64/2019/jul/09 pass: 3,967 Build 4: aarch64/2019/jul/11 pass: 3,968 Build 5: aarch64/2019/jul/12 pass: 3,968 Build 6: aarch64/2019/jul/15 pass: 3,968 Build 7: aarch64/2019/jul/17 pass: 3,968 Build 8: aarch64/2019/jul/19 pass: 3,969 Build 9: aarch64/2019/jul/22 pass: 3,969 Build 10: aarch64/2019/jul/24 pass: 3,970 Build 11: aarch64/2019/jul/26 pass: 3,970 Build 12: aarch64/2019/jul/29 pass: 3,970 Build 13: aarch64/2019/jul/31 pass: 3,970 Build 14: aarch64/2019/aug/02 pass: 3,970 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.63x Relative performance: Server critical-jOPS (nc): 8.99x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 207.57 Server 207.57 / Server 2014-04-01 (71.00): 2.92x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-01-01 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/365/results/ 2019-07-01 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/182/results/ 2019-07-04 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/184/results/ 2019-07-05 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/186/results/ 2019-07-10 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/190/results/ 2019-07-12 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/192/results/ 2019-07-15 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/196/results/ 2019-07-17 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/198/results/ 2019-07-20 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/200/results/ 2019-07-22 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/203/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/205/results/ 2019-07-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/207/results/ 2019-07-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/210/results/ 2019-08-01 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/212/results/ 2019-08-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/214/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From ci_notify at linaro.org Sun Aug 4 19:34:50 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sun, 4 Aug 2019 19:34:50 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 13 on AArch64 Message-ID: <480175920.4714.1564947290836.JavaMail.jenkins@6e40b75d9e9e> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk13/openjdk-jtreg-nightly-tests/summary/2019/215/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/22 pass: 5,645; fail: 3 Build 1: aarch64/2019/jun/25 pass: 5,644; fail: 2; error: 1 Build 2: aarch64/2019/jun/27 pass: 5,645; fail: 2 Build 3: aarch64/2019/jun/29 pass: 5,644; fail: 3 Build 4: aarch64/2019/jul/02 pass: 5,645; fail: 2 Build 5: aarch64/2019/jul/04 pass: 5,644; fail: 2; error: 1 Build 6: aarch64/2019/jul/09 pass: 5,643; fail: 4 Build 7: aarch64/2019/jul/16 pass: 5,646; fail: 1 Build 8: aarch64/2019/jul/18 pass: 5,644; fail: 2; error: 1 Build 9: aarch64/2019/jul/20 pass: 5,645; fail: 1; error: 1 Build 10: aarch64/2019/jul/23 pass: 5,644; fail: 3 Build 11: aarch64/2019/jul/25 pass: 5,644; fail: 3 Build 12: aarch64/2019/jul/30 pass: 5,645; fail: 2 Build 13: aarch64/2019/aug/01 pass: 5,646; fail: 1 Build 14: aarch64/2019/aug/03 pass: 5,646; fail: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/22 pass: 8,599; fail: 523; error: 24 Build 1: aarch64/2019/jun/25 pass: 8,603; fail: 525; error: 18 Build 2: aarch64/2019/jun/27 pass: 8,609; fail: 512; error: 26 Build 3: aarch64/2019/jun/29 pass: 8,601; fail: 520; error: 29 Build 4: aarch64/2019/jul/02 pass: 8,604; fail: 521; error: 25 Build 5: aarch64/2019/jul/04 pass: 8,601; fail: 523; error: 26 Build 6: aarch64/2019/jul/09 pass: 8,606; fail: 515; error: 29 Build 7: aarch64/2019/jul/16 pass: 8,593; fail: 531; error: 30 Build 8: aarch64/2019/jul/18 pass: 8,618; fail: 527; error: 26 Build 9: aarch64/2019/jul/20 pass: 8,619; fail: 519; error: 33 Build 10: aarch64/2019/jul/23 pass: 8,616; fail: 525; error: 30 Build 11: aarch64/2019/jul/25 pass: 8,620; fail: 528; error: 23 Build 12: aarch64/2019/jul/30 pass: 8,610; fail: 529; error: 32 Build 13: aarch64/2019/aug/01 pass: 8,620; fail: 527; error: 24 Build 14: aarch64/2019/aug/03 pass: 8,596; fail: 552; error: 23 5 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/22 pass: 3,962 Build 1: aarch64/2019/jun/25 pass: 3,962 Build 2: aarch64/2019/jun/27 pass: 3,962 Build 3: aarch64/2019/jun/29 pass: 3,962 Build 4: aarch64/2019/jul/02 pass: 3,962 Build 5: aarch64/2019/jul/04 pass: 3,962 Build 6: aarch64/2019/jul/09 pass: 3,962 Build 7: aarch64/2019/jul/16 pass: 3,963 Build 8: aarch64/2019/jul/18 pass: 3,964 Build 9: aarch64/2019/jul/20 pass: 3,964 Build 10: aarch64/2019/jul/23 pass: 3,964 Build 11: aarch64/2019/jul/25 pass: 3,964 Build 12: aarch64/2019/jul/30 pass: 3,964 Build 13: aarch64/2019/aug/01 pass: 3,964 Build 14: aarch64/2019/aug/03 pass: 3,964 Previous results can be found here: http://openjdk.linaro.org/jdk13/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.63x Relative performance: Server critical-jOPS (nc): 9.32x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk13/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 210.67 Server 210.67 / Server 2014-04-01 (71.00): 2.97x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk13/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-06-23 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/173/results/ 2019-06-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/176/results/ 2019-06-28 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/178/results/ 2019-06-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/180/results/ 2019-07-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/183/results/ 2019-07-04 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/185/results/ 2019-07-10 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/190/results/ 2019-07-16 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/197/results/ 2019-07-19 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/199/results/ 2019-07-21 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/201/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/204/results/ 2019-07-26 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/211/results/ 2019-08-02 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/213/results/ 2019-08-04 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/215/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/ From ci_notify at linaro.org Sun Aug 4 19:39:54 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sun, 4 Aug 2019 19:39:54 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 11u on AArch64 Message-ID: <418847960.4716.1564947594751.JavaMail.jenkins@6e40b75d9e9e> 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/jdk11u/openjdk-jtreg-nightly-tests/summary/2019/215/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/07 pass: 5,719; fail: 9; not run: 11,618 Build 1: aarch64/2019/mar/12 pass: 5,719; fail: 9; not run: 11,618 Build 2: aarch64/2019/mar/16 pass: 5,721; fail: 8; not run: 11,618 Build 3: aarch64/2019/mar/19 pass: 5,721; fail: 9; not run: 11,618 Build 4: aarch64/2019/mar/28 pass: 5,722; fail: 8; not run: 11,618 Build 5: aarch64/2019/apr/02 pass: 5,723; fail: 8; not run: 11,618 Build 6: aarch64/2019/apr/04 pass: 5,722; fail: 9; not run: 11,618 Build 7: aarch64/2019/apr/18 pass: 5,723; fail: 8; not run: 11,618 Build 8: aarch64/2019/may/16 pass: 5,734; fail: 5; not run: 11,623 Build 9: aarch64/2019/may/25 pass: 5,735; fail: 5; not run: 11,623 Build 10: aarch64/2019/jun/05 pass: 5,737; fail: 5; not run: 11,623 Build 11: aarch64/2019/jun/15 pass: 5,737; fail: 5; not run: 11,623 Build 12: aarch64/2019/jun/27 pass: 5,737; fail: 5 Build 13: aarch64/2019/jul/02 pass: 5,737; fail: 5 Build 14: aarch64/2019/aug/03 pass: 5,746; fail: 4 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/07 pass: 8,388; fail: 502; error: 26 Build 1: aarch64/2019/mar/12 pass: 8,370; fail: 520; error: 26 Build 2: aarch64/2019/mar/16 pass: 8,397; fail: 497; error: 22 Build 3: aarch64/2019/mar/19 pass: 8,365; fail: 527; error: 24 Build 4: aarch64/2019/mar/28 pass: 8,374; fail: 521; error: 21 Build 5: aarch64/2019/apr/02 pass: 8,354; fail: 536; error: 26 Build 6: aarch64/2019/apr/04 pass: 8,382; fail: 510; error: 24 Build 7: aarch64/2019/apr/18 pass: 8,398; fail: 501; error: 19 Build 8: aarch64/2019/may/16 pass: 8,397; fail: 514; error: 22 Build 9: aarch64/2019/may/25 pass: 8,403; fail: 511; error: 21 Build 10: aarch64/2019/jun/05 pass: 8,427; fail: 489; error: 19 Build 11: aarch64/2019/jun/15 pass: 8,409; fail: 506; error: 20 Build 12: aarch64/2019/jun/27 pass: 8,401; fail: 512; error: 22 Build 13: aarch64/2019/jul/02 pass: 8,407; fail: 498; error: 31 Build 14: aarch64/2019/aug/03 pass: 8,429; fail: 509; error: 18 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/07 pass: 3,904 Build 1: aarch64/2019/mar/12 pass: 3,904 Build 2: aarch64/2019/mar/16 pass: 3,904 Build 3: aarch64/2019/mar/19 pass: 3,904 Build 4: aarch64/2019/mar/28 pass: 3,904 Build 5: aarch64/2019/apr/02 pass: 3,904 Build 6: aarch64/2019/apr/04 pass: 3,904 Build 7: aarch64/2019/apr/18 pass: 3,904 Build 8: aarch64/2019/may/16 pass: 3,908 Build 9: aarch64/2019/may/25 pass: 3,908 Build 10: aarch64/2019/jun/05 pass: 3,908 Build 11: aarch64/2019/jun/15 pass: 3,908 Build 12: aarch64/2019/jun/27 pass: 3,908 Build 13: aarch64/2019/jul/02 pass: 3,908 Build 14: aarch64/2019/aug/03 pass: 3,908 Previous results can be found here: http://openjdk.linaro.org/jdk11u/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.46x Relative performance: Server critical-jOPS (nc): 8.16x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk11u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 201.64 Server 201.64 / Server 2014-04-01 (71.00): 2.84x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk11u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-03-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/066/results/ 2019-03-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/071/results/ 2019-03-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/075/results/ 2019-03-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/078/results/ 2019-03-29 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/087/results/ 2019-04-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/092/results/ 2019-04-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/094/results/ 2019-04-19 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/108/results/ 2019-05-17 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/136/results/ 2019-05-26 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/145/results/ 2019-06-05 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/156/results/ 2019-06-16 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/166/results/ 2019-06-28 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/178/results/ 2019-07-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/183/results/ 2019-08-04 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/215/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/ From ci_notify at linaro.org Mon Aug 5 03:36:03 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Mon, 5 Aug 2019 03:36:03 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <1655448833.4786.1564976163710.JavaMail.jenkins@6e40b75d9e9e> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/summary/2019/216/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/feb/26 pass: 799; fail: 9; error: 3 Build 1: aarch64/2019/feb/28 pass: 803; fail: 9; error: 2 Build 2: aarch64/2019/mar/26 pass: 799; fail: 13; error: 2 Build 3: aarch64/2019/apr/09 pass: 807; fail: 9; error: 2 Build 4: aarch64/2019/apr/18 pass: 815; fail: 10 Build 5: aarch64/2019/apr/30 pass: 797; fail: 23; error: 9 Build 6: aarch64/2019/may/02 pass: 814; fail: 14; error: 2 Build 7: aarch64/2019/jun/15 pass: 815; fail: 22; error: 1 Build 8: aarch64/2019/jun/20 pass: 820; fail: 16; error: 2 Build 9: aarch64/2019/jun/29 pass: 807; fail: 25; error: 6 Build 10: aarch64/2019/jul/19 pass: 814; fail: 20; error: 4 Build 11: aarch64/2019/jul/25 pass: 802; fail: 25; error: 11 Build 12: aarch64/2019/jul/30 pass: 787; fail: 40; error: 11 Build 13: aarch64/2019/aug/01 pass: 800; fail: 26; error: 12 Build 14: aarch64/2019/aug/04 pass: 808; fail: 30; error: 2 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/feb/26 pass: 5,756; fail: 259; error: 27 Build 1: aarch64/2019/feb/28 pass: 5,749; fail: 268; error: 26 Build 2: aarch64/2019/mar/26 pass: 5,768; fail: 246; error: 29 Build 3: aarch64/2019/apr/09 pass: 5,763; fail: 267; error: 24 Build 4: aarch64/2019/apr/18 pass: 5,784; fail: 259; error: 25 Build 5: aarch64/2019/apr/30 pass: 5,779; fail: 262; error: 27 Build 6: aarch64/2019/may/02 pass: 5,784; fail: 262; error: 22 Build 7: aarch64/2019/jun/15 pass: 5,827; fail: 242; error: 22 Build 8: aarch64/2019/jun/20 pass: 5,821; fail: 244; error: 26 Build 9: aarch64/2019/jun/29 pass: 5,799; fail: 265; error: 27 Build 10: aarch64/2019/jul/19 pass: 5,940; fail: 278; error: 22 Build 11: aarch64/2019/jul/25 pass: 5,938; fail: 276; error: 26 Build 12: aarch64/2019/jul/30 pass: 5,942; fail: 273; error: 25 Build 13: aarch64/2019/aug/01 pass: 5,945; fail: 271; error: 24 Build 14: aarch64/2019/aug/04 pass: 5,949; fail: 270; error: 24 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/feb/26 pass: 3,114; fail: 2 Build 1: aarch64/2019/feb/28 pass: 3,114; fail: 2 Build 2: aarch64/2019/mar/26 pass: 3,114; fail: 2 Build 3: aarch64/2019/apr/09 pass: 3,115; fail: 2 Build 4: aarch64/2019/apr/18 pass: 3,115; fail: 2 Build 5: aarch64/2019/apr/30 pass: 3,115; fail: 2 Build 6: aarch64/2019/may/02 pass: 3,115; fail: 2 Build 7: aarch64/2019/jun/15 pass: 3,116; fail: 2 Build 8: aarch64/2019/jun/20 pass: 3,116; fail: 2 Build 9: aarch64/2019/jun/29 pass: 3,116; fail: 2 Build 10: aarch64/2019/jul/19 pass: 3,116; fail: 2 Build 11: aarch64/2019/jul/25 pass: 3,116; fail: 2 Build 12: aarch64/2019/jul/30 pass: 3,116; fail: 2 Build 13: aarch64/2019/aug/01 pass: 3,116; fail: 2 Build 14: aarch64/2019/aug/04 pass: 3,116; fail: 2 Previous results can be found here: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 6.73x Relative performance: Server critical-jOPS (nc): 8.17x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 178.67 Server 178.67 / Server 2014-04-01 (71.00): 2.52x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-02-27 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/057/results/ 2019-02-28 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/059/results/ 2019-03-26 pass rate: 8490/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/085/results/ 2019-04-09 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/099/results/ 2019-04-19 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/108/results/ 2019-04-30 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/120/results/ 2019-05-02 pass rate: 8490/8490, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/122/results/ 2019-06-16 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/166/results/ 2019-06-21 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/171/results/ 2019-06-30 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/180/results/ 2019-07-20 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/200/results/ 2019-07-26 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/211/results/ 2019-08-02 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/213/results/ 2019-08-05 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/216/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From shade at redhat.com Mon Aug 5 08:17:09 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 5 Aug 2019 10:17:09 +0200 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator Message-ID: This is the backport of cleanup/removal in 8u-aarch64: https://bugs.openjdk.java.net/browse/JDK-8228400 https://hg.openjdk.java.net/jdk/jdk/rev/01bca26734bb 8u-aarch64 webrev: https://cr.openjdk.java.net/~shade/8228400/webrev.8u.01/ Testing: aarch64 build, hotspot_gc_shenandoah (for the lack of tier1) -- Thanks, -Aleksey From adinn at redhat.com Mon Aug 5 08:37:12 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 5 Aug 2019 09:37:12 +0100 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: References: Message-ID: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> On 05/08/2019 09:17, Aleksey Shipilev wrote: > This is the backport of cleanup/removal in 8u-aarch64: > https://bugs.openjdk.java.net/browse/JDK-8228400 > https://hg.openjdk.java.net/jdk/jdk/rev/01bca26734bb > > 8u-aarch64 webrev: > https://cr.openjdk.java.net/~shade/8228400/webrev.8u.01/ > > Testing: aarch64 build, hotspot_gc_shenandoah (for the lack of tier1) Were there any /significant/ changes relative to the 11u changes? 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 shade at redhat.com Mon Aug 5 08:44:41 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 5 Aug 2019 10:44:41 +0200 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> Message-ID: <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> On 8/5/19 10:37 AM, Andrew Dinn wrote: > On 05/08/2019 09:17, Aleksey Shipilev wrote: >> This is the backport of cleanup/removal in 8u-aarch64: >> https://bugs.openjdk.java.net/browse/JDK-8228400 >> https://hg.openjdk.java.net/jdk/jdk/rev/01bca26734bb >> >> 8u-aarch64 webrev: >> https://cr.openjdk.java.net/~shade/8228400/webrev.8u.01/ >> >> Testing: aarch64 build, hotspot_gc_shenandoah (for the lack of tier1) > Were there any /significant/ changes relative to the 11u changes? Not really. The context is different in some places, so I had to grep again for BUILTIN_SIM and friends, and remove those leftovers. The only change that required more work is changing to call_VM_leaf in c1_CodeStubs_aarch64.cpp: there is no such code in 11+. It would still be good to look through the entire 8u-aarch64 webrev and see if removals are sane. -- Thanks, -Aleksey From shade at redhat.com Mon Aug 5 08:54:18 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 5 Aug 2019 10:54:18 +0200 Subject: [aarch64-port-dev ] RFR (XS) 8229123: Revert build fixes for aarch64/zero Message-ID: RFE: https://bugs.openjdk.java.net/browse/JDK-8229123 Another thing found during 8u-aarch64 webrev scrubbing. Not sure why this thing is needed. Reverting it does not break aarch64/zero cross-compiled build. There is no change like this in any of the upstreams either. Maybe Edward remembers why it is there? 8u-aarch64 fix: diff -r 732ebff024df src/share/vm/interpreter/interpreterRuntime.cpp --- a/src/share/vm/interpreter/interpreterRuntime.cpp Mon Aug 05 09:42:26 2019 +0200 +++ b/src/share/vm/interpreter/interpreterRuntime.cpp Mon Aug 05 10:51:59 2019 +0200 @@ -396,37 +396,35 @@ int handler_bci; int current_bci = bci(thread); -#ifndef CC_INTERP if (thread->frames_to_pop_failed_realloc() > 0) { // Allocation of scalar replaced object used in this frame // failed. Unconditionally pop the frame. thread->dec_frames_to_pop_failed_realloc(); thread->set_vm_result(h_exception()); // If the method is synchronized we already unlocked the monitor // during deoptimization so the interpreter needs to skip it when // the frame is popped. thread->set_do_not_unlock_if_synchronized(true); #ifdef CC_INTERP return (address) -1; #else return Interpreter::remove_activation_entry(); #endif } -#endif // Need to do this check first since when _do_not_unlock_if_synchronized // is set, we don't want to trigger any classloading which may make calls Testing: aarch64 {server,zero} builds; ad-hoc testing zero build -- Thanks, -Aleksey From shade at redhat.com Mon Aug 5 09:20:22 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 5 Aug 2019 11:20:22 +0200 Subject: [aarch64-port-dev ] RFR (XS) 8229124: Revert disassembler.cpp changes Message-ID: <53786189-ad4c-fd9f-24ae-0ff66a111997@redhat.com> RFE: https://bugs.openjdk.java.net/browse/JDK-8229124 Another thing from 8u-aarch64 scrubbing. See issue above for details. 8u-aarch64 fix: diff -r da143ba1b89a src/share/vm/compiler/disassembler.cpp --- a/src/share/vm/compiler/disassembler.cpp Mon Aug 05 10:51:19 2019 +0200 +++ b/src/share/vm/compiler/disassembler.cpp Mon Aug 05 11:19:47 2019 +0200 @@ -473,5 +473,5 @@ NULL, (void*) xmlout, NULL, (void*) out, - options(), 1/*nice new line*/) + options(), 0/*nice new line*/) : (address) Testing: aarch64 build -- Thanks, -Aleksey From adinn at redhat.com Mon Aug 5 09:42:33 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 5 Aug 2019 10:42:33 +0100 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> Message-ID: On 05/08/2019 09:44, Aleksey Shipilev wrote: > On 8/5/19 10:37 AM, Andrew Dinn wrote: >> On 05/08/2019 09:17, Aleksey Shipilev wrote: >>> This is the backport of cleanup/removal in 8u-aarch64: >>> https://bugs.openjdk.java.net/browse/JDK-8228400 >>> https://hg.openjdk.java.net/jdk/jdk/rev/01bca26734bb >>> >>> 8u-aarch64 webrev: >>> https://cr.openjdk.java.net/~shade/8228400/webrev.8u.01/ >>> >>> Testing: aarch64 build, hotspot_gc_shenandoah (for the lack of tier1) >> Were there any /significant/ changes relative to the 11u changes? > > Not really. The context is different in some places, so I had to grep again for BUILTIN_SIM and > friends, and remove those leftovers. The only change that required more work is changing to > call_VM_leaf in c1_CodeStubs_aarch64.cpp: there is no such code in 11+. > > It would still be good to look through the entire 8u-aarch64 webrev and see if removals are sane. Indeed. I worked through all changes and also compared them against your previous 11u change set. The changes which are new in the jdk8u patch are because of: 1) c1 code stubs 2) vtable tweaks (in the metaspace code) 3) os_cpu specific changes 4) c1 calls using blrt 5) (generic only) c1 + nmethod compilation notifies to sim debugger 6) (generic only) relocation notifies in shared runtime 7) (generic only) safe fetch stub routines There are also a few 'equivalent' removals but to code that has is now in a different source file: relocate of templateInterpreter code to templateInterpreterGenerator relocate of interpreter code to templateInterpreterGenerator The specific changes all look correct. So, I don't think there is any problem with the patch ... well, except you have omitted updates to quite a few copyright headers :-] However, this left me wondering why these new changes had turned up. It seems some of these new removals make sense but a couple appear to have been missed from the corresponding 11u files: 3) os_linux_aarch64.cpp 4) c1_Runtime1_aarch64.cpp So, sorry, a jdk11u follow-up is needed. Also, I think quite a few of the copyrights did not get updated in the jdk11u patch :-/ n.b. Andrew Haley carefully deleted all the generic changes when we imported the AArch64 code into JDK9. The rest of the AArch64-specific stuff has disappeared because of global JVM changes (e.g. prefetch and safe fetch functions, vtable tweaking etc all got changed over the years). SO, I think that accounts for why only these 2 jdk11u files have turned up. Of course, it is still possible that some BUILTIN_SIM-related changes are lingering in jdk8u/11u but it looks like this has found almost all if not all of them. 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 Mon Aug 5 10:07:55 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 5 Aug 2019 11:07:55 +0100 Subject: [aarch64-port-dev ] RFR (XS) 8229123: Revert build fixes for aarch64/zero In-Reply-To: References: Message-ID: <6a145084-d0ce-3c39-46a4-8c23c634637a@redhat.com> On 05/08/2019 09:54, Aleksey Shipilev wrote: > RFE: > https://bugs.openjdk.java.net/browse/JDK-8229123 > > Another thing found during 8u-aarch64 webrev scrubbing. Not sure why this thing is needed. Reverting > it does not break aarch64/zero cross-compiled build. There is no change like this in any of the > upstreams either. Maybe Edward remembers why it is there? I ecrtainy don't recognise this code. Maybe Andrew Haley does? Is Ed Nevill's name on the change-set? If so he will probably have had a good reason to add this. Given the comment explaining why this is needed I'm concerned that the error it guards against may only turn up in unusual circumstances which might well explain why standard tests succeeded after removal. Still ... > 8u-aarch64 fix: > > diff -r 732ebff024df src/share/vm/interpreter/interpreterRuntime.cpp > --- a/src/share/vm/interpreter/interpreterRuntime.cpp Mon Aug 05 09:42:26 2019 +0200 > +++ b/src/share/vm/interpreter/interpreterRuntime.cpp Mon Aug 05 10:51:59 2019 +0200 > @@ -396,37 +396,35 @@ > int handler_bci; > int current_bci = bci(thread); > > -#ifndef CC_INTERP > if (thread->frames_to_pop_failed_realloc() > 0) { > // Allocation of scalar replaced object used in this frame > // failed. Unconditionally pop the frame. > thread->dec_frames_to_pop_failed_realloc(); > thread->set_vm_result(h_exception()); > // If the method is synchronized we already unlocked the monitor > // during deoptimization so the interpreter needs to skip it when > // the frame is popped. > thread->set_do_not_unlock_if_synchronized(true); > #ifdef CC_INTERP > return (address) -1; > #else > return Interpreter::remove_activation_entry(); > #endif > } > -#endif > > // Need to do this check first since when _do_not_unlock_if_synchronized > // is set, we don't want to trigger any classloading which may make calls > > Testing: aarch64 {server,zero} builds; ad-hoc testing zero build ... Yuck! Those ifdefs are a mess which does not inspire confidence. Since this is not present and has not yet caused a problem in jdk11u or head I can see why it is very tempting to delete it and wait for the error to turn up. However, that's just what we *ought not* to do in a maintenance release. So, I don't think that's a good enough reason to remove it. I think the only way to proceed here would be to 1) look into how the value returned by thread->frames_to_pop_failed_realloc() can be > 0 and see if the logic of this response really makes sense 2) check with Ed Nevill why he added the code (assuming it was his) 3) work out if ths code really is needed to protect against a potential error and 4) still leave it alone unless those 3 prior investigations provide an utterly sound reason to delete it. Alternatively, you can claim priority of the status quo as force majeure and do nothing. Your choice :-) 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 Mon Aug 5 10:21:46 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 5 Aug 2019 11:21:46 +0100 Subject: [aarch64-port-dev ] RFR (XS) 8229123: Revert build fixes for aarch64/zero In-Reply-To: <6a145084-d0ce-3c39-46a4-8c23c634637a@redhat.com> References: <6a145084-d0ce-3c39-46a4-8c23c634637a@redhat.com> Message-ID: <2c39e600-4c08-27fd-513f-fabae20dbe22@redhat.com> Ah, sorry, I think I got the wrong end of the stick here. You are talking about deleting this from jdk8u-aarch64 in order not to push it up into jdk8u. In that case then the direction and weight of inertia is much more unclear. In theory the status quo derives from the jdk8u upstream code which mans the conservative approach is not to push this change up into jdk8u. However, if anyone has actually been using zero then they I think they may well have been using a Linux build and, for recent builds, that means they will likely have been using the jdk8u-aarch64 code. I'm no longer sure what to do here and would really like Andrew Haley to provide an answer. regards, Andrew Dinn ----------- On 05/08/2019 11:07, Andrew Dinn wrote: > On 05/08/2019 09:54, Aleksey Shipilev wrote: >> RFE: >> https://bugs.openjdk.java.net/browse/JDK-8229123 >> >> Another thing found during 8u-aarch64 webrev scrubbing. Not sure why this thing is needed. Reverting >> it does not break aarch64/zero cross-compiled build. There is no change like this in any of the >> upstreams either. Maybe Edward remembers why it is there? > > I ecrtainy don't recognise this code. Maybe Andrew Haley does? > > Is Ed Nevill's name on the change-set? If so he will probably have had a > good reason to add this. Given the comment explaining why this is needed > I'm concerned that the error it guards against may only turn up in > unusual circumstances which might well explain why standard tests > succeeded after removal. Still ... > >> 8u-aarch64 fix: >> >> diff -r 732ebff024df src/share/vm/interpreter/interpreterRuntime.cpp >> --- a/src/share/vm/interpreter/interpreterRuntime.cpp Mon Aug 05 09:42:26 2019 +0200 >> +++ b/src/share/vm/interpreter/interpreterRuntime.cpp Mon Aug 05 10:51:59 2019 +0200 >> @@ -396,37 +396,35 @@ >> int handler_bci; >> int current_bci = bci(thread); >> >> -#ifndef CC_INTERP >> if (thread->frames_to_pop_failed_realloc() > 0) { >> // Allocation of scalar replaced object used in this frame >> // failed. Unconditionally pop the frame. >> thread->dec_frames_to_pop_failed_realloc(); >> thread->set_vm_result(h_exception()); >> // If the method is synchronized we already unlocked the monitor >> // during deoptimization so the interpreter needs to skip it when >> // the frame is popped. >> thread->set_do_not_unlock_if_synchronized(true); >> #ifdef CC_INTERP >> return (address) -1; >> #else >> return Interpreter::remove_activation_entry(); >> #endif >> } >> -#endif >> >> // Need to do this check first since when _do_not_unlock_if_synchronized >> // is set, we don't want to trigger any classloading which may make calls >> >> Testing: aarch64 {server,zero} builds; ad-hoc testing zero build > ... Yuck! Those ifdefs are a mess which does not inspire confidence. > Since this is not present and has not yet caused a problem in jdk11u or > head I can see why it is very tempting to delete it and wait for the > error to turn up. However, that's just what we *ought not* to do in a > maintenance release. So, I don't think that's a good enough reason to > remove it. > > I think the only way to proceed here would be to 1) look into how the > value returned by thread->frames_to_pop_failed_realloc() can be > 0 and > see if the logic of this response really makes sense 2) check with Ed > Nevill why he added the code (assuming it was his) 3) work out if ths > code really is needed to protect against a potential error and 4) still > leave it alone unless those 3 prior investigations provide an utterly > sound reason to delete it. Alternatively, you can claim priority of the > status quo as force majeure and do nothing. Your choice :-) > > 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 > -- 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 Mon Aug 5 10:22:56 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 5 Aug 2019 11:22:56 +0100 Subject: [aarch64-port-dev ] RFR (XS) 8229124: Revert disassembler.cpp changes In-Reply-To: <53786189-ad4c-fd9f-24ae-0ff66a111997@redhat.com> References: <53786189-ad4c-fd9f-24ae-0ff66a111997@redhat.com> Message-ID: <24af5184-3834-ccb9-ece3-019072541187@redhat.com> On 05/08/2019 10:20, Aleksey Shipilev wrote: > RFE: > https://bugs.openjdk.java.net/browse/JDK-8229124 > > Another thing from 8u-aarch64 scrubbing. See issue above for details. > > 8u-aarch64 fix: > > diff -r da143ba1b89a src/share/vm/compiler/disassembler.cpp > --- a/src/share/vm/compiler/disassembler.cpp Mon Aug 05 10:51:19 2019 +0200 > +++ b/src/share/vm/compiler/disassembler.cpp Mon Aug 05 11:19:47 2019 +0200 > @@ -473,5 +473,5 @@ > NULL, (void*) xmlout, > NULL, (void*) out, > - options(), 1/*nice new line*/) > + options(), 0/*nice new line*/) > : > (address) > > > Testing: aarch64 build I can see no reason for this change to be pushed up into jdk8u. 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 shade at redhat.com Mon Aug 5 10:27:32 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 5 Aug 2019 12:27:32 +0200 Subject: [aarch64-port-dev ] RFR (XS) 8229123: Revert build fixes for aarch64/zero In-Reply-To: <2c39e600-4c08-27fd-513f-fabae20dbe22@redhat.com> References: <6a145084-d0ce-3c39-46a4-8c23c634637a@redhat.com> <2c39e600-4c08-27fd-513f-fabae20dbe22@redhat.com> Message-ID: <0a085db3-6fad-bff9-e8ce-ba9b21b838c7@redhat.com> On 8/5/19 12:21 PM, Andrew Dinn wrote: > Ah, sorry, I think I got the wrong end of the stick here. You are > talking about deleting this from jdk8u-aarch64 in order not to push it > up into jdk8u. Yup. We have to explain why the divergence from 8u upstream is needed. If there is no good explanation, I think the change needs to go. If it does not happen in this RFR, it would inevitably pop up when the "upstreaming" webrev is generated: https://builds.shipilev.net/patch-openjdk-jdk8-aarch64/hotspot/src/share/vm/interpreter/interpreterRuntime.cpp.sdiff.html > However, if anyone has actually been using zero then they I think they > may well have been using a Linux build and, for recent builds, that > means they will likely have been using the jdk8u-aarch64 code. I am pretty sure hardly anybody builds/maintains aarch64/zero to begin with, and if somebody does, they probably either against 8u upstream and have only Zero, or they go full-JIT version from aarch64-port, not something in between. -- Thanks, -Aleksey From shade at redhat.com Mon Aug 5 10:38:54 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 5 Aug 2019 12:38:54 +0200 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> Message-ID: <03a3080e-655f-67c2-24e0-1658113ee8b5@redhat.com> On 8/5/19 11:42 AM, Andrew Dinn wrote: > There are also a few 'equivalent' removals but to code that has is now > in a different source file: > > relocate of templateInterpreter code to templateInterpreterGenerator > relocate of interpreter code to templateInterpreterGenerator > > The specific changes all look correct. So, I don't think there is any > problem with the patch ... well, except you have omitted updates to > quite a few copyright headers :-] Right. There no strict rule here: backporting work does not usually make additional copyright dates changes, unless the backported changeset demands it, or there is a conflict. Removals are even more awkward: consider what happens if the removed code had come in the single changeset. Then it is the usual practice to cleanly backout the complete changeset, even years later, keeping copyright dates untouched. In the 8u-aarch64 case, I think we would need to bulk update copyright headers before 8u upstreaming anyway, so it does not hurt either way. We have also did not do updates in either jdk/jdk changeset (already pushed), jdk11u-dev webrev (can still be amended), or here. So, I'd rather keep the removals without additional changes. Can update the copyrights if you insist. > However, this left me wondering why these new changes had turned up. It > seems some of these new removals make sense but a couple appear to have > been missed from the corresponding 11u files: > > 3) os_linux_aarch64.cpp Not following: 8u: https://cr.openjdk.java.net/~shade/8228400/webrev.8u.01/src/os_cpu/linux_aarch64/vm/os_linux_aarch64.cpp.sdiff.html 11u: https://cr.openjdk.java.net/~shade/8228400/webrev.11u.01/src/hotspot/os_cpu/linux_aarch64/os_linux_aarch64.cpp.sdiff.html The diff is nearly the same. Changed parts are in SPELL_REG_{SP,FP}, and one BUILTIN_SIM block is not removed, because there is no such block in 11u. > 4) c1_Runtime1_aarch64.cpp Not following: 8u: https://cr.openjdk.java.net/~shade/8228400/webrev.8u.01/src/cpu/aarch64/vm/c1_Runtime1_aarch64.cpp.sdiff.html 11u: https://cr.openjdk.java.net/~shade/8228400/webrev.11u.01/src/hotspot/cpu/aarch64/c1_Runtime1_aarch64.cpp.sdiff.html The diff is the same. > So, sorry, a jdk11u follow-up is needed. Also, I think quite a few of > the copyrights did not get updated in the jdk11u patch :-/ See above re: copyright dates. Otherwise, omissions from 11u patch should really be discussed in 11u review thread, which is still open. -- Thanks, -Aleksey From aph at redhat.com Mon Aug 5 10:50:01 2019 From: aph at redhat.com (Andrew Haley) Date: Mon, 5 Aug 2019 03:50:01 -0700 Subject: [aarch64-port-dev ] RFR (XS) 8229123: Revert build fixes for aarch64/zero In-Reply-To: <2c39e600-4c08-27fd-513f-fabae20dbe22@redhat.com> References: <6a145084-d0ce-3c39-46a4-8c23c634637a@redhat.com> <2c39e600-4c08-27fd-513f-fabae20dbe22@redhat.com> Message-ID: On 8/5/19 11:21 AM, Andrew Dinn wrote: > However, if anyone has actually been using zero then they I think they > may well have been using a Linux build and, for recent builds, that > means they will likely have been using the jdk8u-aarch64 code. > > I'm no longer sure what to do here and would really like Andrew Haley to > provide an answer. According to the comment it's for AArch64 Zero only, so it shouldn't be merged into jdk8u. Sure, something might break somewhere, but we must minimize changes to shared code when doing the AArch64 merge into 8u. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Mon Aug 5 11:22:04 2019 From: aph at redhat.com (Andrew Haley) Date: Mon, 5 Aug 2019 12:22:04 +0100 Subject: [aarch64-port-dev ] RFR (XS) 8229124: Revert disassembler.cpp changes In-Reply-To: <24af5184-3834-ccb9-ece3-019072541187@redhat.com> References: <53786189-ad4c-fd9f-24ae-0ff66a111997@redhat.com> <24af5184-3834-ccb9-ece3-019072541187@redhat.com> Message-ID: On 8/5/19 11:22 AM, Andrew Dinn wrote: > I can see no reason for this change to be pushed up into jdk8u. Indeed. Unless there's some extraordinarily good reason there should be no changes to shared code except the necessary ones guarded by ifdef AARCH64. That way we can be certain that the import into 8u cannot break anything. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From shade at redhat.com Mon Aug 5 12:36:33 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 5 Aug 2019 14:36:33 +0200 Subject: [aarch64-port-dev ] RFR (XS) 8229124: Revert disassembler.cpp changes In-Reply-To: References: <53786189-ad4c-fd9f-24ae-0ff66a111997@redhat.com> <24af5184-3834-ccb9-ece3-019072541187@redhat.com> Message-ID: <30e6c60f-81b9-1f70-1f1f-36aa56d475c0@redhat.com> On 8/5/19 1:22 PM, Andrew Haley wrote: > On 8/5/19 11:22 AM, Andrew Dinn wrote: >> I can see no reason for this change to be pushed up into jdk8u. > > Indeed. Unless there's some extraordinarily good reason there should > be no changes to shared code except the necessary ones guarded by > ifdef AARCH64. That way we can be certain that the import into 8u > cannot break anything. I am a bit confused if this counts as approval to push to 8u-aarch64 or not. It seems to be! To be clear: I am going to push this reversal to aarch64-port/jdk8u-shenandoah to minimize upstream differences. -- Thanks, -Aleksey From shade at redhat.com Mon Aug 5 12:37:00 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 5 Aug 2019 14:37:00 +0200 Subject: [aarch64-port-dev ] RFR (XS) 8229123: Revert build fixes for aarch64/zero In-Reply-To: References: <6a145084-d0ce-3c39-46a4-8c23c634637a@redhat.com> <2c39e600-4c08-27fd-513f-fabae20dbe22@redhat.com> Message-ID: <2dbc31d9-5bf9-7cb5-579c-5a673c788571@redhat.com> On 8/5/19 12:50 PM, Andrew Haley wrote: > On 8/5/19 11:21 AM, Andrew Dinn wrote: >> However, if anyone has actually been using zero then they I think they >> may well have been using a Linux build and, for recent builds, that >> means they will likely have been using the jdk8u-aarch64 code. >> >> I'm no longer sure what to do here and would really like Andrew Haley to >> provide an answer. > > According to the comment it's for AArch64 Zero only, so it shouldn't > be merged into jdk8u. Sure, something might break somewhere, but we > must minimize changes to shared code when doing the AArch64 merge into > 8u. Here too! I am a bit confused if this counts as approval to push to 8u-aarch64 or not. It seems to be. To be clear: I am going to push this reversal to aarch64-port/jdk8u-shenandoah to minimize upstream differences. -- Thanks, -Aleksey From adinn at redhat.com Mon Aug 5 12:37:36 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 5 Aug 2019 13:37:36 +0100 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: <03a3080e-655f-67c2-24e0-1658113ee8b5@redhat.com> References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> <03a3080e-655f-67c2-24e0-1658113ee8b5@redhat.com> Message-ID: <36e8b083-53ba-51fc-98cd-1f342f4414f1@redhat.com> On 05/08/2019 11:38, Aleksey Shipilev wrote: > On 8/5/19 11:42 AM, Andrew Dinn wrote: >> There are also a few 'equivalent' removals but to code that has is now >> in a different source file: >> >> relocate of templateInterpreter code to templateInterpreterGenerator >> relocate of interpreter code to templateInterpreterGenerator >> >> The specific changes all look correct. So, I don't think there is any >> problem with the patch ... well, except you have omitted updates to >> quite a few copyright headers :-] > > Right. There no strict rule here: backporting work does not usually make additional copyright dates > changes, unless the backported changeset demands it, or there is a conflict. Removals are even more > awkward: consider what happens if the removed code had come in the single changeset. Then it is the > usual practice to cleanly backout the complete changeset, even years later, keeping copyright dates > untouched. > > In the 8u-aarch64 case, I think we would need to bulk update copyright headers before 8u upstreaming > anyway, so it does not hurt either way. We have also did not do updates in either jdk/jdk changeset > (already pushed), jdk11u-dev webrev (can still be amended), or here. So, I'd rather keep the > removals without additional changes. Can update the copyrights if you insist. No, I'm fine if you leave the copyrights. >> However, this left me wondering why these new changes had turned up. It >> seems some of these new removals make sense but a couple appear to have >> been missed from the corresponding 11u files: >> >> 3) os_linux_aarch64.cpp > > Not following: Ah, I was comparing your 8u deletions against the code currently in the latest jdk11u and found the deleted code still present. However, I see now that your check in to remove the changes from upstream jdk11 was relative to jdk11u-dev and is not yet yet in jdk11u. So, please ignore the comments about jdk11u (including copyrights). The patch is fine as is. 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 Mon Aug 5 12:39:32 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 5 Aug 2019 13:39:32 +0100 Subject: [aarch64-port-dev ] RFR (XS) 8229124: Revert disassembler.cpp changes In-Reply-To: <30e6c60f-81b9-1f70-1f1f-36aa56d475c0@redhat.com> References: <53786189-ad4c-fd9f-24ae-0ff66a111997@redhat.com> <24af5184-3834-ccb9-ece3-019072541187@redhat.com> <30e6c60f-81b9-1f70-1f1f-36aa56d475c0@redhat.com> Message-ID: On 05/08/2019 13:36, Aleksey Shipilev wrote: > On 8/5/19 1:22 PM, Andrew Haley wrote: >> On 8/5/19 11:22 AM, Andrew Dinn wrote: >>> I can see no reason for this change to be pushed up into jdk8u. >> >> Indeed. Unless there's some extraordinarily good reason there should >> be no changes to shared code except the necessary ones guarded by >> ifdef AARCH64. That way we can be certain that the import into 8u >> cannot break anything. > > I am a bit confused if this counts as approval to push to 8u-aarch64 or not. It seems to be! To be > clear: I am going to push this reversal to aarch64-port/jdk8u-shenandoah to minimize upstream > differences. Yes, go ahead and delete this from 8u-aarch64 so it does not cause a change 8u when it is upstreamed there. That's what he meant. And what I meant. 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 shade at redhat.com Mon Aug 5 16:52:39 2019 From: shade at redhat.com (shade at redhat.com) Date: Mon, 05 Aug 2019 16:52:39 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 2 new changesets Message-ID: <201908051652.x75Gqe1N024111@aojmv0008.oracle.com> Changeset: 4f136fd7cee6 Author: shade Date: 2019-08-05 14:47 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/4f136fd7cee6 8229123: Revert build fixes for aarch64/zero Reviewed-by: aph, adinn ! src/share/vm/interpreter/interpreterRuntime.cpp Changeset: a979325732aa Author: shade Date: 2019-08-05 14:47 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/a979325732aa 8229124: Revert disassembler.cpp changes Reviewed-by: adinn, aph ! src/share/vm/compiler/disassembler.cpp From shade at redhat.com Mon Aug 5 16:56:48 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 5 Aug 2019 18:56:48 +0200 Subject: [aarch64-port-dev ] RFR (XS) 8229124: Revert disassembler.cpp changes In-Reply-To: References: <53786189-ad4c-fd9f-24ae-0ff66a111997@redhat.com> <24af5184-3834-ccb9-ece3-019072541187@redhat.com> <30e6c60f-81b9-1f70-1f1f-36aa56d475c0@redhat.com> Message-ID: On 8/5/19 2:39 PM, Andrew Dinn wrote: > On 05/08/2019 13:36, Aleksey Shipilev wrote: >> On 8/5/19 1:22 PM, Andrew Haley wrote: >>> On 8/5/19 11:22 AM, Andrew Dinn wrote: >>>> I can see no reason for this change to be pushed up into jdk8u. >>> >>> Indeed. Unless there's some extraordinarily good reason there should >>> be no changes to shared code except the necessary ones guarded by >>> ifdef AARCH64. That way we can be certain that the import into 8u >>> cannot break anything. >> >> I am a bit confused if this counts as approval to push to 8u-aarch64 or not. It seems to be! To be >> clear: I am going to push this reversal to aarch64-port/jdk8u-shenandoah to minimize upstream >> differences. > Yes, go ahead and delete this from 8u-aarch64 so it does not cause a > change 8u when it is upstreamed there. That's what he meant. And what I > meant. Good. Pushed! -- Thanks, -Aleksey From shade at redhat.com Mon Aug 5 16:57:15 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 5 Aug 2019 18:57:15 +0200 Subject: [aarch64-port-dev ] RFR (XS) 8229123: Revert build fixes for aarch64/zero In-Reply-To: <2dbc31d9-5bf9-7cb5-579c-5a673c788571@redhat.com> References: <6a145084-d0ce-3c39-46a4-8c23c634637a@redhat.com> <2c39e600-4c08-27fd-513f-fabae20dbe22@redhat.com> <2dbc31d9-5bf9-7cb5-579c-5a673c788571@redhat.com> Message-ID: On 8/5/19 2:37 PM, Aleksey Shipilev wrote: > On 8/5/19 12:50 PM, Andrew Haley wrote: >> On 8/5/19 11:21 AM, Andrew Dinn wrote: >>> However, if anyone has actually been using zero then they I think they >>> may well have been using a Linux build and, for recent builds, that >>> means they will likely have been using the jdk8u-aarch64 code. >>> >>> I'm no longer sure what to do here and would really like Andrew Haley to >>> provide an answer. >> >> According to the comment it's for AArch64 Zero only, so it shouldn't >> be merged into jdk8u. Sure, something might break somewhere, but we >> must minimize changes to shared code when doing the AArch64 merge into >> 8u. > > Here too! I am a bit confused if this counts as approval to push to 8u-aarch64 or not. It seems to > be. To be clear: I am going to push this reversal to aarch64-port/jdk8u-shenandoah to minimize > upstream differences. Pushed, using the interpretation from the other thread :) -- Thanks, -Aleksey From shade at redhat.com Mon Aug 5 18:09:42 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 5 Aug 2019 20:09:42 +0200 Subject: [aarch64-port-dev ] RFR (XS) 8229145: Revert TemplateTable::bytecode() visibility change Message-ID: RFE: https://bugs.openjdk.java.net/browse/JDK-8229145 This is 8u-aarch64 specific thing, found again during 8u webrev scrubbing. See details in JIRA. Reversal: diff -r a979325732aa src/share/vm/interpreter/templateTable.hpp --- a/src/share/vm/interpreter/templateTable.hpp Mon Aug 05 14:47:20 2019 +0200 +++ b/src/share/vm/interpreter/templateTable.hpp Mon Aug 05 20:09:05 2019 +0200 @@ -102,10 +102,7 @@ static Template* _desc; // the current template to be generated - public: static Bytecodes::Code bytecode() { return _desc->bytecode(); } - private: static BarrierSet* _bs; // Cache the barrier set. - public: //%note templates_1 Testing: {x86_64, aarch64} x {fastdebug, release}, hotspot_gc_shenandoah (for the lack of tier1) -- Thanks, -Aleksey From aph at redhat.com Mon Aug 5 21:05:10 2019 From: aph at redhat.com (Andrew Haley) Date: Mon, 5 Aug 2019 22:05:10 +0100 Subject: [aarch64-port-dev ] RFR (XS) 8229145: Revert TemplateTable::bytecode() visibility change In-Reply-To: References: Message-ID: <445a3c5d-df09-db51-0455-07b2b7729c41@redhat.com> On 8/5/19 7:09 PM, Aleksey Shipilev wrote: > RFE: > https://bugs.openjdk.java.net/browse/JDK-8229145 > > This is 8u-aarch64 specific thing, found again during 8u webrev scrubbing. See details in JIRA. OK -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Tue Aug 6 02:35:06 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Tue, 6 Aug 2019 02:35:06 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <1827526092.4923.1565058909406.JavaMail.jenkins@6e40b75d9e9e> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2019/217/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/03 pass: 5,654; fail: 2 Build 1: aarch64/2019/jul/05 pass: 5,653; fail: 3 Build 2: aarch64/2019/jul/09 pass: 5,695; fail: 3 Build 3: aarch64/2019/jul/11 pass: 5,696; fail: 3 Build 4: aarch64/2019/jul/12 pass: 5,695; fail: 5 Build 5: aarch64/2019/jul/15 pass: 5,699; fail: 1 Build 6: aarch64/2019/jul/17 pass: 5,700; fail: 1; error: 1 Build 7: aarch64/2019/jul/19 pass: 5,699; fail: 3; error: 1 Build 8: aarch64/2019/jul/22 pass: 5,705; fail: 2 Build 9: aarch64/2019/jul/24 pass: 5,706; fail: 1 Build 10: aarch64/2019/jul/26 pass: 5,707; fail: 2 Build 11: aarch64/2019/jul/29 pass: 5,705; fail: 4 Build 12: aarch64/2019/jul/31 pass: 5,711; fail: 1 Build 13: aarch64/2019/aug/02 pass: 5,711; fail: 2 Build 14: aarch64/2019/aug/05 pass: 5,712; fail: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/03 pass: 8,609; fail: 525; error: 21 Build 1: aarch64/2019/jul/05 pass: 8,612; fail: 515; error: 28 Build 2: aarch64/2019/jul/09 pass: 8,604; fail: 532; error: 19 Build 3: aarch64/2019/jul/11 pass: 8,598; fail: 529; error: 31 Build 4: aarch64/2019/jul/12 pass: 8,601; fail: 528; error: 29 Build 5: aarch64/2019/jul/15 pass: 8,602; fail: 533; error: 25 Build 6: aarch64/2019/jul/17 pass: 8,614; fail: 522; error: 24 Build 7: aarch64/2019/jul/19 pass: 8,611; fail: 526; error: 26 Build 8: aarch64/2019/jul/22 pass: 8,628; fail: 511; error: 24 Build 9: aarch64/2019/jul/24 pass: 8,617; fail: 538; error: 26 Build 10: aarch64/2019/jul/26 pass: 8,649; fail: 518; error: 17 Build 11: aarch64/2019/jul/29 pass: 8,640; fail: 520; error: 26 Build 12: aarch64/2019/jul/31 pass: 8,640; fail: 526; error: 24 Build 13: aarch64/2019/aug/02 pass: 8,637; fail: 524; error: 29 Build 14: aarch64/2019/aug/05 pass: 8,642; fail: 519; error: 29 3 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/03 pass: 3,964 Build 1: aarch64/2019/jul/05 pass: 3,965 Build 2: aarch64/2019/jul/09 pass: 3,967 Build 3: aarch64/2019/jul/11 pass: 3,968 Build 4: aarch64/2019/jul/12 pass: 3,968 Build 5: aarch64/2019/jul/15 pass: 3,968 Build 6: aarch64/2019/jul/17 pass: 3,968 Build 7: aarch64/2019/jul/19 pass: 3,969 Build 8: aarch64/2019/jul/22 pass: 3,969 Build 9: aarch64/2019/jul/24 pass: 3,970 Build 10: aarch64/2019/jul/26 pass: 3,970 Build 11: aarch64/2019/jul/29 pass: 3,970 Build 12: aarch64/2019/jul/31 pass: 3,970 Build 13: aarch64/2019/aug/02 pass: 3,970 Build 14: aarch64/2019/aug/05 pass: 3,970 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.63x Relative performance: Server critical-jOPS (nc): 9.51x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 204.57 Server 204.57 / Server 2014-04-01 (71.00): 2.88x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-01-01 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/365/results/ 2019-07-04 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/184/results/ 2019-07-05 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/186/results/ 2019-07-10 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/190/results/ 2019-07-12 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/192/results/ 2019-07-15 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/196/results/ 2019-07-17 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/198/results/ 2019-07-20 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/200/results/ 2019-07-22 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/203/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/205/results/ 2019-07-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/207/results/ 2019-07-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/210/results/ 2019-08-01 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/212/results/ 2019-08-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/214/results/ 2019-08-06 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/217/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From adinn at redhat.com Tue Aug 6 07:56:36 2019 From: adinn at redhat.com (Andrew Dinn) Date: Tue, 6 Aug 2019 08:56:36 +0100 Subject: [aarch64-port-dev ] RFR (XS) 8229145: Revert TemplateTable::bytecode() visibility change In-Reply-To: References: Message-ID: <50025147-6548-b3e9-e52b-ce3b217c34ba@redhat.com> On 05/08/2019 19:09, Aleksey Shipilev wrote: > RFE: > https://bugs.openjdk.java.net/browse/JDK-8229145 > > This is 8u-aarch64 specific thing, found again during 8u webrev scrubbing. See details in JIRA. > > Reversal: > > diff -r a979325732aa src/share/vm/interpreter/templateTable.hpp > --- a/src/share/vm/interpreter/templateTable.hpp Mon Aug 05 14:47:20 2019 +0200 > +++ b/src/share/vm/interpreter/templateTable.hpp Mon Aug 05 20:09:05 2019 +0200 > @@ -102,10 +102,7 @@ > > static Template* _desc; // the current template to be generated > - public: > static Bytecodes::Code bytecode() { return _desc->bytecode(); } > > - private: > static BarrierSet* _bs; // Cache the barrier set. > - > public: > //%note templates_1 > > Testing: {x86_64, aarch64} x {fastdebug, release}, hotspot_gc_shenandoah (for the lack of tier1) This was needed at one point to allow the sim debugger to access bytecodes and compute line numbers. It should go. 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 shade at redhat.com Tue Aug 6 08:41:48 2019 From: shade at redhat.com (shade at redhat.com) Date: Tue, 06 Aug 2019 08:41:48 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 8229145: Revert TemplateTable::bytecode() visibility change Message-ID: <201908060841.x768fmHJ023644@aojmv0008.oracle.com> Changeset: ec6db58f37d4 Author: shade Date: 2019-08-06 10:22 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/ec6db58f37d4 8229145: Revert TemplateTable::bytecode() visibility change Reviewed-by: aph, adinn ! src/share/vm/interpreter/templateTable.hpp From shade at redhat.com Tue Aug 6 08:42:32 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Tue, 6 Aug 2019 10:42:32 +0200 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: <36e8b083-53ba-51fc-98cd-1f342f4414f1@redhat.com> References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> <03a3080e-655f-67c2-24e0-1658113ee8b5@redhat.com> <36e8b083-53ba-51fc-98cd-1f342f4414f1@redhat.com> Message-ID: On 8/5/19 2:37 PM, Andrew Dinn wrote: > No, I'm fine if you leave the copyrights. Ok, thanks. Do I need to wait for Andrew Haley to ack this removal too? Thanks, -Aleksey From adinn at redhat.com Tue Aug 6 08:45:06 2019 From: adinn at redhat.com (Andrew Dinn) Date: Tue, 6 Aug 2019 09:45:06 +0100 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> <03a3080e-655f-67c2-24e0-1658113ee8b5@redhat.com> <36e8b083-53ba-51fc-98cd-1f342f4414f1@redhat.com> Message-ID: On 06/08/2019 09:42, Aleksey Shipilev wrote: > On 8/5/19 2:37 PM, Andrew Dinn wrote: >> No, I'm fine if you leave the copyrights. > > Ok, thanks. Do I need to wait for Andrew Haley to ack this removal too? No, please push. 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 Tue Aug 6 08:49:17 2019 From: adinn at redhat.com (Andrew Dinn) Date: Tue, 6 Aug 2019 09:49:17 +0100 Subject: [aarch64-port-dev ] Fwd: 8u-aarch64 : Backport 8163363: AArch64: Stack size in tools/launcher/Settings.java needs to be adjusted In-Reply-To: References: Message-ID: <7449235e-a95b-ce5c-214e-3986940dfad4@redhat.com> I'm re-forwarding to aarch64-port-dev this note that I sent in error to jdk8u-dev (apparently my previous forward is stalled awaiting moderator approval because I bcced jdk8u-dev). See after sig for details. regards, Andrew Dinn ----------- -------- Forwarded Message -------- Subject: 8u: Backport 8163363: AArch64: Stack size in tools/launcher/Settings.java needs to be adjusted Date: Mon, 5 Aug 2019 17:23:55 +0100 From: Andrew Dinn To: jdk8u-dev at openjdk.java.net I would like permission to backport this fix to the jdk8u-aarch64-shenandoah repo. This fixes the minimum stack size used by jdk/test/tools/launcher/Settings.java so that it is large enough to allow the test to pass on AArch64 implementations where it previously failed. The backport requires a minor tweak to the original patch as per the following webrev: http://cr.openjdk.java.net/~adinn/8163363-jdk8u/webrev.00/ 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 shade at redhat.com Tue Aug 6 09:13:45 2019 From: shade at redhat.com (shade at redhat.com) Date: Tue, 06 Aug 2019 09:13:45 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 8228400: Remove built-in AArch64 simulator Message-ID: <201908060913.x769Dk4B010873@aojmv0008.oracle.com> Changeset: eaf9b36b7a30 Author: shade Date: 2019-08-06 10:45 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/eaf9b36b7a30 8228400: Remove built-in AArch64 simulator Reviewed-by: adinn, aph, dsamersoff ! make/linux/makefiles/aarch64.make ! make/linux/makefiles/vm.make ! src/cpu/aarch64/vm/aarch64.ad - src/cpu/aarch64/vm/aarch64_call.cpp - src/cpu/aarch64/vm/aarch64_linkage.S ! src/cpu/aarch64/vm/assembler_aarch64.cpp ! src/cpu/aarch64/vm/assembler_aarch64.hpp ! src/cpu/aarch64/vm/c1_CodeStubs_aarch64.cpp ! src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp ! src/cpu/aarch64/vm/c1_MacroAssembler_aarch64.cpp ! src/cpu/aarch64/vm/c1_Runtime1_aarch64.cpp ! src/cpu/aarch64/vm/c1_globals_aarch64.hpp - src/cpu/aarch64/vm/cpustate_aarch64.hpp - src/cpu/aarch64/vm/decode_aarch64.hpp ! src/cpu/aarch64/vm/globals_aarch64.hpp ! src/cpu/aarch64/vm/immediate_aarch64.cpp ! src/cpu/aarch64/vm/interpreter_aarch64.cpp ! src/cpu/aarch64/vm/macroAssembler_aarch64.cpp ! src/cpu/aarch64/vm/macroAssembler_aarch64.hpp ! src/cpu/aarch64/vm/metaspaceShared_aarch64.cpp ! src/cpu/aarch64/vm/sharedRuntime_aarch64.cpp ! src/cpu/aarch64/vm/stubGenerator_aarch64.cpp ! src/cpu/aarch64/vm/stubRoutines_aarch64.hpp ! src/cpu/aarch64/vm/templateInterpreter_aarch64.cpp ! src/cpu/aarch64/vm/templateTable_aarch64.cpp ! src/cpu/aarch64/vm/vm_version_aarch64.cpp ! src/os/linux/vm/os_linux.cpp ! src/os_cpu/linux_aarch64/vm/assembler_linux_aarch64.cpp - src/os_cpu/linux_aarch64/vm/linux_aarch64.S ! src/os_cpu/linux_aarch64/vm/os_linux_aarch64.cpp ! src/os_cpu/linux_aarch64/vm/prefetch_linux_aarch64.inline.hpp ! src/share/vm/c1/c1_Compilation.cpp ! src/share/vm/c1/c1_Runtime1.cpp ! src/share/vm/code/nmethod.cpp ! src/share/vm/interpreter/templateTable.cpp ! src/share/vm/memory/metaspaceShared.cpp ! src/share/vm/memory/metaspaceShared.hpp ! src/share/vm/opto/compile.cpp ! src/share/vm/runtime/os.hpp ! src/share/vm/runtime/sharedRuntime.cpp ! src/share/vm/runtime/stubRoutines.cpp ! src/share/vm/runtime/stubRoutines.hpp From shade at redhat.com Tue Aug 6 09:14:28 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Tue, 6 Aug 2019 11:14:28 +0200 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> <03a3080e-655f-67c2-24e0-1658113ee8b5@redhat.com> <36e8b083-53ba-51fc-98cd-1f342f4414f1@redhat.com> Message-ID: <4dd9405e-bb1b-3da7-fcf5-0facffa00ab8@redhat.com> On 8/6/19 10:45 AM, Andrew Dinn wrote: > On 06/08/2019 09:42, Aleksey Shipilev wrote: >> On 8/5/19 2:37 PM, Andrew Dinn wrote: >>> No, I'm fine if you leave the copyrights. >> >> Ok, thanks. Do I need to wait for Andrew Haley to ack this removal too? > No, please push. Thanks, pushed. This concludes the first round of scrubbing of aarch64-port. There are plenty of Shenandoah 8u things to clean up, which we would do next. -- Thanks, -Aleksey From aph at redhat.com Tue Aug 6 10:06:18 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 6 Aug 2019 11:06:18 +0100 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: <4dd9405e-bb1b-3da7-fcf5-0facffa00ab8@redhat.com> References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> <03a3080e-655f-67c2-24e0-1658113ee8b5@redhat.com> <36e8b083-53ba-51fc-98cd-1f342f4414f1@redhat.com> <4dd9405e-bb1b-3da7-fcf5-0facffa00ab8@redhat.com> Message-ID: <6a93050b-d201-fba7-b28a-61eb4a98d832@redhat.com> On 8/6/19 10:14 AM, Aleksey Shipilev wrote: > This concludes the first round of scrubbing of aarch64-port. There are plenty of Shenandoah 8u > things to clean up, which we would do next. It would make more sense to prepare the aarch64-port 8u patch, wouldn't it? -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From shade at redhat.com Tue Aug 6 10:09:17 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Tue, 6 Aug 2019 12:09:17 +0200 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: <6a93050b-d201-fba7-b28a-61eb4a98d832@redhat.com> References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> <03a3080e-655f-67c2-24e0-1658113ee8b5@redhat.com> <36e8b083-53ba-51fc-98cd-1f342f4414f1@redhat.com> <4dd9405e-bb1b-3da7-fcf5-0facffa00ab8@redhat.com> <6a93050b-d201-fba7-b28a-61eb4a98d832@redhat.com> Message-ID: On 8/6/19 12:06 PM, Andrew Haley wrote: > On 8/6/19 10:14 AM, Aleksey Shipilev wrote: >> This concludes the first round of scrubbing of aarch64-port. There are plenty of Shenandoah 8u >> things to clean up, which we would do next. > > It would make more sense to prepare the aarch64-port 8u patch, wouldn't it? Not sure what you mean. Shenandoah-specific changes are normally done in sh/jdk8, where we test them aggressively before merging them in bulk to aarch64-port/jdk8u-shenandoah. This minimizes regression risks. -- Thanks, -Aleksey From aph at redhat.com Tue Aug 6 12:29:48 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 6 Aug 2019 13:29:48 +0100 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> <03a3080e-655f-67c2-24e0-1658113ee8b5@redhat.com> <36e8b083-53ba-51fc-98cd-1f342f4414f1@redhat.com> <4dd9405e-bb1b-3da7-fcf5-0facffa00ab8@redhat.com> <6a93050b-d201-fba7-b28a-61eb4a98d832@redhat.com> Message-ID: On 8/6/19 11:09 AM, Aleksey Shipilev wrote: > On 8/6/19 12:06 PM, Andrew Haley wrote: >> On 8/6/19 10:14 AM, Aleksey Shipilev wrote: >>> This concludes the first round of scrubbing of aarch64-port. There are plenty of Shenandoah 8u >>> things to clean up, which we would do next. >> >> It would make more sense to prepare the aarch64-port 8u patch, wouldn't it? > > Not sure what you mean. Shenandoah-specific changes are normally > done in sh/jdk8, where we test them aggressively before merging them > in bulk to aarch64-port/jdk8u-shenandoah. This minimizes regression > risks. Sure, but it would also be a good idea to get the jdk8u aarch64 merge webrev ready so we can begin reviewing it. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From shade at redhat.com Tue Aug 6 12:33:11 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Tue, 6 Aug 2019 14:33:11 +0200 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> <03a3080e-655f-67c2-24e0-1658113ee8b5@redhat.com> <36e8b083-53ba-51fc-98cd-1f342f4414f1@redhat.com> <4dd9405e-bb1b-3da7-fcf5-0facffa00ab8@redhat.com> <6a93050b-d201-fba7-b28a-61eb4a98d832@redhat.com> Message-ID: On 8/6/19 2:29 PM, Andrew Haley wrote: > On 8/6/19 11:09 AM, Aleksey Shipilev wrote: >> On 8/6/19 12:06 PM, Andrew Haley wrote: >>> On 8/6/19 10:14 AM, Aleksey Shipilev wrote: >>>> This concludes the first round of scrubbing of aarch64-port. There are plenty of Shenandoah 8u >>>> things to clean up, which we would do next. >>> >>> It would make more sense to prepare the aarch64-port 8u patch, wouldn't it? >> >> Not sure what you mean. Shenandoah-specific changes are normally >> done in sh/jdk8, where we test them aggressively before merging them >> in bulk to aarch64-port/jdk8u-shenandoah. This minimizes regression >> risks. > > Sure, but it would also be a good idea to get the jdk8u aarch64 merge > webrev ready so we can begin reviewing it. Be my guest: https://builds.shipilev.net/patch-openjdk-jdk8-aarch64/ (autogenerated) I thought we wanted to merge the entirety if aarch64-port/jdk8u-shenandoah in one swoop. The webrev above is the difference between aarch64-port/jdk8u-shenandoah and jdk8u upstream. It is still not that close to something I would be comfortable to propose. -- Thanks, -Aleksey From aph at redhat.com Tue Aug 6 13:12:32 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 6 Aug 2019 14:12:32 +0100 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> <03a3080e-655f-67c2-24e0-1658113ee8b5@redhat.com> <36e8b083-53ba-51fc-98cd-1f342f4414f1@redhat.com> <4dd9405e-bb1b-3da7-fcf5-0facffa00ab8@redhat.com> <6a93050b-d201-fba7-b28a-61eb4a98d832@redhat.com> Message-ID: <27f0bfbc-4b22-347a-7c7b-58002a4c713d@redhat.com> On 8/6/19 1:33 PM, Aleksey Shipilev wrote: > I thought we wanted to merge the entirety if > aarch64-port/jdk8u-shenandoah in one swoop. True. It might well be the easiest thing to do, but OTOH I'm not sure it'll make for an easy review. > The webrev above is the difference between > aarch64-port/jdk8u-shenandoah and jdk8u upstream. It is still not > that close to something I would be comfortable to propose. Oh, I see; I didn't understand what you were trying to do. I thought it was all part of the aarch64 backport, hence my bafflement. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From shade at redhat.com Tue Aug 6 15:29:00 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Tue, 6 Aug 2019 17:29:00 +0200 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: <27f0bfbc-4b22-347a-7c7b-58002a4c713d@redhat.com> References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> <03a3080e-655f-67c2-24e0-1658113ee8b5@redhat.com> <36e8b083-53ba-51fc-98cd-1f342f4414f1@redhat.com> <4dd9405e-bb1b-3da7-fcf5-0facffa00ab8@redhat.com> <6a93050b-d201-fba7-b28a-61eb4a98d832@redhat.com> <27f0bfbc-4b22-347a-7c7b-58002a4c713d@redhat.com> Message-ID: <3f0d2596-edfe-8e3c-ac82-78dd0b50319f@redhat.com> On 8/6/19 3:12 PM, Andrew Haley wrote: > On 8/6/19 1:33 PM, Aleksey Shipilev wrote: > >> I thought we wanted to merge the entirety if >> aarch64-port/jdk8u-shenandoah in one swoop. > > True. It might well be the easiest thing to do, but OTOH I'm not sure > it'll make for an easy review. > >> The webrev above is the difference between >> aarch64-port/jdk8u-shenandoah and jdk8u upstream. It is still not >> that close to something I would be comfortable to propose. > > Oh, I see; I didn't understand what you were trying to do. I thought > it was all part of the aarch64 backport, hence my bafflement. My goal is to make aarch64-port/jdk8u-shenandoah vs jdk8u difference as narrow as possible, before the heat of the actual review whenever we propose aarch64-port/jdk8u-shenandoah for inclusion to jdk8u. I usually invite everyone to look through those autogenerated webrevs and chip away differences one by one. When we were doing Shenandoah upstreaming, it was by far the sanest way to go about bulk contribution. (The alternative is juggling staging repositories and/or 100 KLOC webrevs, good luck with that.) There are a few minor Shenandoah 8u cleanups pending, and there is also the major ones (LRB and nofwdptr), which should trim out the significant part of it. None of this changes the processes we have already: everything Shenandoah-related comes with Shenandoah integrations, after Shenandoah testing :) -- Thanks, -Aleksey From shade at redhat.com Tue Aug 6 16:35:25 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Tue, 6 Aug 2019 18:35:25 +0200 Subject: [aarch64-port-dev ] Fwd: 8u-aarch64 : Backport 8163363: AArch64: Stack size in tools/launcher/Settings.java needs to be adjusted In-Reply-To: <7449235e-a95b-ce5c-214e-3986940dfad4@redhat.com> References: <7449235e-a95b-ce5c-214e-3986940dfad4@redhat.com> Message-ID: <10d22723-ac38-06f0-0255-bc51a04727bb@redhat.com> On 8/6/19 10:49 AM, Andrew Dinn wrote: > The backport requires a minor tweak to the original patch as per the > following webrev: > > http://cr.openjdk.java.net/~adinn/8163363-jdk8u/webrev.00/ *) I don't understand, why "ppc64le" case was added? 78 if (getArch().equals("ppc64") || getArch().equals("ppc64le")) { *) Original change has this comment, are we ignoring it? // Check the stack size logs printed by -XshowSettings to verify -Xss meaningfully. Otherwise looks okay. -- Thanks, -Aleksey From adinn at redhat.com Tue Aug 6 16:48:44 2019 From: adinn at redhat.com (Andrew Dinn) Date: Tue, 6 Aug 2019 17:48:44 +0100 Subject: [aarch64-port-dev ] Fwd: 8u-aarch64 : Backport 8163363: AArch64: Stack size in tools/launcher/Settings.java needs to be adjusted In-Reply-To: <10d22723-ac38-06f0-0255-bc51a04727bb@redhat.com> References: <7449235e-a95b-ce5c-214e-3986940dfad4@redhat.com> <10d22723-ac38-06f0-0255-bc51a04727bb@redhat.com> Message-ID: <22a4332b-be17-d0b8-2ee8-375662cc9696@redhat.com> On 06/08/2019 17:35, Aleksey Shipilev wrote: > On 8/6/19 10:49 AM, Andrew Dinn wrote: >> The backport requires a minor tweak to the original patch as per the >> following webrev: >> >> http://cr.openjdk.java.net/~adinn/8163363-jdk8u/webrev.00/ > > *) I don't understand, why "ppc64le" case was added? > > 78 if (getArch().equals("ppc64") || getArch().equals("ppc64le")) { That is because I back-ported the original patch and it was included in that patch and went in automatically. Is ppc64le not a thing in jdk8u? If so I can remove it. > *) Original change has this comment, are we ignoring it? > > // Check the stack size logs printed by -XshowSettings to verify -Xss meaningfully. That comment was not in the jdk8u code but was in a part of the original change set that conflicted with the jdk8u code. So, i omitted to copy it in when I manually reconciled the code. I will restore it if you want. > Otherwise looks okay. Right, shall I push with those two corrections? Does jdk8u-shenandoah demand a jdk8u-fix-request/yes dance? Or can I just push? 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 hohensee at amazon.com Tue Aug 6 17:23:56 2019 From: hohensee at amazon.com (Hohensee, Paul) Date: Tue, 6 Aug 2019 17:23:56 +0000 Subject: [aarch64-port-dev ] [8u] RFR (M) 8228400: Remove built-in AArch64 simulator In-Reply-To: <3f0d2596-edfe-8e3c-ac82-78dd0b50319f@redhat.com> References: <3cc6a02b-8879-aade-d1b3-397ac22e89d8@redhat.com> <7fa88d76-20ba-8e01-d0a4-b7fbe3fb1ae0@redhat.com> <03a3080e-655f-67c2-24e0-1658113ee8b5@redhat.com> <36e8b083-53ba-51fc-98cd-1f342f4414f1@redhat.com> <4dd9405e-bb1b-3da7-fcf5-0facffa00ab8@redhat.com> <6a93050b-d201-fba7-b28a-61eb4a98d832@redhat.com> <27f0bfbc-4b22-347a-7c7b-58002a4c713d@redhat.com> <3f0d2596-edfe-8e3c-ac82-78dd0b50319f@redhat.com> Message-ID: You might do the push to jdk8u-dev in more than one step. It's zero risk to push cpu/aarch64, os_cpu/linux_aarch64, the equivalent agent directories, and platform-specific build files, so you could do that first. That's the vast majority of LOC. Next would be common build code changes, also low risk and (easily) testable. Finally would be changes to shared code. Thanks, Paul ?On 8/6/19, 8:30 AM, "aarch64-port-dev on behalf of Aleksey Shipilev" wrote: On 8/6/19 3:12 PM, Andrew Haley wrote: > On 8/6/19 1:33 PM, Aleksey Shipilev wrote: > >> I thought we wanted to merge the entirety if >> aarch64-port/jdk8u-shenandoah in one swoop. > > True. It might well be the easiest thing to do, but OTOH I'm not sure > it'll make for an easy review. > >> The webrev above is the difference between >> aarch64-port/jdk8u-shenandoah and jdk8u upstream. It is still not >> that close to something I would be comfortable to propose. > > Oh, I see; I didn't understand what you were trying to do. I thought > it was all part of the aarch64 backport, hence my bafflement. My goal is to make aarch64-port/jdk8u-shenandoah vs jdk8u difference as narrow as possible, before the heat of the actual review whenever we propose aarch64-port/jdk8u-shenandoah for inclusion to jdk8u. I usually invite everyone to look through those autogenerated webrevs and chip away differences one by one. When we were doing Shenandoah upstreaming, it was by far the sanest way to go about bulk contribution. (The alternative is juggling staging repositories and/or 100 KLOC webrevs, good luck with that.) There are a few minor Shenandoah 8u cleanups pending, and there is also the major ones (LRB and nofwdptr), which should trim out the significant part of it. None of this changes the processes we have already: everything Shenandoah-related comes with Shenandoah integrations, after Shenandoah testing :) -- Thanks, -Aleksey From shade at redhat.com Tue Aug 6 17:29:56 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Tue, 6 Aug 2019 19:29:56 +0200 Subject: [aarch64-port-dev ] Fwd: 8u-aarch64 : Backport 8163363: AArch64: Stack size in tools/launcher/Settings.java needs to be adjusted In-Reply-To: <22a4332b-be17-d0b8-2ee8-375662cc9696@redhat.com> References: <7449235e-a95b-ce5c-214e-3986940dfad4@redhat.com> <10d22723-ac38-06f0-0255-bc51a04727bb@redhat.com> <22a4332b-be17-d0b8-2ee8-375662cc9696@redhat.com> Message-ID: <176ef63c-543b-5ad7-10ba-9644554167d1@redhat.com> On 8/6/19 6:48 PM, Andrew Dinn wrote: > On 06/08/2019 17:35, Aleksey Shipilev wrote: >> On 8/6/19 10:49 AM, Andrew Dinn wrote: >>> The backport requires a minor tweak to the original patch as per the >>> following webrev: >>> >>> http://cr.openjdk.java.net/~adinn/8163363-jdk8u/webrev.00/ >> >> *) I don't understand, why "ppc64le" case was added? >> >> 78 if (getArch().equals("ppc64") || getArch().equals("ppc64le")) { > > That is because I back-ported the original patch and it was included in > that patch and went in automatically. Is ppc64le not a thing in jdk8u? > If so I can remove it. It is not in the 8u code, backport should not add it. >> *) Original change has this comment, are we ignoring it? >> >> // Check the stack size logs printed by -XshowSettings to verify -Xss meaningfully. > > That comment was not in the jdk8u code but was in a part of the original > change set that conflicted with the jdk8u code. So, i omitted to copy it > in when I manually reconciled the code. I will restore it if you want. I think we better backport the changeset exactly, i.e. with the comment. Please put it in. > Does jdk8u-shenandoah demand a jdk8u-fix-request/yes dance? Or can I > just push? jdk8u-shenandoah is outside JDK Updates process, you can push after this RFR is acked. -- Thanks, -Aleksey From gnu.andrew at redhat.com Wed Aug 7 04:26:35 2019 From: gnu.andrew at redhat.com (Andrew John Hughes) Date: Wed, 7 Aug 2019 05:26:35 +0100 Subject: [aarch64-port-dev ] [RFR] [8u] 8u232-b02 Upstream Sync Message-ID: <494520b8-1ad7-d200-9855-b05c35b51d5f@redhat.com> Webrevs: https://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/ Merge changesets: http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/corba/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/jaxp/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/jaxws/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/jdk/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/hotspot/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/langtools/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/nashorn/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/root/merge.changeset Changes in aarch64-shenandoah-jdk8u232-b02: - S8075546: Add tiered testing definitions to the langtools repo - S8202252: (aio) Closed AsynchronousSocketChannel keeps completion handler alive - S8216597: SIGBUS in Java_sun_security_pkcs11_wrapper_PKCS11_getNativeKeyInfo after JDK-6913047 - S8220513: Wrapper Key may get deleted when closing sessions in SunPKCS11 crypto provider - S8222737: [TESTBUG] Allow for tier 1 like testing in OpenJDK 8u - S8224580: Matcher can cause oop field/array element to be reloaded - S8226543: Reduce GC pressure during message digest calculations in password-based encryption Main issues of note: None diffstat for root b/.hgtags | 1 + b/Makefile | 4 +++- b/make/Main.gmk | 6 ++++++ b/test/Makefile | 49 +++++++++++++++++++++++++++++++++++++++++++++++-- 4 files changed, 57 insertions(+), 3 deletions(-) diffstat for corba b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for jaxp b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for jaxws b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for langtools b/.hgtags | 1 b/test/Makefile | 155 +++++++++++- b/test/ProblemList.txt | 26 ++ b/test/TEST.ROOT | 18 + b/test/TEST.groups | 32 ++ b/test/tools/javadoc/api/basic/GetTask_DocletClassTest.java | 1 6 files changed, 220 insertions(+), 13 deletions(-) diffstat for nashorn b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for jdk b/.hgtags | 1 b/src/share/classes/com/sun/crypto/provider/PBES1Core.java | 39 + b/src/share/classes/sun/security/pkcs11/P11Key.java | 205 ++++++--- b/src/share/native/sun/security/pkcs11/wrapper/p11_keymgmt.c | 32 - b/src/solaris/classes/sun/nio/ch/UnixAsynchronousSocketChannelImpl.java | 5 b/test/Makefile | 2 b/test/TEST.groups | 7 b/test/java/nio/channels/AsynchronousSocketChannel/CompletionHandlerRelease.java | 211 ++++++++++ 8 files changed, 397 insertions(+), 105 deletions(-) diffstat for hotspot b/.hgtags | 1 + b/src/share/vm/opto/matcher.cpp | 13 ++++++------- b/test/Makefile | 6 +++--- b/test/TEST.groups | 6 +++++- 4 files changed, 15 insertions(+), 11 deletions(-) Successfully built on x86, x86_64, s390, s390x, ppc, ppc64, ppc64le & aarch64. Ok to push? -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 https://keybase.io/gnu_andrew From ci_notify at linaro.org Wed Aug 7 06:16:37 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Wed, 7 Aug 2019 06:16:37 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 13 on AArch64 Message-ID: <1934636340.5251.1565158598284.JavaMail.jenkins@6e40b75d9e9e> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk13/openjdk-jtreg-nightly-tests/summary/2019/218/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/25 pass: 5,644; fail: 2; error: 1 Build 1: aarch64/2019/jun/27 pass: 5,645; fail: 2 Build 2: aarch64/2019/jun/29 pass: 5,644; fail: 3 Build 3: aarch64/2019/jul/02 pass: 5,645; fail: 2 Build 4: aarch64/2019/jul/04 pass: 5,644; fail: 2; error: 1 Build 5: aarch64/2019/jul/09 pass: 5,643; fail: 4 Build 6: aarch64/2019/jul/16 pass: 5,646; fail: 1 Build 7: aarch64/2019/jul/18 pass: 5,644; fail: 2; error: 1 Build 8: aarch64/2019/jul/20 pass: 5,645; fail: 1; error: 1 Build 9: aarch64/2019/jul/23 pass: 5,644; fail: 3 Build 10: aarch64/2019/jul/25 pass: 5,644; fail: 3 Build 11: aarch64/2019/jul/30 pass: 5,645; fail: 2 Build 12: aarch64/2019/aug/01 pass: 5,646; fail: 1 Build 13: aarch64/2019/aug/03 pass: 5,646; fail: 1 Build 14: aarch64/2019/aug/06 pass: 5,645; fail: 2 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/25 pass: 8,603; fail: 525; error: 18 Build 1: aarch64/2019/jun/27 pass: 8,609; fail: 512; error: 26 Build 2: aarch64/2019/jun/29 pass: 8,601; fail: 520; error: 29 Build 3: aarch64/2019/jul/02 pass: 8,604; fail: 521; error: 25 Build 4: aarch64/2019/jul/04 pass: 8,601; fail: 523; error: 26 Build 5: aarch64/2019/jul/09 pass: 8,606; fail: 515; error: 29 Build 6: aarch64/2019/jul/16 pass: 8,593; fail: 531; error: 30 Build 7: aarch64/2019/jul/18 pass: 8,618; fail: 527; error: 26 Build 8: aarch64/2019/jul/20 pass: 8,619; fail: 519; error: 33 Build 9: aarch64/2019/jul/23 pass: 8,616; fail: 525; error: 30 Build 10: aarch64/2019/jul/25 pass: 8,620; fail: 528; error: 23 Build 11: aarch64/2019/jul/30 pass: 8,610; fail: 529; error: 32 Build 12: aarch64/2019/aug/01 pass: 8,620; fail: 527; error: 24 Build 13: aarch64/2019/aug/03 pass: 8,596; fail: 552; error: 23 Build 14: aarch64/2019/aug/06 pass: 8,616; fail: 528; error: 27 7 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/25 pass: 3,962 Build 1: aarch64/2019/jun/27 pass: 3,962 Build 2: aarch64/2019/jun/29 pass: 3,962 Build 3: aarch64/2019/jul/02 pass: 3,962 Build 4: aarch64/2019/jul/04 pass: 3,962 Build 5: aarch64/2019/jul/09 pass: 3,962 Build 6: aarch64/2019/jul/16 pass: 3,963 Build 7: aarch64/2019/jul/18 pass: 3,964 Build 8: aarch64/2019/jul/20 pass: 3,964 Build 9: aarch64/2019/jul/23 pass: 3,964 Build 10: aarch64/2019/jul/25 pass: 3,964 Build 11: aarch64/2019/jul/30 pass: 3,964 Build 12: aarch64/2019/aug/01 pass: 3,964 Build 13: aarch64/2019/aug/03 pass: 3,964 Build 14: aarch64/2019/aug/06 pass: 3,964 Previous results can be found here: http://openjdk.linaro.org/jdk13/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.58x Relative performance: Server critical-jOPS (nc): 9.58x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk13/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 204.57 Server 204.57 / Server 2014-04-01 (71.00): 2.88x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk13/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-06-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/176/results/ 2019-06-28 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/178/results/ 2019-06-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/180/results/ 2019-07-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/183/results/ 2019-07-04 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/185/results/ 2019-07-10 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/190/results/ 2019-07-16 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/197/results/ 2019-07-19 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/199/results/ 2019-07-21 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/201/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/204/results/ 2019-07-26 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/211/results/ 2019-08-02 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/213/results/ 2019-08-04 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/215/results/ 2019-08-07 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/218/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/ From ci_notify at linaro.org Wed Aug 7 06:18:00 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Wed, 7 Aug 2019 06:18:00 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <411239328.5253.1565158680458.JavaMail.jenkins@6e40b75d9e9e> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/summary/2019/218/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/feb/28 pass: 803; fail: 9; error: 2 Build 1: aarch64/2019/mar/26 pass: 799; fail: 13; error: 2 Build 2: aarch64/2019/apr/09 pass: 807; fail: 9; error: 2 Build 3: aarch64/2019/apr/18 pass: 815; fail: 10 Build 4: aarch64/2019/apr/30 pass: 797; fail: 23; error: 9 Build 5: aarch64/2019/may/02 pass: 814; fail: 14; error: 2 Build 6: aarch64/2019/jun/15 pass: 815; fail: 22; error: 1 Build 7: aarch64/2019/jun/20 pass: 820; fail: 16; error: 2 Build 8: aarch64/2019/jun/29 pass: 807; fail: 25; error: 6 Build 9: aarch64/2019/jul/19 pass: 814; fail: 20; error: 4 Build 10: aarch64/2019/jul/25 pass: 802; fail: 25; error: 11 Build 11: aarch64/2019/jul/30 pass: 787; fail: 40; error: 11 Build 12: aarch64/2019/aug/01 pass: 800; fail: 26; error: 12 Build 13: aarch64/2019/aug/04 pass: 808; fail: 30; error: 2 Build 14: aarch64/2019/aug/06 pass: 799; fail: 29; error: 12 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/feb/28 pass: 5,749; fail: 268; error: 26 Build 1: aarch64/2019/mar/26 pass: 5,768; fail: 246; error: 29 Build 2: aarch64/2019/apr/09 pass: 5,763; fail: 267; error: 24 Build 3: aarch64/2019/apr/18 pass: 5,784; fail: 259; error: 25 Build 4: aarch64/2019/apr/30 pass: 5,779; fail: 262; error: 27 Build 5: aarch64/2019/may/02 pass: 5,784; fail: 262; error: 22 Build 6: aarch64/2019/jun/15 pass: 5,827; fail: 242; error: 22 Build 7: aarch64/2019/jun/20 pass: 5,821; fail: 244; error: 26 Build 8: aarch64/2019/jun/29 pass: 5,799; fail: 265; error: 27 Build 9: aarch64/2019/jul/19 pass: 5,940; fail: 278; error: 22 Build 10: aarch64/2019/jul/25 pass: 5,938; fail: 276; error: 26 Build 11: aarch64/2019/jul/30 pass: 5,942; fail: 273; error: 25 Build 12: aarch64/2019/aug/01 pass: 5,945; fail: 271; error: 24 Build 13: aarch64/2019/aug/04 pass: 5,949; fail: 270; error: 24 Build 14: aarch64/2019/aug/06 pass: 5,945; fail: 275; error: 23 ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/feb/28 pass: 3,114; fail: 2 Build 1: aarch64/2019/mar/26 pass: 3,114; fail: 2 Build 2: aarch64/2019/apr/09 pass: 3,115; fail: 2 Build 3: aarch64/2019/apr/18 pass: 3,115; fail: 2 Build 4: aarch64/2019/apr/30 pass: 3,115; fail: 2 Build 5: aarch64/2019/may/02 pass: 3,115; fail: 2 Build 6: aarch64/2019/jun/15 pass: 3,116; fail: 2 Build 7: aarch64/2019/jun/20 pass: 3,116; fail: 2 Build 8: aarch64/2019/jun/29 pass: 3,116; fail: 2 Build 9: aarch64/2019/jul/19 pass: 3,116; fail: 2 Build 10: aarch64/2019/jul/25 pass: 3,116; fail: 2 Build 11: aarch64/2019/jul/30 pass: 3,116; fail: 2 Build 12: aarch64/2019/aug/01 pass: 3,116; fail: 2 Build 13: aarch64/2019/aug/04 pass: 3,116; fail: 2 Build 14: aarch64/2019/aug/06 pass: 3,116; fail: 2 Previous results can be found here: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 6.57x Relative performance: Server critical-jOPS (nc): 7.93x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 172.13 Server 172.13 / Server 2014-04-01 (71.00): 2.42x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-02-28 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/059/results/ 2019-03-26 pass rate: 8490/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/085/results/ 2019-04-09 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/099/results/ 2019-04-19 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/108/results/ 2019-04-30 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/120/results/ 2019-05-02 pass rate: 8490/8490, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/122/results/ 2019-06-16 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/166/results/ 2019-06-21 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/171/results/ 2019-06-30 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/180/results/ 2019-07-20 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/200/results/ 2019-07-26 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/211/results/ 2019-08-02 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/213/results/ 2019-08-05 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/216/results/ 2019-08-07 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/218/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From shade at redhat.com Wed Aug 7 07:17:47 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Wed, 7 Aug 2019 09:17:47 +0200 Subject: [aarch64-port-dev ] [RFR] [8u] 8u232-b02 Upstream Sync In-Reply-To: <494520b8-1ad7-d200-9855-b05c35b51d5f@redhat.com> References: <494520b8-1ad7-d200-9855-b05c35b51d5f@redhat.com> Message-ID: <8c4a2c9a-ce25-0ffc-b1b2-d32aa47e5542@redhat.com> On 8/7/19 6:26 AM, Andrew John Hughes wrote: > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/corba/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/jaxp/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/jaxws/merge.changeset Looks trivially good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/jdk/merge.changeset Looks good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/hotspot/merge.changeset Looks good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/langtools/merge.changeset Looks good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/nashorn/merge.changeset Looks trivially good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/root/merge.changeset Looks good. Thumbs up! -- Thanks, -Aleksey From adinn at redhat.com Wed Aug 7 12:49:17 2019 From: adinn at redhat.com (Andrew Dinn) Date: Wed, 7 Aug 2019 13:49:17 +0100 Subject: [aarch64-port-dev ] Fwd: 8u-aarch64 : Backport 8163363: AArch64: Stack size in tools/launcher/Settings.java needs to be adjusted In-Reply-To: <176ef63c-543b-5ad7-10ba-9644554167d1@redhat.com> References: <7449235e-a95b-ce5c-214e-3986940dfad4@redhat.com> <10d22723-ac38-06f0-0255-bc51a04727bb@redhat.com> <22a4332b-be17-d0b8-2ee8-375662cc9696@redhat.com> <176ef63c-543b-5ad7-10ba-9644554167d1@redhat.com> Message-ID: On 06/08/2019 18:29, Aleksey Shipilev wrote: > On 8/6/19 6:48 PM, Andrew Dinn wrote: >> On 06/08/2019 17:35, Aleksey Shipilev wrote: >>> On 8/6/19 10:49 AM, Andrew Dinn wrote: >>>> The backport requires a minor tweak to the original patch as per the >>>> following webrev: >>>> >>>> http://cr.openjdk.java.net/~adinn/8163363-jdk8u/webrev.00/ >>> >>> *) I don't understand, why "ppc64le" case was added? >>> >>> 78 if (getArch().equals("ppc64") || getArch().equals("ppc64le")) { >> >> That is because I back-ported the original patch and it was included in >> that patch and went in automatically. Is ppc64le not a thing in jdk8u? >> If so I can remove it. > > It is not in the 8u code, backport should not add it. Ah, ok, I see what is wrong here. This is my cock-up. I updated the root tree (hg pull+update) rather than pulling all subtrees (run get_source.sh). So, I ended up applying and tweaking the patch against a stale checkout. The pp64cle check /is/ supposed to be present before and after patching (it is present in upstream jdk8u). Even with the latest tree the original patch still does not apply cleanly even after path demangling because of: 1) stack size arguments supplied as strings not numbers 2) different local Strings used in comparison checks. So, I corrected for both of these differences. Here is a second webrev as a sanity check (it includes the omitted comment): http://cr.openjdk.java.net/~adinn/8163363-jdk8u/webrev.01/ Testing: 'make test core_tools' passes ok with this new version. 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 shade at redhat.com Wed Aug 7 12:56:17 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Wed, 7 Aug 2019 14:56:17 +0200 Subject: [aarch64-port-dev ] Fwd: 8u-aarch64 : Backport 8163363: AArch64: Stack size in tools/launcher/Settings.java needs to be adjusted In-Reply-To: References: <7449235e-a95b-ce5c-214e-3986940dfad4@redhat.com> <10d22723-ac38-06f0-0255-bc51a04727bb@redhat.com> <22a4332b-be17-d0b8-2ee8-375662cc9696@redhat.com> <176ef63c-543b-5ad7-10ba-9644554167d1@redhat.com> Message-ID: <665cbbc7-a650-4976-a21a-29762b26975d@redhat.com> On 8/7/19 2:49 PM, Andrew Dinn wrote: > http://cr.openjdk.java.net/~adinn/8163363-jdk8u/webrev.01/ Looks good! -- Thanks, -Aleksey From shade at redhat.com Wed Aug 7 12:59:09 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Wed, 7 Aug 2019 14:59:09 +0200 Subject: [aarch64-port-dev ] RFR/RFC 8219011: Implement MacroAssembler::warn method on AArch64 Message-ID: RFE: https://bugs.openjdk.java.net/browse/JDK-8219011 It seems odd to keep MacroAssembler::warn declared, but not defined. We have rectified this in every release, except 8u-aarch64. We can instead remove MacroAssembler::warn declaration, but that would deviate from both 8u upstream and every other release too. This is 8u-aarch64 backport for aarch64-port/jdk8u-shenandoah: diff -r eaf9b36b7a30 src/cpu/aarch64/vm/macroAssembler_aarch64.cpp --- a/src/cpu/aarch64/vm/macroAssembler_aarch64.cpp Tue Aug 06 10:45:43 2019 +0200 +++ b/src/cpu/aarch64/vm/macroAssembler_aarch64.cpp Wed Aug 07 14:57:04 2019 +0200 @@ -2009,4 +2009,12 @@ } +void MacroAssembler::warn(const char* msg) { + pusha(); + mov(c_rarg0, (address)msg); + mov(lr, CAST_FROM_FN_PTR(address, warning)); + blr(lr); + popa(); +} + // If a constant does not fit in an immediate field, generate some // number of MOV instructions and then perform the operation. Testing: aarch64 build -- Thanks, -Aleksey From adinn at redhat.com Wed Aug 7 14:32:07 2019 From: adinn at redhat.com (adinn at redhat.com) Date: Wed, 07 Aug 2019 14:32:07 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jdk: 8163363: AArch64: Stack size in tools/launcher/Settings.java needs to be adjusted Message-ID: <201908071432.x77EW7JG021808@aojmv0008.oracle.com> Changeset: aa716af1da26 Author: qpzhang Date: 2019-08-07 11:08 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/aa716af1da26 8163363: AArch64: Stack size in tools/launcher/Settings.java needs to be adjusted Summary: Specify a proper min stack size input to -Xss for aarch64 Reviewed-by: aph ! test/tools/launcher/Settings.java From shade at redhat.com Wed Aug 7 15:16:27 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Wed, 7 Aug 2019 17:16:27 +0200 Subject: [aarch64-port-dev ] [11u] RFR 8228400: Remove built-in AArch64 simulator In-Reply-To: <52cc6d46-3bfd-edda-bb7e-c2b59aa36d72@redhat.com> References: <5e246f51-4cb9-03a2-d4f2-bf0f7bf440f6@redhat.com> <390b1088-6194-bcd8-a1c5-d8cf07a65fd8@redhat.com> <741a213c-2745-d242-d2bb-367d28f04cd3@redhat.com> <5b5c30a1-e6d8-3e6d-7209-dded08d95307@redhat.com> <82829029-facf-3d9e-cee4-ca35a6d151f7@redhat.com> <52cc6d46-3bfd-edda-bb7e-c2b59aa36d72@redhat.com> Message-ID: On 8/1/19 7:54 PM, Andrew Haley wrote: >> Anyway, I have formally requested the backport of JDK-8228400 with >> jdk11u-fix-request. If you still feel it should not be in 11u, >> please formally reject it with jdk11u-fix-no. I would then give up >> here, and move on backporting this removal to 8u-aarch64. > > I'll think some more. I can see both sides of this, and I guess the > builtin sim is a special case. I am certainly not going to treat this > as a precedent for future cleanups. Right. 8u-aarch64 and 14 have the simulator removed at this point. Have you decided what would you like to do with 11u? There is one little cleanup that follows this removal: https://bugs.openjdk.java.net/browse/JDK-8228725 (it could have been in this change, but alas) -- Thanks, -Aleksey From aph at redhat.com Wed Aug 7 15:54:39 2019 From: aph at redhat.com (Andrew Haley) Date: Wed, 7 Aug 2019 16:54:39 +0100 Subject: [aarch64-port-dev ] RFR/RFC 8219011: Implement MacroAssembler::warn method on AArch64 In-Reply-To: References: Message-ID: On 8/7/19 1:59 PM, Aleksey Shipilev wrote: > RFE: > https://bugs.openjdk.java.net/browse/JDK-8219011 > > It seems odd to keep MacroAssembler::warn declared, but not defined. We have rectified this in every > release, except 8u-aarch64. We can instead remove MacroAssembler::warn declaration, but that would > deviate from both 8u upstream and every other release too. This is 8u-aarch64 backport for > aarch64-port/jdk8u-shenandoah: OK. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From shade at redhat.com Wed Aug 7 16:04:46 2019 From: shade at redhat.com (shade at redhat.com) Date: Wed, 07 Aug 2019 16:04:46 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 8219011: Implement MacroAssembler::warn method on AArch64 Message-ID: <201908071604.x77G4kj5021284@aojmv0008.oracle.com> Changeset: 748d79c6233f Author: mbalao Date: 2019-02-15 11:46 -0300 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/748d79c6233f 8219011: Implement MacroAssembler::warn method on AArch64 Reviewed-by: adinn ! src/cpu/aarch64/vm/macroAssembler_aarch64.cpp From shade at redhat.com Wed Aug 7 16:05:33 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Wed, 7 Aug 2019 18:05:33 +0200 Subject: [aarch64-port-dev ] RFR/RFC 8219011: Implement MacroAssembler::warn method on AArch64 In-Reply-To: References: Message-ID: <2805a97c-c328-bc70-af3d-6f5985facbdf@redhat.com> On 8/7/19 5:54 PM, Andrew Haley wrote: > On 8/7/19 1:59 PM, Aleksey Shipilev wrote: >> RFE: >> https://bugs.openjdk.java.net/browse/JDK-8219011 >> >> It seems odd to keep MacroAssembler::warn declared, but not defined. We have rectified this in every >> release, except 8u-aarch64. We can instead remove MacroAssembler::warn declaration, but that would >> deviate from both 8u upstream and every other release too. This is 8u-aarch64 backport for >> aarch64-port/jdk8u-shenandoah: > > OK. Thanks, pushed. -- Thanks, -Aleksey From aph at redhat.com Wed Aug 7 16:46:10 2019 From: aph at redhat.com (Andrew Haley) Date: Wed, 7 Aug 2019 17:46:10 +0100 Subject: [aarch64-port-dev ] [11u] RFR 8228400: Remove built-in AArch64 simulator In-Reply-To: References: <5e246f51-4cb9-03a2-d4f2-bf0f7bf440f6@redhat.com> <390b1088-6194-bcd8-a1c5-d8cf07a65fd8@redhat.com> <741a213c-2745-d242-d2bb-367d28f04cd3@redhat.com> <5b5c30a1-e6d8-3e6d-7209-dded08d95307@redhat.com> <82829029-facf-3d9e-cee4-ca35a6d151f7@redhat.com> <52cc6d46-3bfd-edda-bb7e-c2b59aa36d72@redhat.com> Message-ID: On 8/7/19 4:16 PM, Aleksey Shipilev wrote: > 8u-aarch64 and 14 have the simulator removed at this point. > Have you decided what would you like to do with 11u? It must be the same as 8u: take it out. Thanks. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Thu Aug 8 00:13:29 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Thu, 8 Aug 2019 00:13:29 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <1345282616.6373.1565223210409.JavaMail.jenkins@6e40b75d9e9e> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2019/219/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/05 pass: 5,653; fail: 3 Build 1: aarch64/2019/jul/09 pass: 5,695; fail: 3 Build 2: aarch64/2019/jul/11 pass: 5,696; fail: 3 Build 3: aarch64/2019/jul/12 pass: 5,695; fail: 5 Build 4: aarch64/2019/jul/15 pass: 5,699; fail: 1 Build 5: aarch64/2019/jul/17 pass: 5,700; fail: 1; error: 1 Build 6: aarch64/2019/jul/19 pass: 5,699; fail: 3; error: 1 Build 7: aarch64/2019/jul/22 pass: 5,705; fail: 2 Build 8: aarch64/2019/jul/24 pass: 5,706; fail: 1 Build 9: aarch64/2019/jul/26 pass: 5,707; fail: 2 Build 10: aarch64/2019/jul/29 pass: 5,705; fail: 4 Build 11: aarch64/2019/jul/31 pass: 5,711; fail: 1 Build 12: aarch64/2019/aug/02 pass: 5,711; fail: 2 Build 13: aarch64/2019/aug/05 pass: 5,712; fail: 1 Build 14: aarch64/2019/aug/07 pass: 5,711; fail: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/05 pass: 8,612; fail: 515; error: 28 Build 1: aarch64/2019/jul/09 pass: 8,604; fail: 532; error: 19 Build 2: aarch64/2019/jul/11 pass: 8,598; fail: 529; error: 31 Build 3: aarch64/2019/jul/12 pass: 8,601; fail: 528; error: 29 Build 4: aarch64/2019/jul/15 pass: 8,602; fail: 533; error: 25 Build 5: aarch64/2019/jul/17 pass: 8,614; fail: 522; error: 24 Build 6: aarch64/2019/jul/19 pass: 8,611; fail: 526; error: 26 Build 7: aarch64/2019/jul/22 pass: 8,628; fail: 511; error: 24 Build 8: aarch64/2019/jul/24 pass: 8,617; fail: 538; error: 26 Build 9: aarch64/2019/jul/26 pass: 8,649; fail: 518; error: 17 Build 10: aarch64/2019/jul/29 pass: 8,640; fail: 520; error: 26 Build 11: aarch64/2019/jul/31 pass: 8,640; fail: 526; error: 24 Build 12: aarch64/2019/aug/02 pass: 8,637; fail: 524; error: 29 Build 13: aarch64/2019/aug/05 pass: 8,642; fail: 519; error: 29 Build 14: aarch64/2019/aug/07 pass: 8,638; fail: 529; error: 23 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/05 pass: 3,965 Build 1: aarch64/2019/jul/09 pass: 3,967 Build 2: aarch64/2019/jul/11 pass: 3,968 Build 3: aarch64/2019/jul/12 pass: 3,968 Build 4: aarch64/2019/jul/15 pass: 3,968 Build 5: aarch64/2019/jul/17 pass: 3,968 Build 6: aarch64/2019/jul/19 pass: 3,969 Build 7: aarch64/2019/jul/22 pass: 3,969 Build 8: aarch64/2019/jul/24 pass: 3,970 Build 9: aarch64/2019/jul/26 pass: 3,970 Build 10: aarch64/2019/jul/29 pass: 3,970 Build 11: aarch64/2019/jul/31 pass: 3,970 Build 12: aarch64/2019/aug/02 pass: 3,970 Build 13: aarch64/2019/aug/05 pass: 3,970 Build 14: aarch64/2019/aug/07 pass: 3,970 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.68x Relative performance: Server critical-jOPS (nc): 9.60x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 213.86 Server 213.86 / Server 2014-04-01 (71.00): 3.01x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-01-01 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/365/results/ 2019-07-05 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/186/results/ 2019-07-10 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/190/results/ 2019-07-12 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/192/results/ 2019-07-15 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/196/results/ 2019-07-17 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/198/results/ 2019-07-20 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/200/results/ 2019-07-22 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/203/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/205/results/ 2019-07-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/207/results/ 2019-07-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/210/results/ 2019-08-01 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/212/results/ 2019-08-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/214/results/ 2019-08-06 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/217/results/ 2019-08-08 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/219/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From patrick at os.amperecomputing.com Thu Aug 8 06:15:18 2019 From: patrick at os.amperecomputing.com (Patrick Zhang OS) Date: Thu, 8 Aug 2019 06:15:18 +0000 Subject: [aarch64-port-dev ] Adv. SIMD/Neon support in intrinsics/stubs for AArch64 Message-ID: Hi Does anyone know the whole picture of the Neon support in intrinsics/stubs? I am not sure whether what I observed is correct: 1. Pre-Armv8 distinguishes between VFP and Neon floating-point support but the definitions are not explicitly separated (via any special prefix) in assembly_aarch64.hpp. 2. There are some intrinsics/stubs implemented using VFP for vectorizing, where we still have opportunities to improve by aid of Neon 2x64-bit integer/floating-point operations, such as string_compare [1]. 3. More intrinsics need vectorizing, with reference to other archs. Thanks for any comments, with regards to current situation and/or future plans. [1] http://hg.openjdk.java.net/jdk/jdk/file/cafd691c6c04/src/hotspot/cpu/aarch64/stubGenerator_aarch64.cpp#l3982 Regards Patrick From aph at redhat.com Thu Aug 8 08:18:23 2019 From: aph at redhat.com (Andrew Haley) Date: Thu, 8 Aug 2019 09:18:23 +0100 Subject: [aarch64-port-dev ] Adv. SIMD/Neon support in intrinsics/stubs for AArch64 In-Reply-To: References: Message-ID: <2b7429dc-cd58-4930-da74-49a40fb5f42f@redhat.com> On 8/8/19 7:15 AM, Patrick Zhang OS wrote: > Does anyone know the whole picture of the Neon support in intrinsics/stubs? I'm as likely to know as anyone else. > I am not sure whether what I observed is correct: 1. Pre-Armv8 > distinguishes between VFP and Neon floating-point support but the > definitions are not explicitly separated (via any special prefix) in > assembly_aarch64.hpp. With AArch64 there's no need: AdvSIMD is part of the spec. > 2. There are some intrinsics/stubs implemented using VFP for > vectorizing, where we still have opportunities to improve by aid of > Neon 2x64-bit integer/floating-point operations, such as > string_compare [1]. How would that help anything? string_compare already uses vector ops. > 3. More intrinsics need vectorizing, with reference to other archs. Maybe. In theory it would help, but in practice meaningful speedups are quite difficult to achieve without compromising performance with small strings. But please feel free to try. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From nick.gasson at arm.com Thu Aug 8 09:32:03 2019 From: nick.gasson at arm.com (Nick Gasson) Date: Thu, 8 Aug 2019 17:32:03 +0800 Subject: [aarch64-port-dev ] RFR: 8229118: [TESTBUG] serviceability/sa/ClhsdbFindPC fails on AArch64 Message-ID: <4a646485-4230-9632-dfd4-4368d79ba4cd@arm.com> Hi, Bug: https://bugs.openjdk.java.net/browse/JDK-8229118 Webrev: http://cr.openjdk.java.net/~ngasson/8229118/webrev.0/ This test starts a sub-process with -Xcomp and then uses the SA to get a stack trace of it. It expects to see this line: In code in NMethod for jdk/test/lib/apps/LingeredApp.main But actually on AArch64 the stack trace looks like this: - java.lang.Thread.sleep(long) @bci=0, pc=0x0000ffff74603d08, Method*=0x0000ffff031baf98 (Compiled frame; information may be imprecise) - jdk.test.lib.apps.LingeredApp.main(java.lang.String[]) @bci=53, line=502, pc=0x0000ffff6c9276e0, Method*=0x0000ffff03611d48 (Interpreted frame) The main method is interpreted even though we're running with -Xcomp. That's because it is deoptimized almost immediately, because main calls some methods on java.nio.file.Paths, but that class hasn't been loaded when main is compiled. X86 can patch in the address of the method on-the-fly, but AArch64 can't do this because of restrictions on which instructions can be legally rewritten. This patch lifts the code that uses the java.nio classes out of LingeredApp::main into a separate static method. LingeredApp.main now only uses classes that are loaded very early in boot, before main is compiled. The stack trace now looks like: "main" #1 prio=5 tid=0x0000ffffb4022800 nid=0xd610 waiting on condition [0x0000ffffbb755000] java.lang.Thread.State: TIMED_WAITING (sleeping) JavaThread state: _thread_blocked - java.lang.Thread.sleep(long) @bci=0, pc=0x0000fffface414c8, Method*=0x0000ffff3dac8a28 (Compiled frame; information may be imprecise) - jdk.test.lib.apps.LingeredApp.pollLockFile(java.lang.String) @bci=30, line=499, pc=0x0000ffffa50818e0, Method*=0x0000ffff3c122cf0 (Interpreted frame) - jdk.test.lib.apps.LingeredApp.main(java.lang.String[]) @bci=25, line=529, pc=0x0000ffffa59afd58, Method*=0x0000ffff3c122de0 (Compiled frame) I.e. pollLockFile was deoptimized to an interpreted frame but LingeredApp.main is still a compiled frame which is what ClhsdbFindPC is looking for. This solution does seem a bit hacky, so if it's not acceptable an alternative is to just skip the -Xcomp part of the test on AArch64. Ran a full jtreg test on AArch64/x86 to check for regressions. Thanks, Nick From adinn at redhat.com Thu Aug 8 10:16:40 2019 From: adinn at redhat.com (Andrew Dinn) Date: Thu, 8 Aug 2019 11:16:40 +0100 Subject: [aarch64-port-dev ] RFR: 8229118: [TESTBUG] serviceability/sa/ClhsdbFindPC fails on AArch64 In-Reply-To: <4a646485-4230-9632-dfd4-4368d79ba4cd@arm.com> References: <4a646485-4230-9632-dfd4-4368d79ba4cd@arm.com> Message-ID: <39f8fd3f-fcce-0200-3922-33405978e297@redhat.com> Hi Nick, On 08/08/2019 10:32, Nick Gasson wrote: > Bug: https://bugs.openjdk.java.net/browse/JDK-8229118 > Webrev: http://cr.openjdk.java.net/~ngasson/8229118/webrev.0/ > > This test starts a sub-process with -Xcomp and then uses the SA to get a > stack trace of it. It expects to see this line: > > In code in NMethod for jdk/test/lib/apps/LingeredApp.main > > But actually on AArch64 the stack trace looks like this: > > - java.lang.Thread.sleep(long) @bci=0, pc=0x0000ffff74603d08, Method*=0x0000ffff031baf98 (Compiled frame; information may be imprecise) > - jdk.test.lib.apps.LingeredApp.main(java.lang.String[]) @bci=53, line=502, pc=0x0000ffff6c9276e0, Method*=0x0000ffff03611d48 (Interpreted frame) > > The main method is interpreted even though we're running with > -Xcomp. That's because it is deoptimized almost immediately, because > main calls some methods on java.nio.file.Paths, but that class hasn't > been loaded when main is compiled. > > X86 can patch in the address of the method on-the-fly, but AArch64 can't > do this because of restrictions on which instructions can be legally > rewritten. > > This patch lifts the code that uses the java.nio classes out of > LingeredApp::main into a separate static method. LingeredApp.main now > only uses classes that are loaded very early in boot, before main is > compiled. The stack trace now looks like: > > "main" #1 prio=5 tid=0x0000ffffb4022800 nid=0xd610 waiting on condition [0x0000ffffbb755000] > java.lang.Thread.State: TIMED_WAITING (sleeping) > JavaThread state: _thread_blocked > - java.lang.Thread.sleep(long) @bci=0, pc=0x0000fffface414c8, Method*=0x0000ffff3dac8a28 (Compiled frame; information may be imprecise) > - jdk.test.lib.apps.LingeredApp.pollLockFile(java.lang.String) @bci=30, line=499, pc=0x0000ffffa50818e0, Method*=0x0000ffff3c122cf0 (Interpreted frame) > - jdk.test.lib.apps.LingeredApp.main(java.lang.String[]) @bci=25, line=529, pc=0x0000ffffa59afd58, Method*=0x0000ffff3c122de0 (Compiled frame) > > I.e. pollLockFile was deoptimized to an interpreted frame but > LingeredApp.main is still a compiled frame which is what ClhsdbFindPC is > looking for. > > This solution does seem a bit hacky, so if it's not acceptable an > alternative is to just skip the -Xcomp part of the test on AArch64. > > Ran a full jtreg test on AArch64/x86 to check for regressions. Yuck! That's a nice hack to avoid the indeterminate effect of -Xcomp. However, my gut feeling is still that relying on -Xcomp in tests is just a /really/ bad idea and I'd prefer to omit it but . . . I'm not 100% clear what the point of this test is but it looks like it is meant to exercise the stack backtrace code when there is a compiled method on the stack. If so then I guess your hack fits the bill while removing the -Xcomp flag from the command line would not fulfil the test's remit. If that is the point of the test then I agree, reluctantly, that your hack is the right solution. On those grounds I'm happy to accept the patch. However, I'd prefer someone else (Andrew Haley?) also to review this before it gets pushed. 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 Thu Aug 8 10:37:05 2019 From: aph at redhat.com (Andrew Haley) Date: Thu, 8 Aug 2019 11:37:05 +0100 Subject: [aarch64-port-dev ] RFR: 8229118: [TESTBUG] serviceability/sa/ClhsdbFindPC fails on AArch64 In-Reply-To: <39f8fd3f-fcce-0200-3922-33405978e297@redhat.com> References: <4a646485-4230-9632-dfd4-4368d79ba4cd@arm.com> <39f8fd3f-fcce-0200-3922-33405978e297@redhat.com> Message-ID: On 8/8/19 11:16 AM, Andrew Dinn wrote: > I'm not 100% clear what the point of this test is but it looks like it > is meant to exercise the stack backtrace code when there is a compiled > method on the stack. If so then I guess your hack fits the bill while > removing the -Xcomp flag from the command line would not fulfil the > test's remit. If that is the point of the test then I agree, > reluctantly, that your hack is the right solution. On those grounds I'm > happy to accept the patch. However, I'd prefer someone else (Andrew > Haley?) also to review this before it gets pushed. Eww. I suppose that -Xcomp often always fails on AArch64 because we deoptimize so readily. Given that the test is not supposed to be testing -Xcomp but SA I guess the test is OK, but it's very fragile. It does mean that any tests which depend on -Xcomp don't really work on AArch64. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From patrick at os.amperecomputing.com Thu Aug 8 11:27:32 2019 From: patrick at os.amperecomputing.com (Patrick Zhang OS) Date: Thu, 8 Aug 2019 11:27:32 +0000 Subject: [aarch64-port-dev ] Adv. SIMD/Neon support in intrinsics/stubs for AArch64 In-Reply-To: <2b7429dc-cd58-4930-da74-49a40fb5f42f@redhat.com> References: <2b7429dc-cd58-4930-da74-49a40fb5f42f@redhat.com> Message-ID: > How would that help anything? string_compare already uses vector ops. Hmm..well. I might have thought it for granted that UMOV should be used instead of FMOV, shortly after found a piece of comment in Arm Arch ref manual [1]: >> Some of the Floating-point move (register) instructions overlap with the functionality provided by the Advanced >> SIMD instructions DUP, INS, and UMOV. However, ARM recommends using the FMOV instructions when operating on >> scalar floating-point data to avoid the creation of scalar floating-point code that depends on the availability of the >> Advanced SIMD instruction set. And in another relevant doc for A75 [2], it says FMOV's execution latency and throughput can be the better choice. [1] https://developer.arm.com/docs/ddi0487/latest/arm-architecture-reference-manual-armv8-for-armv8-a-architecture-profile, p228 [2] https://static.docs.arm.com/101398/0200/arm_cortex_a75_software_optimization_guide_v2.pdf, p11 Regards Patrick -----Original Message----- From: Andrew Haley Sent: Thursday, August 8, 2019 4:18 PM To: Patrick Zhang OS ; aarch64-port-dev at openjdk.java.net Subject: Re: [aarch64-port-dev ] Adv. SIMD/Neon support in intrinsics/stubs for AArch64 On 8/8/19 7:15 AM, Patrick Zhang OS wrote: > Does anyone know the whole picture of the Neon support in intrinsics/stubs? I'm as likely to know as anyone else. > I am not sure whether what I observed is correct: 1. Pre-Armv8 > distinguishes between VFP and Neon floating-point support but the > definitions are not explicitly separated (via any special prefix) in > assembly_aarch64.hpp. With AArch64 there's no need: AdvSIMD is part of the spec. > 2. There are some intrinsics/stubs implemented using VFP for > vectorizing, where we still have opportunities to improve by aid of > Neon 2x64-bit integer/floating-point operations, such as > string_compare [1]. How would that help anything? string_compare already uses vector ops. > 3. More intrinsics need vectorizing, with reference to other archs. Maybe. In theory it would help, but in practice meaningful speedups are quite difficult to achieve without compromising performance with small strings. But please feel free to try. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From adinn at redhat.com Thu Aug 8 15:19:21 2019 From: adinn at redhat.com (Andrew Dinn) Date: Thu, 8 Aug 2019 16:19:21 +0100 Subject: [aarch64-port-dev ] RFR: [11u] JDK-8205421: AARCH64: StubCodeMark should be placed after alignment Message-ID: <5210a43f-899d-97e2-3f1f-4c3dbdfeca5d@redhat.com> Could I please have a review of this backport for JDK-8205421 which required a few minor changes to the original patch Upstream JIRA: https://bugs.openjdk.java.net/browse/JDK-8205421 Upstream patch: http://hg.openjdk.java.net/jdk/jdk/rev/2e4903f83295 Backport webrev: http://cr.openjdk.java.net/~adinn/8205421/webrev.00/ Testing: tier1 passes -- modulo unrelated failures with SA debugger and varhandle weakCompareAndSet 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 shade at redhat.com Thu Aug 8 15:41:42 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Thu, 8 Aug 2019 17:41:42 +0200 Subject: [aarch64-port-dev ] RFR: [11u] JDK-8205421: AARCH64: StubCodeMark should be placed after alignment In-Reply-To: <5210a43f-899d-97e2-3f1f-4c3dbdfeca5d@redhat.com> References: <5210a43f-899d-97e2-3f1f-4c3dbdfeca5d@redhat.com> Message-ID: <45560921-b6aa-146d-12d1-9ca43da0669e@redhat.com> On 8/8/19 5:19 PM, Andrew Dinn wrote: > Could I please have a review of this backport for JDK-8205421 which > required a few minor changes to the original patch > > Upstream JIRA: https://bugs.openjdk.java.net/browse/JDK-8205421 > Upstream patch: http://hg.openjdk.java.net/jdk/jdk/rev/2e4903f83295 > Backport webrev: http://cr.openjdk.java.net/~adinn/8205421/webrev.00/ Backport looks good to me. I assume the patch did not apply due to context differences? Thanks, -Aleksey From adinn at redhat.com Thu Aug 8 15:55:37 2019 From: adinn at redhat.com (Andrew Dinn) Date: Thu, 8 Aug 2019 16:55:37 +0100 Subject: [aarch64-port-dev ] RFR: [11u] JDK-8205421: AARCH64: StubCodeMark should be placed after alignment In-Reply-To: <45560921-b6aa-146d-12d1-9ca43da0669e@redhat.com> References: <5210a43f-899d-97e2-3f1f-4c3dbdfeca5d@redhat.com> <45560921-b6aa-146d-12d1-9ca43da0669e@redhat.com> Message-ID: On 08/08/2019 16:41, Aleksey Shipilev wrote: > On 8/8/19 5:19 PM, Andrew Dinn wrote: >> Could I please have a review of this backport for JDK-8205421 which >> required a few minor changes to the original patch >> >> Upstream JIRA: https://bugs.openjdk.java.net/browse/JDK-8205421 >> Upstream patch: http://hg.openjdk.java.net/jdk/jdk/rev/2e4903f83295 >> Backport webrev: http://cr.openjdk.java.net/~adinn/8205421/webrev.00/ > > Backport looks good to me. I assume the patch did not apply due to context differences? Exactly. 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 Aug 9 00:05:01 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 09 Aug 2019 00:05:01 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah: 4 new changesets Message-ID: <201908090005.x79052Er026832@aojmv0008.oracle.com> Changeset: ef851705e3e1 Author: sgehwolf Date: 2019-04-25 14:01 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/ef851705e3e1 8222737: [TESTBUG] Allow for tier 1 like testing in OpenJDK 8u Reviewed-by: shade, adinn, andrew ! Makefile ! make/Main.gmk ! test/Makefile Changeset: c5ca527b0afd Author: andrew Date: 2019-08-01 03:43 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/c5ca527b0afd Added tag jdk8u232-b02 for changeset ef851705e3e1 ! .hgtags Changeset: 3f7302a81ad2 Author: andrew Date: 2019-08-02 17:05 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/3f7302a81ad2 Merge jdk8u232-b02 ! .hgtags Changeset: 1e8f9293313d Author: andrew Date: 2019-08-02 17:26 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/1e8f9293313d Added tag aarch64-shenandoah-jdk8u232-b02 for changeset 3f7302a81ad2 ! .hgtags From gnu.andrew at redhat.com Fri Aug 9 00:05:12 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 09 Aug 2019 00:05:12 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/corba: 3 new changesets Message-ID: <201908090005.x7905Ct0027017@aojmv0008.oracle.com> Changeset: 8ce5d3e4f0b4 Author: andrew Date: 2019-08-01 03:43 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/8ce5d3e4f0b4 Added tag jdk8u232-b02 for changeset 63cfd6362001 ! .hgtags Changeset: e9baa1f9739f Author: andrew Date: 2019-08-02 17:05 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/e9baa1f9739f Merge jdk8u232-b02 ! .hgtags Changeset: 007f08f0cd76 Author: andrew Date: 2019-08-02 17:26 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/007f08f0cd76 Added tag aarch64-shenandoah-jdk8u232-b02 for changeset e9baa1f9739f ! .hgtags From gnu.andrew at redhat.com Fri Aug 9 00:05:19 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 09 Aug 2019 00:05:19 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxp: 3 new changesets Message-ID: <201908090005.x7905Jqw027159@aojmv0008.oracle.com> Changeset: 271cd29281ff Author: andrew Date: 2019-08-01 03:43 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/271cd29281ff Added tag jdk8u232-b02 for changeset ff1df33b41f4 ! .hgtags Changeset: 21f96212d710 Author: andrew Date: 2019-08-02 17:05 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/21f96212d710 Merge jdk8u232-b02 ! .hgtags Changeset: 628324ef8101 Author: andrew Date: 2019-08-02 17:26 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/628324ef8101 Added tag aarch64-shenandoah-jdk8u232-b02 for changeset 21f96212d710 ! .hgtags From gnu.andrew at redhat.com Fri Aug 9 00:05:34 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 09 Aug 2019 00:05:34 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/langtools: 5 new changesets Message-ID: <201908090005.x7905Y1J027341@aojmv0008.oracle.com> Changeset: 45746e46893b Author: darcy Date: 2015-06-01 15:19 -0700 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/45746e46893b 8075546: Add tiered testing definitions to the langtools repo Reviewed-by: jjg + test/ProblemList.txt ! test/TEST.ROOT + test/TEST.groups ! test/tools/javadoc/api/basic/GetTask_DocletClassTest.java Changeset: 19908109cb37 Author: sgehwolf Date: 2019-04-25 14:03 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/19908109cb37 8222737: [TESTBUG] Allow for tier 1 like testing in OpenJDK 8u Reviewed-by: adinn, shade, andrew ! test/Makefile ! test/TEST.groups Changeset: 671c4ba50c6f Author: andrew Date: 2019-08-01 03:44 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/671c4ba50c6f Added tag jdk8u232-b02 for changeset 19908109cb37 ! .hgtags Changeset: 195fc04b5fae Author: andrew Date: 2019-08-02 17:05 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/195fc04b5fae Merge jdk8u232-b02 ! .hgtags Changeset: f5f6b34c3861 Author: andrew Date: 2019-08-02 17:26 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/f5f6b34c3861 Added tag aarch64-shenandoah-jdk8u232-b02 for changeset 195fc04b5fae ! .hgtags From gnu.andrew at redhat.com Fri Aug 9 00:05:26 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 09 Aug 2019 00:05:26 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxws: 3 new changesets Message-ID: <201908090005.x7905QTP027249@aojmv0008.oracle.com> Changeset: 28c25aedce28 Author: andrew Date: 2019-08-01 03:44 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/28c25aedce28 Added tag jdk8u232-b02 for changeset dc445b545ab7 ! .hgtags Changeset: b055aaad541e Author: andrew Date: 2019-08-02 17:05 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/b055aaad541e Merge jdk8u232-b02 ! .hgtags Changeset: 283ce65917ef Author: andrew Date: 2019-08-02 17:26 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/283ce65917ef Added tag aarch64-shenandoah-jdk8u232-b02 for changeset b055aaad541e ! .hgtags From gnu.andrew at redhat.com Fri Aug 9 00:05:56 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 09 Aug 2019 00:05:56 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/nashorn: 3 new changesets Message-ID: <201908090005.x7905uBl028273@aojmv0008.oracle.com> Changeset: 7979e4a31f24 Author: andrew Date: 2019-08-01 03:44 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/7979e4a31f24 Added tag jdk8u232-b02 for changeset 908754951075 ! .hgtags Changeset: a9ff7eb50b4c Author: andrew Date: 2019-08-02 17:05 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/a9ff7eb50b4c Merge jdk8u232-b02 ! .hgtags Changeset: 3330c82ce541 Author: andrew Date: 2019-08-02 17:26 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/3330c82ce541 Added tag aarch64-shenandoah-jdk8u232-b02 for changeset a9ff7eb50b4c ! .hgtags From patrick at os.amperecomputing.com Fri Aug 9 09:45:35 2019 From: patrick at os.amperecomputing.com (Patrick Zhang OS) Date: Fri, 9 Aug 2019 09:45:35 +0000 Subject: [aarch64-port-dev ] Adv. SIMD/Neon support in intrinsics/stubs for AArch64 In-Reply-To: References: <2b7429dc-cd58-4930-da74-49a40fb5f42f@redhat.com> Message-ID: I found a couple of recent major intrinsifying work recorded in JEP 315: Improve Aarch64 Intrinsics [1][2], and some additional tasks are also marked as "relates to" within. By the way, per my JMH tests on Ampere eMAG system, the STUB_THREHOLD[3] in string_compare intrinsic should be lowered (or 0) for better performance with shorter Strings (less than 72 chars). I would suggest make it tunable, will file a new JBS to track the details. [1] http://openjdk.java.net/jeps/315 [2] https://bugs.openjdk.java.net/browse/JDK-8189104 [3] http://hg.openjdk.java.net/jdk/jdk/file/4aea554692aa/src/hotspot/cpu/aarch64/macroAssembler_aarch64.cpp#l4848 Regards Patrick -----Original Message----- From: aarch64-port-dev On Behalf Of Patrick Zhang OS Sent: Thursday, August 8, 2019 7:28 PM To: Andrew Haley ; aarch64-port-dev at openjdk.java.net Subject: Re: [aarch64-port-dev ] Adv. SIMD/Neon support in intrinsics/stubs for AArch64 > How would that help anything? string_compare already uses vector ops. Hmm..well. I might have thought it for granted that UMOV should be used instead of FMOV, shortly after found a piece of comment in Arm Arch ref manual [1]: >> Some of the Floating-point move (register) instructions overlap with >> the functionality provided by the Advanced SIMD instructions DUP, >> INS, and UMOV. However, ARM recommends using the FMOV instructions >> when operating on scalar floating-point data to avoid the creation of scalar floating-point code that depends on the availability of the Advanced SIMD instruction set. And in another relevant doc for A75 [2], it says FMOV's execution latency and throughput can be the better choice. [1] https://developer.arm.com/docs/ddi0487/latest/arm-architecture-reference-manual-armv8-for-armv8-a-architecture-profile, p228 [2] https://static.docs.arm.com/101398/0200/arm_cortex_a75_software_optimization_guide_v2.pdf, p11 Regards Patrick -----Original Message----- From: Andrew Haley Sent: Thursday, August 8, 2019 4:18 PM To: Patrick Zhang OS ; aarch64-port-dev at openjdk.java.net Subject: Re: [aarch64-port-dev ] Adv. SIMD/Neon support in intrinsics/stubs for AArch64 On 8/8/19 7:15 AM, Patrick Zhang OS wrote: > Does anyone know the whole picture of the Neon support in intrinsics/stubs? I'm as likely to know as anyone else. > I am not sure whether what I observed is correct: 1. Pre-Armv8 > distinguishes between VFP and Neon floating-point support but the > definitions are not explicitly separated (via any special prefix) in > assembly_aarch64.hpp. With AArch64 there's no need: AdvSIMD is part of the spec. > 2. There are some intrinsics/stubs implemented using VFP for > vectorizing, where we still have opportunities to improve by aid of > Neon 2x64-bit integer/floating-point operations, such as > string_compare [1]. How would that help anything? string_compare already uses vector ops. > 3. More intrinsics need vectorizing, with reference to other archs. Maybe. In theory it would help, but in practice meaningful speedups are quite difficult to achieve without compromising performance with small strings. But please feel free to try. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Fri Aug 9 09:51:30 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 9 Aug 2019 09:51:30 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <1051122578.6660.1565344290786.JavaMail.jenkins@6e40b75d9e9e> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/summary/2019/220/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/26 pass: 799; fail: 13; error: 2 Build 1: aarch64/2019/apr/09 pass: 807; fail: 9; error: 2 Build 2: aarch64/2019/apr/18 pass: 815; fail: 10 Build 3: aarch64/2019/apr/30 pass: 797; fail: 23; error: 9 Build 4: aarch64/2019/may/02 pass: 814; fail: 14; error: 2 Build 5: aarch64/2019/jun/15 pass: 815; fail: 22; error: 1 Build 6: aarch64/2019/jun/20 pass: 820; fail: 16; error: 2 Build 7: aarch64/2019/jun/29 pass: 807; fail: 25; error: 6 Build 8: aarch64/2019/jul/19 pass: 814; fail: 20; error: 4 Build 9: aarch64/2019/jul/25 pass: 802; fail: 25; error: 11 Build 10: aarch64/2019/jul/30 pass: 787; fail: 40; error: 11 Build 11: aarch64/2019/aug/01 pass: 800; fail: 26; error: 12 Build 12: aarch64/2019/aug/04 pass: 808; fail: 30; error: 2 Build 13: aarch64/2019/aug/06 pass: 799; fail: 29; error: 12 Build 14: aarch64/2019/aug/08 pass: 830; fail: 9; error: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/26 pass: 5,768; fail: 246; error: 29 Build 1: aarch64/2019/apr/09 pass: 5,763; fail: 267; error: 24 Build 2: aarch64/2019/apr/18 pass: 5,784; fail: 259; error: 25 Build 3: aarch64/2019/apr/30 pass: 5,779; fail: 262; error: 27 Build 4: aarch64/2019/may/02 pass: 5,784; fail: 262; error: 22 Build 5: aarch64/2019/jun/15 pass: 5,827; fail: 242; error: 22 Build 6: aarch64/2019/jun/20 pass: 5,821; fail: 244; error: 26 Build 7: aarch64/2019/jun/29 pass: 5,799; fail: 265; error: 27 Build 8: aarch64/2019/jul/19 pass: 5,940; fail: 278; error: 22 Build 9: aarch64/2019/jul/25 pass: 5,938; fail: 276; error: 26 Build 10: aarch64/2019/jul/30 pass: 5,942; fail: 273; error: 25 Build 11: aarch64/2019/aug/01 pass: 5,945; fail: 271; error: 24 Build 12: aarch64/2019/aug/04 pass: 5,949; fail: 270; error: 24 Build 13: aarch64/2019/aug/06 pass: 5,945; fail: 275; error: 23 Build 14: aarch64/2019/aug/08 pass: 5,953; fail: 267; error: 23 ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/26 pass: 3,114; fail: 2 Build 1: aarch64/2019/apr/09 pass: 3,115; fail: 2 Build 2: aarch64/2019/apr/18 pass: 3,115; fail: 2 Build 3: aarch64/2019/apr/30 pass: 3,115; fail: 2 Build 4: aarch64/2019/may/02 pass: 3,115; fail: 2 Build 5: aarch64/2019/jun/15 pass: 3,116; fail: 2 Build 6: aarch64/2019/jun/20 pass: 3,116; fail: 2 Build 7: aarch64/2019/jun/29 pass: 3,116; fail: 2 Build 8: aarch64/2019/jul/19 pass: 3,116; fail: 2 Build 9: aarch64/2019/jul/25 pass: 3,116; fail: 2 Build 10: aarch64/2019/jul/30 pass: 3,116; fail: 2 Build 11: aarch64/2019/aug/01 pass: 3,116; fail: 2 Build 12: aarch64/2019/aug/04 pass: 3,116; fail: 2 Build 13: aarch64/2019/aug/06 pass: 3,116; fail: 2 Build 14: aarch64/2019/aug/08 pass: 3,116; fail: 2 Previous results can be found here: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 6.97x Relative performance: Server critical-jOPS (nc): 8.17x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 178.67 Server 178.67 / Server 2014-04-01 (71.00): 2.52x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-03-26 pass rate: 8490/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/085/results/ 2019-04-09 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/099/results/ 2019-04-19 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/108/results/ 2019-04-30 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/120/results/ 2019-05-02 pass rate: 8490/8490, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/122/results/ 2019-06-16 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/166/results/ 2019-06-21 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/171/results/ 2019-06-30 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/180/results/ 2019-07-20 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/200/results/ 2019-07-26 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/211/results/ 2019-08-02 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/213/results/ 2019-08-05 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/216/results/ 2019-08-07 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/218/results/ 2019-08-09 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/220/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From adinn at redhat.com Fri Aug 9 10:56:44 2019 From: adinn at redhat.com (Andrew Dinn) Date: Fri, 9 Aug 2019 11:56:44 +0100 Subject: [aarch64-port-dev ] RFR [8u] JDK-8205421: AARCH64: StubCodeMark should be placed after alignment Message-ID: <68b255f1-a095-34a8-9e8d-f13254096838@redhat.com> Can I please have a review of the following AArch64-specific backport to jdk8u-shenandoah. The original patch included tweaks to stubs that don't exist in jdk8u so only a few of the changes carried through. webrev: http://cr.openjdk.java.net/~adinn/8205421-jdk8u/webrev.00 Testing: basic hotspot tests complete as before 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 shade at redhat.com Fri Aug 9 10:58:46 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Fri, 9 Aug 2019 12:58:46 +0200 Subject: [aarch64-port-dev ] RFR [8u] JDK-8205421: AARCH64: StubCodeMark should be placed after alignment In-Reply-To: <68b255f1-a095-34a8-9e8d-f13254096838@redhat.com> References: <68b255f1-a095-34a8-9e8d-f13254096838@redhat.com> Message-ID: On 8/9/19 12:56 PM, Andrew Dinn wrote: > Can I please have a review of the following AArch64-specific backport to > jdk8u-shenandoah. The original patch included tweaks to stubs that don't > exist in jdk8u so only a few of the changes carried through. > > webrev: http://cr.openjdk.java.net/~adinn/8205421-jdk8u/webrev.00 Looks good to me. -- Thanks, -Aleksey From adinn at redhat.com Fri Aug 9 11:15:11 2019 From: adinn at redhat.com (adinn at redhat.com) Date: Fri, 09 Aug 2019 11:15:11 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 8205421: AARCH64: StubCodeMark should be placed after alignment Message-ID: <201908091115.x79BFBXO007875@aojmv0008.oracle.com> Changeset: fb1c163c2bba Author: dpochepk Date: 2019-08-08 16:30 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/fb1c163c2bba 8205421: AARCH64: StubCodeMark should be placed after alignment Reviewed-by: aph ! src/cpu/aarch64/vm/stubGenerator_aarch64.cpp From gnu.andrew at redhat.com Fri Aug 9 14:34:37 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 09 Aug 2019 14:34:37 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 7 new changesets Message-ID: <201908091434.x79EYbpS008125@aojmv0008.oracle.com> Changeset: 34799214056c Author: roland Date: 2019-05-21 09:08 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/34799214056c 8224580: Matcher can cause oop field/array element to be reloaded Reviewed-by: neliasso, rkennke, dlong ! src/share/vm/opto/matcher.cpp Changeset: c963a2881865 Author: sgehwolf Date: 2019-04-25 14:02 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/c963a2881865 8222737: [TESTBUG] Allow for tier 1 like testing in OpenJDK 8u Reviewed-by: adinn, shade, andrew ! test/Makefile ! test/TEST.groups Changeset: c7a3e57fdf4a Author: andrew Date: 2019-08-01 03:44 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/c7a3e57fdf4a Added tag jdk8u232-b02 for changeset c963a2881865 ! .hgtags Changeset: 3361f4905b78 Author: andrew Date: 2019-08-02 17:05 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/3361f4905b78 Merge jdk8u232-b02 ! .hgtags ! src/share/vm/opto/matcher.cpp ! test/TEST.groups Changeset: 3caa125dac8b Author: andrew Date: 2019-08-02 17:26 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/3caa125dac8b Added tag aarch64-shenandoah-jdk8u232-b02 for changeset 3361f4905b78 ! .hgtags Changeset: 9fed88afe634 Author: andrew Date: 2019-08-09 15:33 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/9fed88afe634 Merge - src/cpu/aarch64/vm/aarch64_call.cpp - src/cpu/aarch64/vm/aarch64_linkage.S - src/cpu/aarch64/vm/cpustate_aarch64.hpp - src/cpu/aarch64/vm/decode_aarch64.hpp - src/os_cpu/linux_aarch64/vm/linux_aarch64.S Changeset: 2bcd2950d21c Author: andrew Date: 2019-08-09 15:34 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/2bcd2950d21c Merge From gnu.andrew at redhat.com Fri Aug 9 14:37:23 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Fri, 09 Aug 2019 14:37:23 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jdk: 9 new changesets Message-ID: <201908091437.x79EbNVo011483@aojmv0008.oracle.com> Changeset: 273fcb2eebd4 Author: valeriep Date: 2019-02-20 19:16 +0000 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/273fcb2eebd4 8216597: SIGBUS in Java_sun_security_pkcs11_wrapper_PKCS11_getNativeKeyInfo after JDK-6913047 Summary: changed variable declaration type to byte* from long* to fix SIGBUS error Reviewed-by: ascarpino ! src/share/native/sun/security/pkcs11/wrapper/p11_keymgmt.c Changeset: c52f29f8dd18 Author: mbalao Date: 2019-07-30 17:59 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/c52f29f8dd18 8220513: Wrapper Key may get deleted when closing sessions in SunPKCS11 crypto provider Summary: Do not close the session holding the Wrapper Key while in use. Delete the Wrapper Key when no longer needed. Reviewed-by: valeriep ! src/share/classes/sun/security/pkcs11/P11Key.java ! src/share/native/sun/security/pkcs11/wrapper/p11_keymgmt.c Changeset: 2d3d319b8f56 Author: igerasim Date: 2019-06-25 17:27 -0700 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/2d3d319b8f56 8226543: Reduce GC pressure during message digest calculations in password-based encryption Reviewed-by: mullan ! src/share/classes/com/sun/crypto/provider/PBES1Core.java Changeset: f0eb67dccf17 Author: bpb Date: 2018-07-03 15:02 -0700 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f0eb67dccf17 8202252: (aio) Closed AsynchronousSocketChannel keeps completion handler alive Summary: Clear handler instance variable after use Reviewed-by: rriggs, alanb ! src/solaris/classes/sun/nio/ch/UnixAsynchronousSocketChannelImpl.java + test/java/nio/channels/AsynchronousSocketChannel/CompletionHandlerRelease.java Changeset: 6698d87704f4 Author: sgehwolf Date: 2019-04-25 14:05 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/6698d87704f4 8222737: [TESTBUG] Allow for tier 1 like testing in OpenJDK 8u Reviewed-by: shade, adinn, andrew ! test/Makefile ! test/TEST.groups Changeset: 89c8bfe10659 Author: andrew Date: 2019-08-01 03:44 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/89c8bfe10659 Added tag jdk8u232-b02 for changeset 6698d87704f4 ! .hgtags Changeset: fd5c20ddcbb1 Author: andrew Date: 2019-08-02 17:05 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/fd5c20ddcbb1 Merge jdk8u232-b02 ! .hgtags ! src/share/classes/com/sun/crypto/provider/PBES1Core.java ! src/share/classes/sun/security/pkcs11/P11Key.java ! test/Makefile ! test/TEST.groups Changeset: 9af713a480a2 Author: andrew Date: 2019-08-02 17:26 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/9af713a480a2 Added tag aarch64-shenandoah-jdk8u232-b02 for changeset fd5c20ddcbb1 ! .hgtags Changeset: fafc7972be78 Author: andrew Date: 2019-08-09 15:37 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/fafc7972be78 Merge From gnu.andrew at redhat.com Fri Aug 9 14:39:01 2019 From: gnu.andrew at redhat.com (Andrew John Hughes) Date: Fri, 9 Aug 2019 15:39:01 +0100 Subject: [aarch64-port-dev ] [RFR] [8u] 8u232-b02 Upstream Sync In-Reply-To: <8c4a2c9a-ce25-0ffc-b1b2-d32aa47e5542@redhat.com> References: <494520b8-1ad7-d200-9855-b05c35b51d5f@redhat.com> <8c4a2c9a-ce25-0ffc-b1b2-d32aa47e5542@redhat.com> Message-ID: <5d0fb4b1-631a-5df9-8a84-aeffc18cf312@redhat.com> On 07/08/2019 08:17, Aleksey Shipilev wrote: > On 8/7/19 6:26 AM, Andrew John Hughes wrote: >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/corba/merge.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/jaxp/merge.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/jaxws/merge.changeset > > Looks trivially good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/jdk/merge.changeset > > Looks good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/hotspot/merge.changeset > > Looks good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/langtools/merge.changeset > > Looks good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/nashorn/merge.changeset > > Looks trivially good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b02/root/merge.changeset > Looks good. > > Thumbs up! > Thanks. Pushed. -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 https://keybase.io/gnu_andrew From ci_notify at linaro.org Sun Aug 11 20:50:52 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sun, 11 Aug 2019 20:50:52 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 13 on AArch64 Message-ID: <2086335397.260.1565556653927.JavaMail.jenkins@9a480cea2ca5> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk13/openjdk-jtreg-nightly-tests/summary/2019/222/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/29 pass: 5,644; fail: 3 Build 1: aarch64/2019/jul/02 pass: 5,645; fail: 2 Build 2: aarch64/2019/jul/04 pass: 5,644; fail: 2; error: 1 Build 3: aarch64/2019/jul/09 pass: 5,643; fail: 4 Build 4: aarch64/2019/jul/16 pass: 5,646; fail: 1 Build 5: aarch64/2019/jul/18 pass: 5,644; fail: 2; error: 1 Build 6: aarch64/2019/jul/20 pass: 5,645; fail: 1; error: 1 Build 7: aarch64/2019/jul/23 pass: 5,644; fail: 3 Build 8: aarch64/2019/jul/25 pass: 5,644; fail: 3 Build 9: aarch64/2019/jul/30 pass: 5,645; fail: 2 Build 10: aarch64/2019/aug/01 pass: 5,646; fail: 1 Build 11: aarch64/2019/aug/03 pass: 5,646; fail: 1 Build 12: aarch64/2019/aug/06 pass: 5,645; fail: 2 Build 13: aarch64/2019/aug/08 pass: 5,646; fail: 1 Build 14: aarch64/2019/aug/10 pass: 5,646; fail: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/29 pass: 8,601; fail: 520; error: 29 Build 1: aarch64/2019/jul/02 pass: 8,604; fail: 521; error: 25 Build 2: aarch64/2019/jul/04 pass: 8,601; fail: 523; error: 26 Build 3: aarch64/2019/jul/09 pass: 8,606; fail: 515; error: 29 Build 4: aarch64/2019/jul/16 pass: 8,593; fail: 531; error: 30 Build 5: aarch64/2019/jul/18 pass: 8,618; fail: 527; error: 26 Build 6: aarch64/2019/jul/20 pass: 8,619; fail: 519; error: 33 Build 7: aarch64/2019/jul/23 pass: 8,616; fail: 525; error: 30 Build 8: aarch64/2019/jul/25 pass: 8,620; fail: 528; error: 23 Build 9: aarch64/2019/jul/30 pass: 8,610; fail: 529; error: 32 Build 10: aarch64/2019/aug/01 pass: 8,620; fail: 527; error: 24 Build 11: aarch64/2019/aug/03 pass: 8,596; fail: 552; error: 23 Build 12: aarch64/2019/aug/06 pass: 8,616; fail: 528; error: 27 Build 13: aarch64/2019/aug/08 pass: 8,649; fail: 504; error: 18 Build 14: aarch64/2019/aug/10 pass: 8,647; fail: 507; error: 17 3 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/29 pass: 3,962 Build 1: aarch64/2019/jul/02 pass: 3,962 Build 2: aarch64/2019/jul/04 pass: 3,962 Build 3: aarch64/2019/jul/09 pass: 3,962 Build 4: aarch64/2019/jul/16 pass: 3,963 Build 5: aarch64/2019/jul/18 pass: 3,964 Build 6: aarch64/2019/jul/20 pass: 3,964 Build 7: aarch64/2019/jul/23 pass: 3,964 Build 8: aarch64/2019/jul/25 pass: 3,964 Build 9: aarch64/2019/jul/30 pass: 3,964 Build 10: aarch64/2019/aug/01 pass: 3,964 Build 11: aarch64/2019/aug/03 pass: 3,964 Build 12: aarch64/2019/aug/06 pass: 3,964 Build 13: aarch64/2019/aug/08 pass: 3,964 Build 14: aarch64/2019/aug/10 pass: 3,964 Previous results can be found here: http://openjdk.linaro.org/jdk13/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 8.04x Relative performance: Server critical-jOPS (nc): 9.25x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk13/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 210.67 Server 210.67 / Server 2014-04-01 (71.00): 2.97x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk13/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-06-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/180/results/ 2019-07-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/183/results/ 2019-07-04 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/185/results/ 2019-07-10 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/190/results/ 2019-07-16 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/197/results/ 2019-07-19 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/199/results/ 2019-07-21 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/201/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/204/results/ 2019-07-26 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/211/results/ 2019-08-02 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/213/results/ 2019-08-04 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/215/results/ 2019-08-07 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/218/results/ 2019-08-09 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/220/results/ 2019-08-11 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/2019/222/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk13/jcstress-nightly-runs/ From ci_notify at linaro.org Sun Aug 11 20:55:55 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sun, 11 Aug 2019 20:55:55 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 11u on AArch64 Message-ID: <86917436.262.1565556956249.JavaMail.jenkins@9a480cea2ca5> 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/jdk11u/openjdk-jtreg-nightly-tests/summary/2019/222/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/12 pass: 5,719; fail: 9; not run: 11,618 Build 1: aarch64/2019/mar/16 pass: 5,721; fail: 8; not run: 11,618 Build 2: aarch64/2019/mar/19 pass: 5,721; fail: 9; not run: 11,618 Build 3: aarch64/2019/mar/28 pass: 5,722; fail: 8; not run: 11,618 Build 4: aarch64/2019/apr/02 pass: 5,723; fail: 8; not run: 11,618 Build 5: aarch64/2019/apr/04 pass: 5,722; fail: 9; not run: 11,618 Build 6: aarch64/2019/apr/18 pass: 5,723; fail: 8; not run: 11,618 Build 7: aarch64/2019/may/16 pass: 5,734; fail: 5; not run: 11,623 Build 8: aarch64/2019/may/25 pass: 5,735; fail: 5; not run: 11,623 Build 9: aarch64/2019/jun/05 pass: 5,737; fail: 5; not run: 11,623 Build 10: aarch64/2019/jun/15 pass: 5,737; fail: 5; not run: 11,623 Build 11: aarch64/2019/jun/27 pass: 5,737; fail: 5 Build 12: aarch64/2019/jul/02 pass: 5,737; fail: 5 Build 13: aarch64/2019/aug/03 pass: 5,746; fail: 4 Build 14: aarch64/2019/aug/10 pass: 5,747; fail: 4 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/12 pass: 8,370; fail: 520; error: 26 Build 1: aarch64/2019/mar/16 pass: 8,397; fail: 497; error: 22 Build 2: aarch64/2019/mar/19 pass: 8,365; fail: 527; error: 24 Build 3: aarch64/2019/mar/28 pass: 8,374; fail: 521; error: 21 Build 4: aarch64/2019/apr/02 pass: 8,354; fail: 536; error: 26 Build 5: aarch64/2019/apr/04 pass: 8,382; fail: 510; error: 24 Build 6: aarch64/2019/apr/18 pass: 8,398; fail: 501; error: 19 Build 7: aarch64/2019/may/16 pass: 8,397; fail: 514; error: 22 Build 8: aarch64/2019/may/25 pass: 8,403; fail: 511; error: 21 Build 9: aarch64/2019/jun/05 pass: 8,427; fail: 489; error: 19 Build 10: aarch64/2019/jun/15 pass: 8,409; fail: 506; error: 20 Build 11: aarch64/2019/jun/27 pass: 8,401; fail: 512; error: 22 Build 12: aarch64/2019/jul/02 pass: 8,407; fail: 498; error: 31 Build 13: aarch64/2019/aug/03 pass: 8,429; fail: 509; error: 18 Build 14: aarch64/2019/aug/10 pass: 8,450; fail: 485; error: 16 3 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/12 pass: 3,904 Build 1: aarch64/2019/mar/16 pass: 3,904 Build 2: aarch64/2019/mar/19 pass: 3,904 Build 3: aarch64/2019/mar/28 pass: 3,904 Build 4: aarch64/2019/apr/02 pass: 3,904 Build 5: aarch64/2019/apr/04 pass: 3,904 Build 6: aarch64/2019/apr/18 pass: 3,904 Build 7: aarch64/2019/may/16 pass: 3,908 Build 8: aarch64/2019/may/25 pass: 3,908 Build 9: aarch64/2019/jun/05 pass: 3,908 Build 10: aarch64/2019/jun/15 pass: 3,908 Build 11: aarch64/2019/jun/27 pass: 3,908 Build 12: aarch64/2019/jul/02 pass: 3,908 Build 13: aarch64/2019/aug/03 pass: 3,908 Build 14: aarch64/2019/aug/10 pass: 3,909 Previous results can be found here: http://openjdk.linaro.org/jdk11u/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.74x Relative performance: Server critical-jOPS (nc): 8.01x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk11u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 204.57 Server 204.57 / Server 2014-04-01 (71.00): 2.88x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk11u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-03-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/071/results/ 2019-03-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/075/results/ 2019-03-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/078/results/ 2019-03-29 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/087/results/ 2019-04-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/092/results/ 2019-04-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/094/results/ 2019-04-19 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/108/results/ 2019-05-17 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/136/results/ 2019-05-26 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/145/results/ 2019-06-05 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/156/results/ 2019-06-16 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/166/results/ 2019-06-28 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/178/results/ 2019-07-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/183/results/ 2019-08-04 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/215/results/ 2019-08-11 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/222/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/ From ci_notify at linaro.org Mon Aug 12 05:51:31 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Mon, 12 Aug 2019 05:51:31 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <541461799.310.1565589093131.JavaMail.jenkins@9a480cea2ca5> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/summary/2019/223/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/apr/09 pass: 807; fail: 9; error: 2 Build 1: aarch64/2019/apr/18 pass: 815; fail: 10 Build 2: aarch64/2019/apr/30 pass: 797; fail: 23; error: 9 Build 3: aarch64/2019/may/02 pass: 814; fail: 14; error: 2 Build 4: aarch64/2019/jun/15 pass: 815; fail: 22; error: 1 Build 5: aarch64/2019/jun/20 pass: 820; fail: 16; error: 2 Build 6: aarch64/2019/jun/29 pass: 807; fail: 25; error: 6 Build 7: aarch64/2019/jul/19 pass: 814; fail: 20; error: 4 Build 8: aarch64/2019/jul/25 pass: 802; fail: 25; error: 11 Build 9: aarch64/2019/jul/30 pass: 787; fail: 40; error: 11 Build 10: aarch64/2019/aug/01 pass: 800; fail: 26; error: 12 Build 11: aarch64/2019/aug/04 pass: 808; fail: 30; error: 2 Build 12: aarch64/2019/aug/06 pass: 799; fail: 29; error: 12 Build 13: aarch64/2019/aug/08 pass: 830; fail: 9; error: 1 Build 14: aarch64/2019/aug/11 pass: 825; fail: 14; error: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/apr/09 pass: 5,763; fail: 267; error: 24 Build 1: aarch64/2019/apr/18 pass: 5,784; fail: 259; error: 25 Build 2: aarch64/2019/apr/30 pass: 5,779; fail: 262; error: 27 Build 3: aarch64/2019/may/02 pass: 5,784; fail: 262; error: 22 Build 4: aarch64/2019/jun/15 pass: 5,827; fail: 242; error: 22 Build 5: aarch64/2019/jun/20 pass: 5,821; fail: 244; error: 26 Build 6: aarch64/2019/jun/29 pass: 5,799; fail: 265; error: 27 Build 7: aarch64/2019/jul/19 pass: 5,940; fail: 278; error: 22 Build 8: aarch64/2019/jul/25 pass: 5,938; fail: 276; error: 26 Build 9: aarch64/2019/jul/30 pass: 5,942; fail: 273; error: 25 Build 10: aarch64/2019/aug/01 pass: 5,945; fail: 271; error: 24 Build 11: aarch64/2019/aug/04 pass: 5,949; fail: 270; error: 24 Build 12: aarch64/2019/aug/06 pass: 5,945; fail: 275; error: 23 Build 13: aarch64/2019/aug/08 pass: 5,953; fail: 267; error: 23 Build 14: aarch64/2019/aug/11 pass: 5,947; fail: 272; error: 25 ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/apr/09 pass: 3,115; fail: 2 Build 1: aarch64/2019/apr/18 pass: 3,115; fail: 2 Build 2: aarch64/2019/apr/30 pass: 3,115; fail: 2 Build 3: aarch64/2019/may/02 pass: 3,115; fail: 2 Build 4: aarch64/2019/jun/15 pass: 3,116; fail: 2 Build 5: aarch64/2019/jun/20 pass: 3,116; fail: 2 Build 6: aarch64/2019/jun/29 pass: 3,116; fail: 2 Build 7: aarch64/2019/jul/19 pass: 3,116; fail: 2 Build 8: aarch64/2019/jul/25 pass: 3,116; fail: 2 Build 9: aarch64/2019/jul/30 pass: 3,116; fail: 2 Build 10: aarch64/2019/aug/01 pass: 3,116; fail: 2 Build 11: aarch64/2019/aug/04 pass: 3,116; fail: 2 Build 12: aarch64/2019/aug/06 pass: 3,116; fail: 2 Build 13: aarch64/2019/aug/08 pass: 3,116; fail: 2 Build 14: aarch64/2019/aug/11 pass: 3,116; fail: 2 Previous results can be found here: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 6.97x Relative performance: Server critical-jOPS (nc): 8.15x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 174.26 Server 174.26 / Server 2014-04-01 (71.00): 2.45x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-04-09 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/099/results/ 2019-04-19 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/108/results/ 2019-04-30 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/120/results/ 2019-05-02 pass rate: 8490/8490, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/122/results/ 2019-06-16 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/166/results/ 2019-06-21 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/171/results/ 2019-06-30 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/180/results/ 2019-07-20 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/200/results/ 2019-07-26 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/211/results/ 2019-08-02 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/213/results/ 2019-08-05 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/216/results/ 2019-08-07 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/218/results/ 2019-08-09 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/220/results/ 2019-08-12 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/223/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From felix.yang at huawei.com Mon Aug 12 08:43:19 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Mon, 12 Aug 2019 08:43:19 +0000 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency Message-ID: Hi, Could I have a review of the following AArch64-specific backport to jdk8u-shenandoah please? Webrev: http://cr.openjdk.java.net/~fyang/mm-8u-backport/webrev.00/ We are witnessing real-world volatile access inconsistency bugs on our Kunpeng 64/128 core server platform. As pointed out on JDK-8179954 and JDK-8209420, C2 should always emit LDAR/STLR for volatile accesses. For this to work properly the aarch64 backend has to locate membars that go with a memory access to elide them. This is currently implemented with some complicated pattern matching for the 8u-aarch64 port. We found it failed for certain cases due to unexpected C2 graph shapes one of which looks like: LoadX[mo_unordered] LoadX[mo_acquire] // \\ // Phi // \\ MemBarAcquire Pattern matching will not consider the Phi node here for this case. As a result, C2 emits a combination of ldr and dmb ishld for the volatile read access. We also see other graph shapes. JDK-8209420 fixed this issue with a better solution: tracking members for volatile accesses from the start. Webrev includes the following 5 patches in time order (4 and 5 are follow-up fixes for 3) : 1. https://bugs.openjdk.java.net/browse/JDK-8179954 http://hg.openjdk.java.net/jdk9/jdk9/hotspot/rev/38a240fd58a2 2. https://bugs.openjdk.java.net/browse/JDK-8206163 http://hg.openjdk.java.net/jdk/jdk11/rev/8df91a1b549b 3. https://bugs.openjdk.java.net/browse/JDK-8209420 http://hg.openjdk.java.net/jdk/jdk/rev/d7029542d67a 4. https://bugs.openjdk.java.net/browse/JDK-8211233 http://hg.openjdk.java.net/jdk/jdk/rev/bbc90467f354 5. https://bugs.openjdk.java.net/browse/JDK-8214857 http://hg.openjdk.java.net/jdk/jdk/rev/6e7db888f04c 3 fixes volatile access inconsistency issue for C2. 1 handles the case for C1 and template interpreter. 2 is included because in fact it is also a pattern matching issue and it changes some shared part with 3. The backport patch for 3 includes tweaks for tracking members which corresponds to changes in barrierSetC2.cpp of the original patch. Testing: Jtreg tested with both 8u aarch64 fastdebug build and release build. Passed Jcstress test with TieredCompilation option turned on & off. Thanks, Felix From adinn at redhat.com Mon Aug 12 09:26:51 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 12 Aug 2019 10:26:51 +0100 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency In-Reply-To: References: Message-ID: Hi Felix, On 12/08/2019 09:43, Yangfei (Felix) wrote: > Could I have a review of the following AArch64-specific backport to > jdk8u-shenandoah please? I think this patch would be worth backporting /even without/ the problems you have encountered because it significantly reduces complexity. > Webrev: http://cr.openjdk.java.net/~fyang/mm-8u-backport/webrev.00/ This patch looks good to me. > Testing: > > Jtreg tested with both 8u aarch64 fastdebug build and release build. > > Passed Jcstress test with TieredCompilation option turned on & off. Excellent. I think this is ok to push. However, I would be happier if Roland could also check it before you do that. 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 Mon Aug 12 09:37:24 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 12 Aug 2019 10:37:24 +0100 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency In-Reply-To: References: Message-ID: <1f92a9da-f3c3-8044-3de2-05ed2f9d9105@redhat.com> Hi Felix, Aleksey pointed out to me that patches 3 4 and 5 are not in jdk11u. You will need to backport these to 11u before they can appear in jdk8u-aarch64. So, please negotiate this via the jdkupdates mail list and/or Fix-Requests on the relevant JIRAs. Also, it will be necessary to backport each change to jdk8u separately rather than committing all 5 as a single patch. regards, Andrew Dinn ----------- On 12/08/2019 10:26, Andrew Dinn wrote: > On 12/08/2019 09:43, Yangfei (Felix) wrote: >> Could I have a review of the following AArch64-specific backport to >> jdk8u-shenandoah please? > > I think this patch would be worth backporting /even without/ the > problems you have encountered because it significantly reduces complexity. > >> Webrev: http://cr.openjdk.java.net/~fyang/mm-8u-backport/webrev.00/ > > This patch looks good to me. > >> Testing: >> >> Jtreg tested with both 8u aarch64 fastdebug build and release build. >> >> Passed Jcstress test with TieredCompilation option turned on & off. > > Excellent. > > I think this is ok to push. However, I would be happier if Roland could > also check it before you do that. > > 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 > -- 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 Mon Aug 12 10:01:52 2019 From: aph at redhat.com (Andrew Haley) Date: Mon, 12 Aug 2019 11:01:52 +0100 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency In-Reply-To: References: Message-ID: On 8/12/19 10:26 AM, Andrew Dinn wrote: > I think this is ok to push. However, I would be happier if Roland could > also check it before you do that. I think so too. Mind you, it's a complex patch. On the other hand, it does get rid of a lot of cruft. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From shade at redhat.com Mon Aug 12 10:07:38 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 12 Aug 2019 12:07:38 +0200 Subject: [aarch64-port-dev ] RFR (S) 8228725: AArch64: Purge method call format support Message-ID: <5e6d61c6-4568-c6a5-dc67-60d7e3932177@redhat.com> Original RFE: https://bugs.openjdk.java.net/browse/JDK-8228725 https://hg.openjdk.java.net/jdk/jdk/rev/ec78fddafd88 As mentioned in the RFE, 8u-aarch64 version can remove more than upstream patch. It reverses changes in method.{c|h}pp to 8u upstream state: https://cr.openjdk.java.net/~shade/8228725/webrev.8u.01/ Testing: aarch64 tier1 (assorted existing failures are there), hotspot_gc_shenandoah -- Thanks, -Aleksey From nick.gasson at arm.com Mon Aug 12 10:24:35 2019 From: nick.gasson at arm.com (Nick Gasson) Date: Mon, 12 Aug 2019 18:24:35 +0800 Subject: [aarch64-port-dev ] RFR: 8229118: [TESTBUG] serviceability/sa/ClhsdbFindPC fails on AArch64 In-Reply-To: <39f8fd3f-fcce-0200-3922-33405978e297@redhat.com> References: <4a646485-4230-9632-dfd4-4368d79ba4cd@arm.com> <39f8fd3f-fcce-0200-3922-33405978e297@redhat.com> Message-ID: <5071d6c9-73f8-4c7d-4ae8-3b3d1bcddf82@arm.com> Thanks Andrew. Can someone from the serviceability team check this is OK to push? Nick On 08/08/2019 18:16, Andrew Dinn wrote: > Hi Nick, > > On 08/08/2019 10:32, Nick Gasson wrote: >> Bug: https://bugs.openjdk.java.net/browse/JDK-8229118 >> Webrev: http://cr.openjdk.java.net/~ngasson/8229118/webrev.0/ >> >> This test starts a sub-process with -Xcomp and then uses the SA to get a >> stack trace of it. It expects to see this line: >> >> In code in NMethod for jdk/test/lib/apps/LingeredApp.main >> >> But actually on AArch64 the stack trace looks like this: >> >> - java.lang.Thread.sleep(long) @bci=0, pc=0x0000ffff74603d08, Method*=0x0000ffff031baf98 (Compiled frame; information may be imprecise) >> - jdk.test.lib.apps.LingeredApp.main(java.lang.String[]) @bci=53, line=502, pc=0x0000ffff6c9276e0, Method*=0x0000ffff03611d48 (Interpreted frame) >> >> The main method is interpreted even though we're running with >> -Xcomp. That's because it is deoptimized almost immediately, because >> main calls some methods on java.nio.file.Paths, but that class hasn't >> been loaded when main is compiled. >> >> X86 can patch in the address of the method on-the-fly, but AArch64 can't >> do this because of restrictions on which instructions can be legally >> rewritten. >> >> This patch lifts the code that uses the java.nio classes out of >> LingeredApp::main into a separate static method. LingeredApp.main now >> only uses classes that are loaded very early in boot, before main is >> compiled. The stack trace now looks like: >> >> "main" #1 prio=5 tid=0x0000ffffb4022800 nid=0xd610 waiting on condition [0x0000ffffbb755000] >> java.lang.Thread.State: TIMED_WAITING (sleeping) >> JavaThread state: _thread_blocked >> - java.lang.Thread.sleep(long) @bci=0, pc=0x0000fffface414c8, Method*=0x0000ffff3dac8a28 (Compiled frame; information may be imprecise) >> - jdk.test.lib.apps.LingeredApp.pollLockFile(java.lang.String) @bci=30, line=499, pc=0x0000ffffa50818e0, Method*=0x0000ffff3c122cf0 (Interpreted frame) >> - jdk.test.lib.apps.LingeredApp.main(java.lang.String[]) @bci=25, line=529, pc=0x0000ffffa59afd58, Method*=0x0000ffff3c122de0 (Compiled frame) >> >> I.e. pollLockFile was deoptimized to an interpreted frame but >> LingeredApp.main is still a compiled frame which is what ClhsdbFindPC is >> looking for. >> >> This solution does seem a bit hacky, so if it's not acceptable an >> alternative is to just skip the -Xcomp part of the test on AArch64. >> >> Ran a full jtreg test on AArch64/x86 to check for regressions. > Yuck! That's a nice hack to avoid the indeterminate effect of -Xcomp. > However, my gut feeling is still that relying on -Xcomp in tests is just > a /really/ bad idea and I'd prefer to omit it but . . . > > I'm not 100% clear what the point of this test is but it looks like it > is meant to exercise the stack backtrace code when there is a compiled > method on the stack. If so then I guess your hack fits the bill while > removing the -Xcomp flag from the command line would not fulfil the > test's remit. If that is the point of the test then I agree, > reluctantly, that your hack is the right solution. On those grounds I'm > happy to accept the patch. However, I'd prefer someone else (Andrew > Haley?) also to review this before it gets pushed. > > 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 Mon Aug 12 10:30:17 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 12 Aug 2019 11:30:17 +0100 Subject: [aarch64-port-dev ] Weird behaviour with tests for: JDK-8213134 AArch64: vector shift failed with MaxVectorSize=8 Message-ID: I am currently trying to test a backport of the above patch for JDK11 on AArch64 and I noticed that tests Test{Short/Int/...}Vect etc all run much slower than TestByteVect. Waaaay slower. The difference is roughly 10-20 seconds vs 10-20 minutes. I also noticed when I ran 'top' in thread view that the C1 Compiler thread runs flat out while the Main thread eats only a few percent of CPU. This is weird because all the tests have essentially the same code structure: Call a whole slew of sub-test methods (there really are a lot of them) in a loop to ensure they are C2 compiled. Then call each sub-test method and loop over the resultant array verifying that each entry is as expected. I reran with -XX:+PrintCompilation and observed a significant difference in the compiler behaviour. In the Byte test method TestByteVect::test and the many sub-test methods it calls in its warmup loop get compiled at level 3 and then level 4. They *stay* that way as the main routine goes on to call each sub-test method in the block that follows the loop. By contrast: in the Short test method TestShortVect::test still gets compiled at level 3 then level 4 in the warmup loop as does each sub-test method called in the loop but then ... Between successive sub-test calls in the following block the level 4 and level 3 versions of TestShortVect::test are repeatedly made not entrant. The method is deoptimized and then re-optimized first to level 3 and then to level 4 (you can tell because after each call a message is printed). Finally, towards the end of the Short Test test there is a whole series of 'made zombie' notices for the many different level 3 and level 4 versions of TestShortVect::test as well as a pair of 'made zombie' notices for the level 3 versions of each of the sub-test methods. So, it seemed that this weird oscillating behaviour constitutes repeated OSR compilation then deopt of the main test method. It was not clear to me why the de-opt is happening (also why it is not happening in the Byte case). The way the top level test routine is routine seems to pose a severe challenge to some of the assumptions the OSR compiler is making. Anyway, it is bizarre as well as extremely inconvenient that each test takes such a very, very long time to run. Especially inconvenient given that each test has to be run for each of the 4 available MaxVectorSize settings. In order to verify that it is the top level test method causing the problem I reran the TestShortVect test with a compiler restriction as follows -XX:CompileCommand=compileonly,TestShortVect::test_* i.e. only compile the sub-test methods called from the main loop (which all start with prefix test_). As expected, the run time came back down into the expected 10-20 second range. Clearly, the fact that these tests constitute a basket case for the compiler needs further investigation. I will look into that -- unless anyone already knows why this will be happening. Meanwhile, there may well be some easy way to avoid the compiler issue by refactoring the code (e.g. installing the loops in a separate verify routine). If not then a CompileCommand added to the @run arguments for the test would make the tests much more useful (well, it would make them useful). 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 Mon Aug 12 10:33:50 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 12 Aug 2019 11:33:50 +0100 Subject: [aarch64-port-dev ] RFR (S) 8228725: AArch64: Purge method call format support In-Reply-To: <5e6d61c6-4568-c6a5-dc67-60d7e3932177@redhat.com> References: <5e6d61c6-4568-c6a5-dc67-60d7e3932177@redhat.com> Message-ID: <38aacbec-d657-7010-bea3-01a4cbbc0fc6@redhat.com> On 12/08/2019 11:07, Aleksey Shipilev wrote: > Original RFE: > https://bugs.openjdk.java.net/browse/JDK-8228725 > https://hg.openjdk.java.net/jdk/jdk/rev/ec78fddafd88 > > As mentioned in the RFE, 8u-aarch64 version can remove more than upstream patch. It reverses changes > in method.{c|h}pp to 8u upstream state: > https://cr.openjdk.java.net/~shade/8228725/webrev.8u.01/ > > Testing: aarch64 tier1 (assorted existing failures are there), hotspot_gc_shenandoah Looking good. 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 shade at redhat.com Mon Aug 12 13:49:43 2019 From: shade at redhat.com (shade at redhat.com) Date: Mon, 12 Aug 2019 13:49:43 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 8228725: AArch64: Purge method call format support Message-ID: <201908121349.x7CDnhqs023094@aojmv0008.oracle.com> Changeset: 21ef28d4f754 Author: shade Date: 2019-07-30 22:16 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/21ef28d4f754 8228725: AArch64: Purge method call format support Reviewed-by: adinn ! src/cpu/aarch64/vm/interpreterRT_aarch64.cpp ! src/cpu/aarch64/vm/interpreterRT_aarch64.hpp ! src/cpu/aarch64/vm/macroAssembler_aarch64.hpp ! src/cpu/aarch64/vm/templateInterpreter_aarch64.cpp ! src/share/vm/oops/method.cpp ! src/share/vm/oops/method.hpp From shade at redhat.com Mon Aug 12 13:49:54 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Mon, 12 Aug 2019 15:49:54 +0200 Subject: [aarch64-port-dev ] RFR (S) 8228725: AArch64: Purge method call format support In-Reply-To: <38aacbec-d657-7010-bea3-01a4cbbc0fc6@redhat.com> References: <5e6d61c6-4568-c6a5-dc67-60d7e3932177@redhat.com> <38aacbec-d657-7010-bea3-01a4cbbc0fc6@redhat.com> Message-ID: On 8/12/19 12:33 PM, Andrew Dinn wrote: > On 12/08/2019 11:07, Aleksey Shipilev wrote: >> Original RFE: >> https://bugs.openjdk.java.net/browse/JDK-8228725 >> https://hg.openjdk.java.net/jdk/jdk/rev/ec78fddafd88 >> >> As mentioned in the RFE, 8u-aarch64 version can remove more than upstream patch. It reverses changes >> in method.{c|h}pp to 8u upstream state: >> https://cr.openjdk.java.net/~shade/8228725/webrev.8u.01/ >> >> Testing: aarch64 tier1 (assorted existing failures are there), hotspot_gc_shenandoah > Looking good. Thanks, pushed. -- Thanks, -Aleksey From adinn at redhat.com Mon Aug 12 15:23:35 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 12 Aug 2019 16:23:35 +0100 Subject: [aarch64-port-dev ] Weird behaviour with tests for: JDK-8213134 AArch64: vector shift failed with MaxVectorSize=8 In-Reply-To: References: Message-ID: <683b1257-65c9-5d2d-57ab-9073149e6018@redhat.com> On 12/08/2019 11:30, Andrew Dinn wrote: > I am currently trying to test a backport of the above patch for JDK11 on > AArch64 and I noticed that tests Test{Short/Int/...}Vect etc all run > much slower than TestByteVect. Waaaay slower. The difference is roughly > 10-20 seconds vs 10-20 minutes. I forgot to mention the figures cited above were obtained running with a fastdebug build. The problem is less severe with a release build although there is still quite a noticeable slowdown (from 3 seconds to 33 seconds). It turns out that the problem when executing the TestShortVect relates to the sequence of loops at the end of the top level method. Each of them iterates over a call to a different sub-test method (there are 72 of these methods!). When each loop is entered the top-level method first gets C1 OSR compiled and then C2 OSR compiled. The C2 compile includes only the code for the loop. After the loop completes it terminates very quickly with an unconditional uncommon trap that reverts to interpreted. The C1 code runs particularly slowly as it includes lots of profiling (and for non-product code also includes various debug checks). The C1 compile also takes a long time as it compiles the whole method every time rather than just the loop code. So, the slow down seems to result from a combination of taking a long time to deliver not very well optimized C1 code to replace interpreted execution and very little gain when the C1 code finally gets run because of the associated profiling (and debug verify) costs with the assumed gain from doing that compilation foiled by an almost immediate reversion to interpreted once the C2 code is delivered. Anyway, the important thing is that it doesn't appear to be a problem with the patch side-effecting the test which was what I really had to check. The puzzling this is why this same problem does not cause a slow down for TestByteVect? There are a similar 72 loops at the end of the top level method but they don't lead to OSR compiles of the top level method. Given that the code is pretty much identical except for using byte[] in place of short[] that's still something of a mystery. 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 ci_notify at linaro.org Tue Aug 13 02:20:58 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Tue, 13 Aug 2019 02:20:58 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <149654477.485.1565662858881.JavaMail.jenkins@9a480cea2ca5> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2019/224/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/09 pass: 5,695; fail: 3 Build 1: aarch64/2019/jul/11 pass: 5,696; fail: 3 Build 2: aarch64/2019/jul/12 pass: 5,695; fail: 5 Build 3: aarch64/2019/jul/15 pass: 5,699; fail: 1 Build 4: aarch64/2019/jul/17 pass: 5,700; fail: 1; error: 1 Build 5: aarch64/2019/jul/19 pass: 5,699; fail: 3; error: 1 Build 6: aarch64/2019/jul/22 pass: 5,705; fail: 2 Build 7: aarch64/2019/jul/24 pass: 5,706; fail: 1 Build 8: aarch64/2019/jul/26 pass: 5,707; fail: 2 Build 9: aarch64/2019/jul/29 pass: 5,705; fail: 4 Build 10: aarch64/2019/jul/31 pass: 5,711; fail: 1 Build 11: aarch64/2019/aug/02 pass: 5,711; fail: 2 Build 12: aarch64/2019/aug/05 pass: 5,712; fail: 1 Build 13: aarch64/2019/aug/07 pass: 5,711; fail: 1 Build 14: aarch64/2019/aug/12 pass: 5,713; fail: 2 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/09 pass: 8,604; fail: 532; error: 19 Build 1: aarch64/2019/jul/11 pass: 8,598; fail: 529; error: 31 Build 2: aarch64/2019/jul/12 pass: 8,601; fail: 528; error: 29 Build 3: aarch64/2019/jul/15 pass: 8,602; fail: 533; error: 25 Build 4: aarch64/2019/jul/17 pass: 8,614; fail: 522; error: 24 Build 5: aarch64/2019/jul/19 pass: 8,611; fail: 526; error: 26 Build 6: aarch64/2019/jul/22 pass: 8,628; fail: 511; error: 24 Build 7: aarch64/2019/jul/24 pass: 8,617; fail: 538; error: 26 Build 8: aarch64/2019/jul/26 pass: 8,649; fail: 518; error: 17 Build 9: aarch64/2019/jul/29 pass: 8,640; fail: 520; error: 26 Build 10: aarch64/2019/jul/31 pass: 8,640; fail: 526; error: 24 Build 11: aarch64/2019/aug/02 pass: 8,637; fail: 524; error: 29 Build 12: aarch64/2019/aug/05 pass: 8,642; fail: 519; error: 29 Build 13: aarch64/2019/aug/07 pass: 8,638; fail: 529; error: 23 Build 14: aarch64/2019/aug/12 pass: 8,659; fail: 515; error: 19 4 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/09 pass: 3,967 Build 1: aarch64/2019/jul/11 pass: 3,968 Build 2: aarch64/2019/jul/12 pass: 3,968 Build 3: aarch64/2019/jul/15 pass: 3,968 Build 4: aarch64/2019/jul/17 pass: 3,968 Build 5: aarch64/2019/jul/19 pass: 3,969 Build 6: aarch64/2019/jul/22 pass: 3,969 Build 7: aarch64/2019/jul/24 pass: 3,970 Build 8: aarch64/2019/jul/26 pass: 3,970 Build 9: aarch64/2019/jul/29 pass: 3,970 Build 10: aarch64/2019/jul/31 pass: 3,970 Build 11: aarch64/2019/aug/02 pass: 3,970 Build 12: aarch64/2019/aug/05 pass: 3,970 Build 13: aarch64/2019/aug/07 pass: 3,970 Build 14: aarch64/2019/aug/12 pass: 3,970 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.84x Relative performance: Server critical-jOPS (nc): 9.38x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 196.04 Server 196.04 / Server 2014-04-01 (71.00): 2.76x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-01-01 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/365/results/ 2019-07-10 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/190/results/ 2019-07-12 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/192/results/ 2019-07-15 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/196/results/ 2019-07-17 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/198/results/ 2019-07-20 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/200/results/ 2019-07-22 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/203/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/205/results/ 2019-07-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/207/results/ 2019-07-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/210/results/ 2019-08-01 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/212/results/ 2019-08-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/214/results/ 2019-08-06 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/217/results/ 2019-08-08 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/219/results/ 2019-08-13 pass rate: 10487/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/224/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From felix.yang at huawei.com Tue Aug 13 05:58:46 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Tue, 13 Aug 2019 05:58:46 +0000 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency Message-ID: Hi, Thank you for your prompt reply. It's appreciated if the authors can confirm the tweaks here, especially 3, 4 and 5. Comments inlined: Hi Felix, Aleksey pointed out to me that patches 3 4 and 5 are not in jdk11u. You will need to backport these to 11u before they can appear in jdk8u-aarch64. So, please negotiate this via the jdkupdates mail list and/or Fix-Requests on the relevant JIRAs. Fyang: OK, will do. The good news is that patches for 3, 4 and 5 can be applied cleanly on the latest 11u repo. We still need some necessary testing. Also, it will be necessary to backport each change to jdk8u separately rather than committing all 5 as a single patch. Fyang: I did one "hg commit" for each patch, so there are 5 commits contained in the webrev. I am assuming this is OK. regards, Andrew Dinn ----------- From adinn at redhat.com Tue Aug 13 07:44:11 2019 From: adinn at redhat.com (Andrew Dinn) Date: Tue, 13 Aug 2019 08:44:11 +0100 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency In-Reply-To: References: Message-ID: <07ba2053-c85f-42a8-8844-35dcd185ef30@redhat.com> On 13/08/2019 06:58, Yangfei (Felix) wrote: > Thank you for your prompt reply. It's appreciated if the authors can > confirm the tweaks here, especially 3, 4 and 5. > > Comments inlined: > > Aleksey pointed out to me that patches 3 4 and 5 are not in jdk11u. > You will need to backport these to 11u before they can appear in > jdk8u-aarch64. So, please negotiate this via the jdkupdates mail list > and/or Fix-Requests on the relevant JIRAs. > > Fyang: OK, will do. The good news is that patches for 3, 4 and 5 can > be applied cleanly on the latest 11u repo. We still need some > necessary testing. Ok, that's good. So, you only need to follow the jdk11u fix request process on each JIRA without need for another email review. > Also, it will be necessary to backport each change to jdk8u > separately rather than committing all 5 as a single patch. > > Fyang: I did one "hg commit" for each patch, so there are 5 commits > contained in the webrev. I am assuming this is OK. Yes, that will be OK. Thank you. 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 nick.gasson at arm.com Tue Aug 13 09:38:07 2019 From: nick.gasson at arm.com (Nick Gasson) Date: Tue, 13 Aug 2019 17:38:07 +0800 Subject: [aarch64-port-dev ] RFR: 8229118: [TESTBUG] serviceability/sa/ClhsdbFindPC fails on AArch64 In-Reply-To: References: <4a646485-4230-9632-dfd4-4368d79ba4cd@arm.com> <39f8fd3f-fcce-0200-3922-33405978e297@redhat.com> <5071d6c9-73f8-4c7d-4ae8-3b3d1bcddf82@arm.com> Message-ID: <178290d1-7904-d59e-3f64-3f57a51ac071@arm.com> Hi Chris, > > Adding to Andrew comments, maybe the solution is to have the test extend > LingeredApp so it can produce a more reliable stack trace other than the > default one you get with LingeredApp. If that's too much trouble, I > don't mind the solution you came up with, but seems writing a > LingeredApp subclass that is specific for this test would be cleaner. Thanks for the suggestion, this does seem much cleaner. Please check the updated webrev here: http://cr.openjdk.java.net/~ngasson/8229118/webrev.1/ Thanks, Nick From ci_notify at linaro.org Tue Aug 13 14:52:21 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Tue, 13 Aug 2019 14:52:21 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <1629857175.682.1565707942805.JavaMail.jenkins@9a480cea2ca5> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/summary/2019/225/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/apr/18 pass: 815; fail: 10 Build 1: aarch64/2019/apr/30 pass: 797; fail: 23; error: 9 Build 2: aarch64/2019/may/02 pass: 814; fail: 14; error: 2 Build 3: aarch64/2019/jun/15 pass: 815; fail: 22; error: 1 Build 4: aarch64/2019/jun/20 pass: 820; fail: 16; error: 2 Build 5: aarch64/2019/jun/29 pass: 807; fail: 25; error: 6 Build 6: aarch64/2019/jul/19 pass: 814; fail: 20; error: 4 Build 7: aarch64/2019/jul/25 pass: 802; fail: 25; error: 11 Build 8: aarch64/2019/jul/30 pass: 787; fail: 40; error: 11 Build 9: aarch64/2019/aug/01 pass: 800; fail: 26; error: 12 Build 10: aarch64/2019/aug/04 pass: 808; fail: 30; error: 2 Build 11: aarch64/2019/aug/06 pass: 799; fail: 29; error: 12 Build 12: aarch64/2019/aug/08 pass: 830; fail: 9; error: 1 Build 13: aarch64/2019/aug/11 pass: 825; fail: 14; error: 1 Build 14: aarch64/2019/aug/13 pass: 830; fail: 9; error: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/apr/18 pass: 5,784; fail: 259; error: 25 Build 1: aarch64/2019/apr/30 pass: 5,779; fail: 262; error: 27 Build 2: aarch64/2019/may/02 pass: 5,784; fail: 262; error: 22 Build 3: aarch64/2019/jun/15 pass: 5,827; fail: 242; error: 22 Build 4: aarch64/2019/jun/20 pass: 5,821; fail: 244; error: 26 Build 5: aarch64/2019/jun/29 pass: 5,799; fail: 265; error: 27 Build 6: aarch64/2019/jul/19 pass: 5,940; fail: 278; error: 22 Build 7: aarch64/2019/jul/25 pass: 5,938; fail: 276; error: 26 Build 8: aarch64/2019/jul/30 pass: 5,942; fail: 273; error: 25 Build 9: aarch64/2019/aug/01 pass: 5,945; fail: 271; error: 24 Build 10: aarch64/2019/aug/04 pass: 5,949; fail: 270; error: 24 Build 11: aarch64/2019/aug/06 pass: 5,945; fail: 275; error: 23 Build 12: aarch64/2019/aug/08 pass: 5,953; fail: 267; error: 23 Build 13: aarch64/2019/aug/11 pass: 5,947; fail: 272; error: 25 Build 14: aarch64/2019/aug/13 pass: 5,962; fail: 258; error: 24 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/apr/18 pass: 3,115; fail: 2 Build 1: aarch64/2019/apr/30 pass: 3,115; fail: 2 Build 2: aarch64/2019/may/02 pass: 3,115; fail: 2 Build 3: aarch64/2019/jun/15 pass: 3,116; fail: 2 Build 4: aarch64/2019/jun/20 pass: 3,116; fail: 2 Build 5: aarch64/2019/jun/29 pass: 3,116; fail: 2 Build 6: aarch64/2019/jul/19 pass: 3,116; fail: 2 Build 7: aarch64/2019/jul/25 pass: 3,116; fail: 2 Build 8: aarch64/2019/jul/30 pass: 3,116; fail: 2 Build 9: aarch64/2019/aug/01 pass: 3,116; fail: 2 Build 10: aarch64/2019/aug/04 pass: 3,116; fail: 2 Build 11: aarch64/2019/aug/06 pass: 3,116; fail: 2 Build 12: aarch64/2019/aug/08 pass: 3,116; fail: 2 Build 13: aarch64/2019/aug/11 pass: 3,116; fail: 2 Build 14: aarch64/2019/aug/13 pass: 3,116; fail: 2 Previous results can be found here: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 6.89x Relative performance: Server critical-jOPS (nc): 8.84x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 174.26 Server 174.26 / Server 2014-04-01 (71.00): 2.45x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-04-19 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/108/results/ 2019-04-30 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/120/results/ 2019-05-02 pass rate: 8490/8490, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/122/results/ 2019-06-16 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/166/results/ 2019-06-21 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/171/results/ 2019-06-30 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/180/results/ 2019-07-20 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/200/results/ 2019-07-26 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/211/results/ 2019-08-02 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/213/results/ 2019-08-05 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/216/results/ 2019-08-07 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/218/results/ 2019-08-09 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/220/results/ 2019-08-12 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/223/results/ 2019-08-13 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/225/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From nick.gasson at arm.com Wed Aug 14 01:26:31 2019 From: nick.gasson at arm.com (Nick Gasson) Date: Wed, 14 Aug 2019 09:26:31 +0800 Subject: [aarch64-port-dev ] RFR: 8229118: [TESTBUG] serviceability/sa/ClhsdbFindPC fails on AArch64 In-Reply-To: References: <4a646485-4230-9632-dfd4-4368d79ba4cd@arm.com> <39f8fd3f-fcce-0200-3922-33405978e297@redhat.com> <5071d6c9-73f8-4c7d-4ae8-3b3d1bcddf82@arm.com> <178290d1-7904-d59e-3f64-3f57a51ac071@arm.com> Message-ID: Hi Chris, > The changes look good, although I think the new file should go in the > serviceability/sa test directory, unless you think this is a generally > useful class that might be used by tests outside of the sa. > The new file is under test/hotspot/jtreg/serviceability/sa/ - the same directory as ClhsdbFindPC.java - did you mean somewhere else? Thanks, Nick From felix.yang at huawei.com Wed Aug 14 02:06:02 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Wed, 14 Aug 2019 02:06:02 +0000 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency Message-ID: > Fyang: OK, will do. The good news is that patches for 3, 4 and 5 can > be applied cleanly on the latest 11u repo. We still need some > necessary testing. Ok, that's good. So, you only need to follow the jdk11u fix request process on each JIRA without need for another email review. Fyang: Yes. As they passed tier1 test and jctress test, I have done that accordingly for 2, 3 and 4. Thank you for your help, Felix From adinn at redhat.com Wed Aug 14 08:10:42 2019 From: adinn at redhat.com (Andrew Dinn) Date: Wed, 14 Aug 2019 09:10:42 +0100 Subject: [aarch64-port-dev ] RFR: 8229118: [TESTBUG] serviceability/sa/ClhsdbFindPC fails on AArch64 In-Reply-To: <04ae9472-05e5-91a9-b986-428806a7ee15@oracle.com> References: <4a646485-4230-9632-dfd4-4368d79ba4cd@arm.com> <39f8fd3f-fcce-0200-3922-33405978e297@redhat.com> <5071d6c9-73f8-4c7d-4ae8-3b3d1bcddf82@arm.com> <178290d1-7904-d59e-3f64-3f57a51ac071@arm.com> <04ae9472-05e5-91a9-b986-428806a7ee15@oracle.com> Message-ID: <4c9f5bb8-2a67-258e-9b65-acc91237055f@redhat.com> On 14/08/2019 03:28, Chris Plummer wrote: > On 8/13/19 6:26 PM, Nick Gasson wrote: >> Hi Chris, >> >>> The changes look good, although I think the new file should go in the >>> serviceability/sa test directory, unless you think this is a generally >>> useful class that might be used by tests outside of the sa. >>> >> >> The new file is under test/hotspot/jtreg/serviceability/sa/ - the same >> directory as ClhsdbFindPC.java - did you mean somewhere else? >> >> Thanks, >> Nick >> > Oh, sorry. For some reason I thought it was in the lib directory with > LingeredApp. Yes, it's good the way it is. I'm still happy with this patch to go in after these changes. 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 chris.plummer at oracle.com Mon Aug 12 20:45:02 2019 From: chris.plummer at oracle.com (Chris Plummer) Date: Mon, 12 Aug 2019 13:45:02 -0700 Subject: [aarch64-port-dev ] RFR: 8229118: [TESTBUG] serviceability/sa/ClhsdbFindPC fails on AArch64 In-Reply-To: <5071d6c9-73f8-4c7d-4ae8-3b3d1bcddf82@arm.com> References: <4a646485-4230-9632-dfd4-4368d79ba4cd@arm.com> <39f8fd3f-fcce-0200-3922-33405978e297@redhat.com> <5071d6c9-73f8-4c7d-4ae8-3b3d1bcddf82@arm.com> Message-ID: Hi Nick, Adding to Andrew comments, maybe the solution is to have the test extend LingeredApp so it can produce a more reliable stack trace other than the default one you get with LingeredApp. If that's too much trouble, I don't mind the solution you came up with, but seems writing a LingeredApp subclass that is specific for this test would be cleaner. thanks, Chris On 8/12/19 3:24 AM, Nick Gasson wrote: > Thanks Andrew. Can someone from the serviceability team check this is > OK to push? > > Nick > > > On 08/08/2019 18:16, Andrew Dinn wrote: >> Hi Nick, >> >> On 08/08/2019 10:32, Nick Gasson wrote: >>> Bug: https://bugs.openjdk.java.net/browse/JDK-8229118 >>> Webrev: http://cr.openjdk.java.net/~ngasson/8229118/webrev.0/ >>> >>> This test starts a sub-process with -Xcomp and then uses the SA to >>> get a >>> stack trace of it. It expects to see this line: >>> >>> ?? In code in NMethod for jdk/test/lib/apps/LingeredApp.main >>> >>> But actually on AArch64 the stack trace looks like this: >>> >>> ? - java.lang.Thread.sleep(long) @bci=0, pc=0x0000ffff74603d08, >>> Method*=0x0000ffff031baf98 (Compiled frame; information may be >>> imprecise) >>> ? - jdk.test.lib.apps.LingeredApp.main(java.lang.String[]) @bci=53, >>> line=502, pc=0x0000ffff6c9276e0, Method*=0x0000ffff03611d48 >>> (Interpreted frame) >>> >>> The main method is interpreted even though we're running with >>> -Xcomp. That's because it is deoptimized almost immediately, because >>> main calls some methods on java.nio.file.Paths, but that class hasn't >>> been loaded when main is compiled. >>> >>> X86 can patch in the address of the method on-the-fly, but AArch64 >>> can't >>> do this because of restrictions on which instructions can be legally >>> rewritten. >>> >>> This patch lifts the code that uses the java.nio classes out of >>> LingeredApp::main into a separate static method. LingeredApp.main now >>> only uses classes that are loaded very early in boot, before main is >>> compiled. The stack trace now looks like: >>> >>> "main" #1 prio=5 tid=0x0000ffffb4022800 nid=0xd610 waiting on >>> condition [0x0000ffffbb755000] >>> ??? java.lang.Thread.State: TIMED_WAITING (sleeping) >>> ??? JavaThread state: _thread_blocked >>> ? - java.lang.Thread.sleep(long) @bci=0, pc=0x0000fffface414c8, >>> Method*=0x0000ffff3dac8a28 (Compiled frame; information may be >>> imprecise) >>> ? - jdk.test.lib.apps.LingeredApp.pollLockFile(java.lang.String) >>> @bci=30, line=499, pc=0x0000ffffa50818e0, Method*=0x0000ffff3c122cf0 >>> (Interpreted frame) >>> ? - jdk.test.lib.apps.LingeredApp.main(java.lang.String[]) @bci=25, >>> line=529, pc=0x0000ffffa59afd58, Method*=0x0000ffff3c122de0 >>> (Compiled frame) >>> >>> I.e. pollLockFile was deoptimized to an interpreted frame but >>> LingeredApp.main is still a compiled frame which is what >>> ClhsdbFindPC is >>> looking for. >>> >>> This solution does seem a bit hacky, so if it's not acceptable an >>> alternative is to just skip the -Xcomp part of the test on AArch64. >>> >>> Ran a full jtreg test on AArch64/x86 to check for regressions. >> Yuck! That's a nice hack to avoid the indeterminate effect of -Xcomp. >> However, my gut feeling is still that relying on -Xcomp in tests is just >> a /really/ bad idea and I'd prefer to omit it but . . . >> >> I'm not 100% clear what the point of this test is but it looks like it >> is meant to exercise the stack backtrace code when there is a compiled >> method on the stack. If so then I guess your hack fits the bill while >> removing the -Xcomp flag from the command line would not fulfil the >> test's remit. If that is the point of the test then I agree, >> reluctantly, that your hack is the right solution. On those grounds I'm >> happy to accept the patch. However, I'd prefer someone else (Andrew >> Haley?) also to review this before it gets pushed. >> >> 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 Mon Aug 5 16:29:36 2019 From: adinn at redhat.com (Andrew Dinn) Date: Mon, 5 Aug 2019 17:29:36 +0100 Subject: [aarch64-port-dev ] 8u-aarch64: Backport 8163363: AArch64: Stack size in tools/launcher/Settings.java needs to be adjusted In-Reply-To: References: Message-ID: Apologies: the original note should have been sent to aarch64-port-dev. I have directed this follow up there and bcced 8u-dev to explain why it is disappearing. Also, note changed subject line . On 05/08/2019 17:23, Andrew Dinn wrote: > I would like permission to backport this fix to the > jdk8u-aarch64-shenandoah repo. This fixes the minimum stack size used by > jdk/test/tools/launcher/Settings.java so that it is large enough to > allow the test to pass on AArch64 implementations where it previously > failed. > > The backport requires a minor tweak to the original patch as per the > following webrev: > > http://cr.openjdk.java.net/~adinn/8163363-jdk8u/webrev.00/ > > 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 > -- 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 chris.plummer at oracle.com Tue Aug 13 16:55:51 2019 From: chris.plummer at oracle.com (Chris Plummer) Date: Tue, 13 Aug 2019 09:55:51 -0700 Subject: [aarch64-port-dev ] RFR: 8229118: [TESTBUG] serviceability/sa/ClhsdbFindPC fails on AArch64 In-Reply-To: <178290d1-7904-d59e-3f64-3f57a51ac071@arm.com> References: <4a646485-4230-9632-dfd4-4368d79ba4cd@arm.com> <39f8fd3f-fcce-0200-3922-33405978e297@redhat.com> <5071d6c9-73f8-4c7d-4ae8-3b3d1bcddf82@arm.com> <178290d1-7904-d59e-3f64-3f57a51ac071@arm.com> Message-ID: On 8/13/19 2:38 AM, Nick Gasson wrote: > Hi Chris, > >> >> Adding to Andrew comments, maybe the solution is to have the test extend >> LingeredApp so it can produce a more reliable stack trace other than the >> default one you get with LingeredApp. If that's too much trouble, I >> don't mind the solution you came up with, but seems writing a >> LingeredApp subclass that is specific for this test would be cleaner. > > Thanks for the suggestion, this does seem much cleaner. Please check > the updated webrev here: > > http://cr.openjdk.java.net/~ngasson/8229118/webrev.1/ > > Thanks, > Nick The changes look good, although I think the new file should go in the serviceability/sa test directory, unless you think this is a generally useful class that might be used by tests outside of the sa. thanks, Chris From chris.plummer at oracle.com Wed Aug 14 02:28:52 2019 From: chris.plummer at oracle.com (Chris Plummer) Date: Tue, 13 Aug 2019 19:28:52 -0700 Subject: [aarch64-port-dev ] RFR: 8229118: [TESTBUG] serviceability/sa/ClhsdbFindPC fails on AArch64 In-Reply-To: References: <4a646485-4230-9632-dfd4-4368d79ba4cd@arm.com> <39f8fd3f-fcce-0200-3922-33405978e297@redhat.com> <5071d6c9-73f8-4c7d-4ae8-3b3d1bcddf82@arm.com> <178290d1-7904-d59e-3f64-3f57a51ac071@arm.com> Message-ID: <04ae9472-05e5-91a9-b986-428806a7ee15@oracle.com> On 8/13/19 6:26 PM, Nick Gasson wrote: > Hi Chris, > >> The changes look good, although I think the new file should go in the >> serviceability/sa test directory, unless you think this is a generally >> useful class that might be used by tests outside of the sa. >> > > The new file is under test/hotspot/jtreg/serviceability/sa/ - the same > directory as ClhsdbFindPC.java - did you mean somewhere else? > > Thanks, > Nick > Oh, sorry. For some reason I thought it was in the lib directory with LingeredApp. Yes, it's good the way it is. thanks, Chris From adinn at redhat.com Wed Aug 14 12:59:04 2019 From: adinn at redhat.com (Andrew Dinn) Date: Wed, 14 Aug 2019 13:59:04 +0100 Subject: [aarch64-port-dev ] RFR: [8u] 8213134: AArch64: vector shift failed with MaxVectorSize=8 Message-ID: Can I please have a review of the following AArch64-specific backport to jdk8u-shenandoah. The meat of this patch is a change to aarch64.ad which applied without needing any tweaks. However, the original patch included modifications to existing tests whereas this patch had to introduce those tests as new tests. webrev: http://cr.openjdk.java.net/~adinn/8213134-jdk8u/webrev.00 Testing: new hotspot vector tests fail before and complete after patch otherwise hotspot tests complete as before 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 Wed Aug 14 13:31:08 2019 From: aph at redhat.com (Andrew Haley) Date: Wed, 14 Aug 2019 14:31:08 +0100 Subject: [aarch64-port-dev ] RFR: [8u] 8213134: AArch64: vector shift failed with MaxVectorSize=8 In-Reply-To: References: Message-ID: On 8/14/19 1:59 PM, Andrew Dinn wrote: > Can I please have a review of the following AArch64-specific backport to > jdk8u-shenandoah. The meat of this patch is a change to aarch64.ad which > applied without needing any tweaks. However, the original patch included > modifications to existing tests whereas this patch had to introduce > those tests as new tests. > > webrev: http://cr.openjdk.java.net/~adinn/8213134-jdk8u/webrev.00 > > Testing: > new hotspot vector tests fail before and complete after patch > otherwise hotspot tests complete as before That looks fine, thanks. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From adinn at redhat.com Wed Aug 14 13:47:18 2019 From: adinn at redhat.com (Andrew Dinn) Date: Wed, 14 Aug 2019 14:47:18 +0100 Subject: [aarch64-port-dev ] RFR: [8u] 8213134: AArch64: vector shift failed with MaxVectorSize=8 In-Reply-To: References: Message-ID: On 14/08/2019 14:31, Andrew Haley wrote: > On 8/14/19 1:59 PM, Andrew Dinn wrote: >> Can I please have a review of the following AArch64-specific backport to >> jdk8u-shenandoah. The meat of this patch is a change to aarch64.ad which >> applied without needing any tweaks. However, the original patch included >> modifications to existing tests whereas this patch had to introduce >> those tests as new tests. >> >> webrev: http://cr.openjdk.java.net/~adinn/8213134-jdk8u/webrev.00 >> >> Testing: >> new hotspot vector tests fail before and complete after patch >> otherwise hotspot tests complete as before > > That looks fine, thanks. Thanks. I should have said I a still waiting on an ack for the upstream 11u fix request which I will need before it can go into 8u. Associated JIRA: https://bugs.openjdk.java.net/browse/JDK-8213134 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 Wed Aug 14 14:48:10 2019 From: aph at redhat.com (Andrew Haley) Date: Wed, 14 Aug 2019 15:48:10 +0100 Subject: [aarch64-port-dev ] RFR: [8u] 8213134: AArch64: vector shift failed with MaxVectorSize=8 In-Reply-To: References: Message-ID: On 8/14/19 2:47 PM, Andrew Dinn wrote: > I should have said I a still waiting on an ack for the upstream 11u fix > request which I will need before it can go into 8u. Done. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From adinn at redhat.com Wed Aug 14 15:42:36 2019 From: adinn at redhat.com (adinn at redhat.com) Date: Wed, 14 Aug 2019 15:42:36 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 8213134: AArch64: vector shift failed with MaxVectorSize=8 Message-ID: <201908141542.x7EFgaFj015113@aojmv0008.oracle.com> Changeset: 9705bb429d01 Author: yzhang Date: 2019-08-14 09:30 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/9705bb429d01 8213134: AArch64: vector shift failed with MaxVectorSize=8 Summary: add vshiftcnt instructions for vector64 and add vsra/vsrl instructions to AArch64 backend. To detect shift failures, MaxVectorSize options are added to jtreg test cases. Reviewed-by: aph, kvn ! src/cpu/aarch64/vm/aarch64.ad + test/compiler/c2/cr6340864/TestByteVect.java + test/compiler/c2/cr6340864/TestDoubleVect.java + test/compiler/c2/cr6340864/TestFloatVect.java + test/compiler/c2/cr6340864/TestIntVect.java + test/compiler/c2/cr6340864/TestLongVect.java + test/compiler/c2/cr6340864/TestShortVect.java + test/compiler/codegen/TestCharVect2.java From ci_notify at linaro.org Thu Aug 15 02:42:50 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Thu, 15 Aug 2019 02:42:50 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <184916491.963.1565836971010.JavaMail.jenkins@9a480cea2ca5> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2019/226/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/11 pass: 5,696; fail: 3 Build 1: aarch64/2019/jul/12 pass: 5,695; fail: 5 Build 2: aarch64/2019/jul/15 pass: 5,699; fail: 1 Build 3: aarch64/2019/jul/17 pass: 5,700; fail: 1; error: 1 Build 4: aarch64/2019/jul/19 pass: 5,699; fail: 3; error: 1 Build 5: aarch64/2019/jul/22 pass: 5,705; fail: 2 Build 6: aarch64/2019/jul/24 pass: 5,706; fail: 1 Build 7: aarch64/2019/jul/26 pass: 5,707; fail: 2 Build 8: aarch64/2019/jul/29 pass: 5,705; fail: 4 Build 9: aarch64/2019/jul/31 pass: 5,711; fail: 1 Build 10: aarch64/2019/aug/02 pass: 5,711; fail: 2 Build 11: aarch64/2019/aug/05 pass: 5,712; fail: 1 Build 12: aarch64/2019/aug/07 pass: 5,711; fail: 1 Build 13: aarch64/2019/aug/12 pass: 5,713; fail: 2 Build 14: aarch64/2019/aug/14 pass: 5,717; fail: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/11 pass: 8,598; fail: 529; error: 31 Build 1: aarch64/2019/jul/12 pass: 8,601; fail: 528; error: 29 Build 2: aarch64/2019/jul/15 pass: 8,602; fail: 533; error: 25 Build 3: aarch64/2019/jul/17 pass: 8,614; fail: 522; error: 24 Build 4: aarch64/2019/jul/19 pass: 8,611; fail: 526; error: 26 Build 5: aarch64/2019/jul/22 pass: 8,628; fail: 511; error: 24 Build 6: aarch64/2019/jul/24 pass: 8,617; fail: 538; error: 26 Build 7: aarch64/2019/jul/26 pass: 8,649; fail: 518; error: 17 Build 8: aarch64/2019/jul/29 pass: 8,640; fail: 520; error: 26 Build 9: aarch64/2019/jul/31 pass: 8,640; fail: 526; error: 24 Build 10: aarch64/2019/aug/02 pass: 8,637; fail: 524; error: 29 Build 11: aarch64/2019/aug/05 pass: 8,642; fail: 519; error: 29 Build 12: aarch64/2019/aug/07 pass: 8,638; fail: 529; error: 23 Build 13: aarch64/2019/aug/12 pass: 8,659; fail: 515; error: 19 Build 14: aarch64/2019/aug/14 pass: 8,674; fail: 505; error: 19 3 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/11 pass: 3,968 Build 1: aarch64/2019/jul/12 pass: 3,968 Build 2: aarch64/2019/jul/15 pass: 3,968 Build 3: aarch64/2019/jul/17 pass: 3,968 Build 4: aarch64/2019/jul/19 pass: 3,969 Build 5: aarch64/2019/jul/22 pass: 3,969 Build 6: aarch64/2019/jul/24 pass: 3,970 Build 7: aarch64/2019/jul/26 pass: 3,970 Build 8: aarch64/2019/jul/29 pass: 3,970 Build 9: aarch64/2019/jul/31 pass: 3,970 Build 10: aarch64/2019/aug/02 pass: 3,970 Build 11: aarch64/2019/aug/05 pass: 3,970 Build 12: aarch64/2019/aug/07 pass: 3,970 Build 13: aarch64/2019/aug/12 pass: 3,970 Build 14: aarch64/2019/aug/14 pass: 3,972 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.84x Relative performance: Server critical-jOPS (nc): 9.20x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 190.74 Server 190.74 / Server 2014-04-01 (71.00): 2.69x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-01-01 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/365/results/ 2019-07-12 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/192/results/ 2019-07-15 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/196/results/ 2019-07-17 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/198/results/ 2019-07-20 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/200/results/ 2019-07-22 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/203/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/205/results/ 2019-07-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/207/results/ 2019-07-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/210/results/ 2019-08-01 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/212/results/ 2019-08-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/214/results/ 2019-08-06 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/217/results/ 2019-08-08 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/219/results/ 2019-08-13 pass rate: 10487/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/224/results/ 2019-08-15 pass rate: 10488/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/226/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From nick.gasson at arm.com Thu Aug 15 06:54:45 2019 From: nick.gasson at arm.com (Nick Gasson) Date: Thu, 15 Aug 2019 14:54:45 +0800 Subject: [aarch64-port-dev ] RFR: 8229118: [TESTBUG] serviceability/sa/ClhsdbFindPC fails on AArch64 In-Reply-To: <4c9f5bb8-2a67-258e-9b65-acc91237055f@redhat.com> References: <4a646485-4230-9632-dfd4-4368d79ba4cd@arm.com> <39f8fd3f-fcce-0200-3922-33405978e297@redhat.com> <5071d6c9-73f8-4c7d-4ae8-3b3d1bcddf82@arm.com> <178290d1-7904-d59e-3f64-3f57a51ac071@arm.com> <04ae9472-05e5-91a9-b986-428806a7ee15@oracle.com> <4c9f5bb8-2a67-258e-9b65-acc91237055f@redhat.com> Message-ID: Thanks Andrew and Chris. Pushed here: https://hg.openjdk.java.net/jdk/jdk/rev/902cef494e66 Nick On 14/08/2019 16:10, Andrew Dinn wrote: > On 14/08/2019 03:28, Chris Plummer wrote: >> On 8/13/19 6:26 PM, Nick Gasson wrote: >>> Hi Chris, >>> >>>> The changes look good, although I think the new file should go in the >>>> serviceability/sa test directory, unless you think this is a generally >>>> useful class that might be used by tests outside of the sa. >>>> >>> >>> The new file is under test/hotspot/jtreg/serviceability/sa/ - the same >>> directory as ClhsdbFindPC.java - did you mean somewhere else? >>> >>> Thanks, >>> Nick >>> >> Oh, sorry. For some reason I thought it was in the lib directory with >> LingeredApp. Yes, it's good the way it is. > I'm still happy with this patch to go in after these changes. > > 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 Thu Aug 15 21:12:13 2019 From: gnu.andrew at redhat.com (Andrew John Hughes) Date: Thu, 15 Aug 2019 22:12:13 +0100 Subject: [aarch64-port-dev ] [RFR] [8u] 8u232-b03 Upstream Sync Message-ID: <38d82ead-65a1-9091-8afa-a47c4510de93@redhat.com> Webrevs: https://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/ Merge changesets: http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/corba/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/jaxp/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/jaxws/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/jdk/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/hotspot/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/langtools/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/nashorn/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/root/merge.changeset Changes in aarch64-shenandoah-jdk8u232-b03: - S8163363: AArch64: Stack size in tools/launcher/Settings.java needs to be adjusted - S8205421: AARCH64: StubCodeMark should be placed after alignment - S8213561: ZipFile/MultiThreadedReadTest.java timed out in tier1 - S8217785: Padding ParallelTaskTerminator::_offered_termination variable - S8219011: Implement MacroAssembler::warn method on AArch64 - S8228400: Remove built-in AArch64 simulator - S8228593: Revert explicit JDK 7 support additions - S8228716: Revert InstanceKlass::print_on debug additions - S8228718: Revert incorrect backport of JDK-8129757 to 8-aarch64 - S8228746: Revert incorrect StubRoutines::contains change - S8228747: Revert "unused" attribute from test_arraycopy_func - S8228767: Revert ResourceMark additions - S8228770: Revert development hsdis changes - S8229123: Revert build fixes for aarch64/zero - S8229124: Revert disassembler.cpp changes - S8229145: Revert TemplateTable::bytecode() visibility change Main issues of note: All changes but 8213561 & 8217785 are already upstream, hence the unlisted changes in the webrev. Check the HotSpot and JDK merge.changeset files for the actual changes. diffstat for root b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for corba b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for jaxp b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for jaxws b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for langtools b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for nashorn b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for jdk b/.hgtags | 1 b/test/java/util/zip/ZipFile/MultiThreadedReadTest.java | 39 +++++++++++----- 2 files changed, 28 insertions(+), 12 deletions(-) diffstat for hotspot b/.hgtags | 1 + b/src/share/vm/utilities/taskqueue.hpp | 3 +++ 2 files changed, 4 insertions(+) Successfully built on x86, x86_64, s390, s390x, ppc, ppc64, ppc64le & aarch64. Ok to push? -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 https://keybase.io/gnu_andrew From shade at redhat.com Thu Aug 15 21:21:32 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Thu, 15 Aug 2019 23:21:32 +0200 Subject: [aarch64-port-dev ] [RFR] [8u] 8u232-b03 Upstream Sync In-Reply-To: <38d82ead-65a1-9091-8afa-a47c4510de93@redhat.com> References: <38d82ead-65a1-9091-8afa-a47c4510de93@redhat.com> Message-ID: <380a4823-298b-3d24-42d5-95f8b4f53327@redhat.com> On 8/15/19 11:12 PM, Andrew John Hughes wrote: > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/corba/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/jaxp/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/jaxws/merge.changeset Trivially good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/jdk/merge.changeset Looks good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/hotspot/merge.changeset Looks good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/langtools/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/nashorn/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/root/merge.changeset Trivially good. Thumbs up! -Aleksey From gnu.andrew at redhat.com Thu Aug 15 21:37:39 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Thu, 15 Aug 2019 21:37:39 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah: 3 new changesets Message-ID: <201908152137.x7FLbdm1024863@aojmv0008.oracle.com> Changeset: 9611ccdff5fe Author: andrew Date: 2019-08-09 00:10 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/9611ccdff5fe Added tag jdk8u232-b03 for changeset c5ca527b0afd ! .hgtags Changeset: 95a4de8376e2 Author: andrew Date: 2019-08-10 13:08 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/95a4de8376e2 Merge jdk8u232-b03 ! .hgtags Changeset: c30ac26944aa Author: andrew Date: 2019-08-10 13:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/c30ac26944aa Added tag aarch64-shenandoah-jdk8u232-b03 for changeset 95a4de8376e2 ! .hgtags From gnu.andrew at redhat.com Thu Aug 15 21:37:47 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Thu, 15 Aug 2019 21:37:47 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/corba: 3 new changesets Message-ID: <201908152137.x7FLblXd024970@aojmv0008.oracle.com> Changeset: 1447921be802 Author: andrew Date: 2019-08-09 00:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/1447921be802 Added tag jdk8u232-b03 for changeset 8ce5d3e4f0b4 ! .hgtags Changeset: 333b919f1035 Author: andrew Date: 2019-08-10 13:08 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/333b919f1035 Merge jdk8u232-b03 ! .hgtags Changeset: 1fcc0dd702ce Author: andrew Date: 2019-08-10 13:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/1fcc0dd702ce Added tag aarch64-shenandoah-jdk8u232-b03 for changeset 333b919f1035 ! .hgtags From gnu.andrew at redhat.com Thu Aug 15 21:37:56 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Thu, 15 Aug 2019 21:37:56 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxp: 3 new changesets Message-ID: <201908152137.x7FLbvwm025072@aojmv0008.oracle.com> Changeset: cf6d61173105 Author: andrew Date: 2019-08-09 00:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/cf6d61173105 Added tag jdk8u232-b03 for changeset 271cd29281ff ! .hgtags Changeset: 52eb30281876 Author: andrew Date: 2019-08-10 13:08 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/52eb30281876 Merge jdk8u232-b03 ! .hgtags Changeset: 8e433e884933 Author: andrew Date: 2019-08-10 13:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/8e433e884933 Added tag aarch64-shenandoah-jdk8u232-b03 for changeset 52eb30281876 ! .hgtags From gnu.andrew at redhat.com Thu Aug 15 21:38:13 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Thu, 15 Aug 2019 21:38:13 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/langtools: 3 new changesets Message-ID: <201908152138.x7FLcDWv025754@aojmv0008.oracle.com> Changeset: 3de2732a8241 Author: andrew Date: 2019-08-09 00:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/3de2732a8241 Added tag jdk8u232-b03 for changeset 671c4ba50c6f ! .hgtags Changeset: 326c63bdf940 Author: andrew Date: 2019-08-10 13:09 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/326c63bdf940 Merge jdk8u232-b03 ! .hgtags Changeset: 0408661335a7 Author: andrew Date: 2019-08-10 13:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/0408661335a7 Added tag aarch64-shenandoah-jdk8u232-b03 for changeset 326c63bdf940 ! .hgtags From gnu.andrew at redhat.com Thu Aug 15 21:38:29 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Thu, 15 Aug 2019 21:38:29 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jdk: 5 new changesets Message-ID: <201908152138.x7FLcTx9026014@aojmv0008.oracle.com> Changeset: 553561bf25a2 Author: coffeys Date: 2019-06-20 08:02 +0000 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/553561bf25a2 8213561: ZipFile/MultiThreadedReadTest.java timed out in tier1 Reviewed-by: shade ! test/java/util/zip/ZipFile/MultiThreadedReadTest.java Changeset: 60eca04567a6 Author: andrew Date: 2019-08-06 04:37 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/60eca04567a6 Merge Changeset: 3ef3348195ff Author: andrew Date: 2019-08-09 00:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/3ef3348195ff Added tag jdk8u232-b03 for changeset 60eca04567a6 ! .hgtags Changeset: f8dd5ee68aeb Author: andrew Date: 2019-08-10 13:09 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f8dd5ee68aeb Merge jdk8u232-b03 ! .hgtags Changeset: 9108d5974fc9 Author: andrew Date: 2019-08-10 13:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/9108d5974fc9 Added tag aarch64-shenandoah-jdk8u232-b03 for changeset f8dd5ee68aeb ! .hgtags From gnu.andrew at redhat.com Thu Aug 15 21:38:04 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Thu, 15 Aug 2019 21:38:04 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxws: 3 new changesets Message-ID: <201908152138.x7FLc4qo025675@aojmv0008.oracle.com> Changeset: d8ecedf2321b Author: andrew Date: 2019-08-09 00:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/d8ecedf2321b Added tag jdk8u232-b03 for changeset 28c25aedce28 ! .hgtags Changeset: 46b592a5f3d3 Author: andrew Date: 2019-08-10 13:09 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/46b592a5f3d3 Merge jdk8u232-b03 ! .hgtags Changeset: 1ff11a64c695 Author: andrew Date: 2019-08-10 13:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/1ff11a64c695 Added tag aarch64-shenandoah-jdk8u232-b03 for changeset 46b592a5f3d3 ! .hgtags From gnu.andrew at redhat.com Thu Aug 15 21:38:36 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Thu, 15 Aug 2019 21:38:36 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/nashorn: 3 new changesets Message-ID: <201908152138.x7FLcbOl026810@aojmv0008.oracle.com> Changeset: 41756665474f Author: andrew Date: 2019-08-09 00:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/41756665474f Added tag jdk8u232-b03 for changeset 7979e4a31f24 ! .hgtags Changeset: f9fb5bfeb323 Author: andrew Date: 2019-08-10 13:09 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/f9fb5bfeb323 Merge jdk8u232-b03 ! .hgtags Changeset: 8e10f6540b18 Author: andrew Date: 2019-08-10 13:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/8e10f6540b18 Added tag aarch64-shenandoah-jdk8u232-b03 for changeset f9fb5bfeb323 ! .hgtags From gnu.andrew at redhat.com Thu Aug 15 21:40:42 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Thu, 15 Aug 2019 21:40:42 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 5 new changesets Message-ID: <201908152140.x7FLeh7B028330@aojmv0008.oracle.com> Changeset: fa7fe6dae563 Author: zgu Date: 2019-01-29 08:28 -0500 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/fa7fe6dae563 8217785: Padding ParallelTaskTerminator::_offered_termination variable Reviewed-by: shade, tschatzl ! src/share/vm/utilities/taskqueue.hpp Changeset: 7576bbd5a03c Author: andrew Date: 2019-08-09 00:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/7576bbd5a03c Added tag jdk8u232-b03 for changeset fa7fe6dae563 ! .hgtags Changeset: b66728ac7416 Author: andrew Date: 2019-08-10 13:09 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/b66728ac7416 Merge jdk8u232-b03 ! .hgtags ! src/share/vm/utilities/taskqueue.hpp Changeset: 0420b6f98827 Author: andrew Date: 2019-08-10 13:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/0420b6f98827 Added tag aarch64-shenandoah-jdk8u232-b03 for changeset b66728ac7416 ! .hgtags Changeset: 7ee409c43b6e Author: andrew Date: 2019-08-15 22:40 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/7ee409c43b6e Merge From gnu.andrew at redhat.com Thu Aug 15 21:42:36 2019 From: gnu.andrew at redhat.com (Andrew John Hughes) Date: Thu, 15 Aug 2019 22:42:36 +0100 Subject: [aarch64-port-dev ] [RFR] [8u] 8u232-b03 Upstream Sync In-Reply-To: <380a4823-298b-3d24-42d5-95f8b4f53327@redhat.com> References: <38d82ead-65a1-9091-8afa-a47c4510de93@redhat.com> <380a4823-298b-3d24-42d5-95f8b4f53327@redhat.com> Message-ID: <0012353b-18a4-8170-c66b-f952aa1c586b@redhat.com> On 15/08/2019 22:21, Aleksey Shipilev wrote: > On 8/15/19 11:12 PM, Andrew John Hughes wrote: >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/corba/merge.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/jaxp/merge.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/jaxws/merge.changeset > > Trivially good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/jdk/merge.changeset > > Looks good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/hotspot/merge.changeset > > Looks good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/langtools/merge.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/nashorn/merge.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b03/root/merge.changeset > > Trivially good. > > Thumbs up! > > -Aleksey > And all pushed. Thanks, -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 https://keybase.io/gnu_andrew From ci_notify at linaro.org Fri Aug 16 10:50:24 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 16 Aug 2019 10:50:24 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 11u on AArch64 Message-ID: <2000530247.1216.1565952624675.JavaMail.javamailuser@localhost> 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/jdk11u/openjdk-jtreg-nightly-tests/summary/2019/227/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/16 pass: 5,721; fail: 8; not run: 11,618 Build 1: aarch64/2019/mar/19 pass: 5,721; fail: 9; not run: 11,618 Build 2: aarch64/2019/mar/28 pass: 5,722; fail: 8; not run: 11,618 Build 3: aarch64/2019/apr/02 pass: 5,723; fail: 8; not run: 11,618 Build 4: aarch64/2019/apr/04 pass: 5,722; fail: 9; not run: 11,618 Build 5: aarch64/2019/apr/18 pass: 5,723; fail: 8; not run: 11,618 Build 6: aarch64/2019/may/16 pass: 5,734; fail: 5; not run: 11,623 Build 7: aarch64/2019/may/25 pass: 5,735; fail: 5; not run: 11,623 Build 8: aarch64/2019/jun/05 pass: 5,737; fail: 5; not run: 11,623 Build 9: aarch64/2019/jun/15 pass: 5,737; fail: 5; not run: 11,623 Build 10: aarch64/2019/jun/27 pass: 5,737; fail: 5 Build 11: aarch64/2019/jul/02 pass: 5,737; fail: 5 Build 12: aarch64/2019/aug/03 pass: 5,746; fail: 4 Build 13: aarch64/2019/aug/10 pass: 5,747; fail: 4 Build 14: aarch64/2019/aug/15 pass: 5,753; fail: 4 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/16 pass: 8,397; fail: 497; error: 22 Build 1: aarch64/2019/mar/19 pass: 8,365; fail: 527; error: 24 Build 2: aarch64/2019/mar/28 pass: 8,374; fail: 521; error: 21 Build 3: aarch64/2019/apr/02 pass: 8,354; fail: 536; error: 26 Build 4: aarch64/2019/apr/04 pass: 8,382; fail: 510; error: 24 Build 5: aarch64/2019/apr/18 pass: 8,398; fail: 501; error: 19 Build 6: aarch64/2019/may/16 pass: 8,397; fail: 514; error: 22 Build 7: aarch64/2019/may/25 pass: 8,403; fail: 511; error: 21 Build 8: aarch64/2019/jun/05 pass: 8,427; fail: 489; error: 19 Build 9: aarch64/2019/jun/15 pass: 8,409; fail: 506; error: 20 Build 10: aarch64/2019/jun/27 pass: 8,401; fail: 512; error: 22 Build 11: aarch64/2019/jul/02 pass: 8,407; fail: 498; error: 31 Build 12: aarch64/2019/aug/03 pass: 8,429; fail: 509; error: 18 Build 13: aarch64/2019/aug/10 pass: 8,450; fail: 485; error: 16 Build 14: aarch64/2019/aug/15 pass: 8,443; fail: 496; error: 13 4 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/16 pass: 3,904 Build 1: aarch64/2019/mar/19 pass: 3,904 Build 2: aarch64/2019/mar/28 pass: 3,904 Build 3: aarch64/2019/apr/02 pass: 3,904 Build 4: aarch64/2019/apr/04 pass: 3,904 Build 5: aarch64/2019/apr/18 pass: 3,904 Build 6: aarch64/2019/may/16 pass: 3,908 Build 7: aarch64/2019/may/25 pass: 3,908 Build 8: aarch64/2019/jun/05 pass: 3,908 Build 9: aarch64/2019/jun/15 pass: 3,908 Build 10: aarch64/2019/jun/27 pass: 3,908 Build 11: aarch64/2019/jul/02 pass: 3,908 Build 12: aarch64/2019/aug/03 pass: 3,908 Build 13: aarch64/2019/aug/10 pass: 3,909 Build 14: aarch64/2019/aug/15 pass: 3,909 Previous results can be found here: http://openjdk.linaro.org/jdk11u/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.83x Relative performance: Server critical-jOPS (nc): 8.18x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk11u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 204.57 Server 204.57 / Server 2014-04-01 (71.00): 2.88x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk11u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-03-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/075/results/ 2019-03-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/078/results/ 2019-03-29 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/087/results/ 2019-04-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/092/results/ 2019-04-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/094/results/ 2019-04-19 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/108/results/ 2019-05-17 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/136/results/ 2019-05-26 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/145/results/ 2019-06-05 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/156/results/ 2019-06-16 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/166/results/ 2019-06-28 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/178/results/ 2019-07-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/183/results/ 2019-08-04 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/215/results/ 2019-08-11 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/222/results/ 2019-08-16 pass rate: 10489/10489, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/227/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/ From ci_notify at linaro.org Fri Aug 16 10:53:46 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 16 Aug 2019 10:53:46 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <1765014824.1218.1565952827261.JavaMail.javamailuser@localhost> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/summary/2019/227/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/apr/30 pass: 797; fail: 23; error: 9 Build 1: aarch64/2019/may/02 pass: 814; fail: 14; error: 2 Build 2: aarch64/2019/jun/15 pass: 815; fail: 22; error: 1 Build 3: aarch64/2019/jun/20 pass: 820; fail: 16; error: 2 Build 4: aarch64/2019/jun/29 pass: 807; fail: 25; error: 6 Build 5: aarch64/2019/jul/19 pass: 814; fail: 20; error: 4 Build 6: aarch64/2019/jul/25 pass: 802; fail: 25; error: 11 Build 7: aarch64/2019/jul/30 pass: 787; fail: 40; error: 11 Build 8: aarch64/2019/aug/01 pass: 800; fail: 26; error: 12 Build 9: aarch64/2019/aug/04 pass: 808; fail: 30; error: 2 Build 10: aarch64/2019/aug/06 pass: 799; fail: 29; error: 12 Build 11: aarch64/2019/aug/08 pass: 830; fail: 9; error: 1 Build 12: aarch64/2019/aug/11 pass: 825; fail: 14; error: 1 Build 13: aarch64/2019/aug/13 pass: 830; fail: 9; error: 1 Build 14: aarch64/2019/aug/15 pass: 837; fail: 9; error: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/apr/30 pass: 5,779; fail: 262; error: 27 Build 1: aarch64/2019/may/02 pass: 5,784; fail: 262; error: 22 Build 2: aarch64/2019/jun/15 pass: 5,827; fail: 242; error: 22 Build 3: aarch64/2019/jun/20 pass: 5,821; fail: 244; error: 26 Build 4: aarch64/2019/jun/29 pass: 5,799; fail: 265; error: 27 Build 5: aarch64/2019/jul/19 pass: 5,940; fail: 278; error: 22 Build 6: aarch64/2019/jul/25 pass: 5,938; fail: 276; error: 26 Build 7: aarch64/2019/jul/30 pass: 5,942; fail: 273; error: 25 Build 8: aarch64/2019/aug/01 pass: 5,945; fail: 271; error: 24 Build 9: aarch64/2019/aug/04 pass: 5,949; fail: 270; error: 24 Build 10: aarch64/2019/aug/06 pass: 5,945; fail: 275; error: 23 Build 11: aarch64/2019/aug/08 pass: 5,953; fail: 267; error: 23 Build 12: aarch64/2019/aug/11 pass: 5,947; fail: 272; error: 25 Build 13: aarch64/2019/aug/13 pass: 5,962; fail: 258; error: 24 Build 14: aarch64/2019/aug/15 pass: 5,955; fail: 266; error: 23 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/apr/30 pass: 3,115; fail: 2 Build 1: aarch64/2019/may/02 pass: 3,115; fail: 2 Build 2: aarch64/2019/jun/15 pass: 3,116; fail: 2 Build 3: aarch64/2019/jun/20 pass: 3,116; fail: 2 Build 4: aarch64/2019/jun/29 pass: 3,116; fail: 2 Build 5: aarch64/2019/jul/19 pass: 3,116; fail: 2 Build 6: aarch64/2019/jul/25 pass: 3,116; fail: 2 Build 7: aarch64/2019/jul/30 pass: 3,116; fail: 2 Build 8: aarch64/2019/aug/01 pass: 3,116; fail: 2 Build 9: aarch64/2019/aug/04 pass: 3,116; fail: 2 Build 10: aarch64/2019/aug/06 pass: 3,116; fail: 2 Build 11: aarch64/2019/aug/08 pass: 3,116; fail: 2 Build 12: aarch64/2019/aug/11 pass: 3,116; fail: 2 Build 13: aarch64/2019/aug/13 pass: 3,116; fail: 2 Build 14: aarch64/2019/aug/15 pass: 3,116; fail: 2 Previous results can be found here: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 6.73x Relative performance: Server critical-jOPS (nc): 8.92x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 174.26 Server 174.26 / Server 2014-04-01 (71.00): 2.45x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-04-30 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/120/results/ 2019-05-02 pass rate: 8490/8490, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/122/results/ 2019-06-16 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/166/results/ 2019-06-21 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/171/results/ 2019-06-30 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/180/results/ 2019-07-20 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/200/results/ 2019-07-26 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/211/results/ 2019-08-02 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/213/results/ 2019-08-05 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/216/results/ 2019-08-07 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/218/results/ 2019-08-09 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/220/results/ 2019-08-12 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/223/results/ 2019-08-13 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/225/results/ 2019-08-16 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/227/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From ci_notify at linaro.org Sat Aug 17 05:50:18 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sat, 17 Aug 2019 05:50:18 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <1679987962.1354.1566021019209.JavaMail.javamailuser@localhost> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2019/228/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/12 pass: 5,695; fail: 5 Build 1: aarch64/2019/jul/15 pass: 5,699; fail: 1 Build 2: aarch64/2019/jul/17 pass: 5,700; fail: 1; error: 1 Build 3: aarch64/2019/jul/19 pass: 5,699; fail: 3; error: 1 Build 4: aarch64/2019/jul/22 pass: 5,705; fail: 2 Build 5: aarch64/2019/jul/24 pass: 5,706; fail: 1 Build 6: aarch64/2019/jul/26 pass: 5,707; fail: 2 Build 7: aarch64/2019/jul/29 pass: 5,705; fail: 4 Build 8: aarch64/2019/jul/31 pass: 5,711; fail: 1 Build 9: aarch64/2019/aug/02 pass: 5,711; fail: 2 Build 10: aarch64/2019/aug/05 pass: 5,712; fail: 1 Build 11: aarch64/2019/aug/07 pass: 5,711; fail: 1 Build 12: aarch64/2019/aug/12 pass: 5,713; fail: 2 Build 13: aarch64/2019/aug/14 pass: 5,717; fail: 1 Build 14: aarch64/2019/aug/16 pass: 5,718 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/12 pass: 8,601; fail: 528; error: 29 Build 1: aarch64/2019/jul/15 pass: 8,602; fail: 533; error: 25 Build 2: aarch64/2019/jul/17 pass: 8,614; fail: 522; error: 24 Build 3: aarch64/2019/jul/19 pass: 8,611; fail: 526; error: 26 Build 4: aarch64/2019/jul/22 pass: 8,628; fail: 511; error: 24 Build 5: aarch64/2019/jul/24 pass: 8,617; fail: 538; error: 26 Build 6: aarch64/2019/jul/26 pass: 8,649; fail: 518; error: 17 Build 7: aarch64/2019/jul/29 pass: 8,640; fail: 520; error: 26 Build 8: aarch64/2019/jul/31 pass: 8,640; fail: 526; error: 24 Build 9: aarch64/2019/aug/02 pass: 8,637; fail: 524; error: 29 Build 10: aarch64/2019/aug/05 pass: 8,642; fail: 519; error: 29 Build 11: aarch64/2019/aug/07 pass: 8,638; fail: 529; error: 23 Build 12: aarch64/2019/aug/12 pass: 8,659; fail: 515; error: 19 Build 13: aarch64/2019/aug/14 pass: 8,674; fail: 505; error: 19 Build 14: aarch64/2019/aug/16 pass: 8,673; fail: 506; error: 21 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/12 pass: 3,968 Build 1: aarch64/2019/jul/15 pass: 3,968 Build 2: aarch64/2019/jul/17 pass: 3,968 Build 3: aarch64/2019/jul/19 pass: 3,969 Build 4: aarch64/2019/jul/22 pass: 3,969 Build 5: aarch64/2019/jul/24 pass: 3,970 Build 6: aarch64/2019/jul/26 pass: 3,970 Build 7: aarch64/2019/jul/29 pass: 3,970 Build 8: aarch64/2019/jul/31 pass: 3,970 Build 9: aarch64/2019/aug/02 pass: 3,970 Build 10: aarch64/2019/aug/05 pass: 3,970 Build 11: aarch64/2019/aug/07 pass: 3,970 Build 12: aarch64/2019/aug/12 pass: 3,970 Build 13: aarch64/2019/aug/14 pass: 3,972 Build 14: aarch64/2019/aug/16 pass: 3,972 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.94x Relative performance: Server critical-jOPS (nc): 8.83x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 196.04 Server 196.04 / Server 2014-04-01 (71.00): 2.76x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-01-01 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/365/results/ 2019-07-15 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/196/results/ 2019-07-17 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/198/results/ 2019-07-20 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/200/results/ 2019-07-22 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/203/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/205/results/ 2019-07-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/207/results/ 2019-07-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/210/results/ 2019-08-01 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/212/results/ 2019-08-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/214/results/ 2019-08-06 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/217/results/ 2019-08-08 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/219/results/ 2019-08-13 pass rate: 10487/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/224/results/ 2019-08-15 pass rate: 10488/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/226/results/ 2019-08-17 pass rate: 10488/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/228/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From ci_notify at linaro.org Sat Aug 17 15:01:44 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sat, 17 Aug 2019 15:01:44 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <708376873.1409.1566054105718.JavaMail.javamailuser@localhost> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/summary/2019/229/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/may/02 pass: 814; fail: 14; error: 2 Build 1: aarch64/2019/jun/15 pass: 815; fail: 22; error: 1 Build 2: aarch64/2019/jun/20 pass: 820; fail: 16; error: 2 Build 3: aarch64/2019/jun/29 pass: 807; fail: 25; error: 6 Build 4: aarch64/2019/jul/19 pass: 814; fail: 20; error: 4 Build 5: aarch64/2019/jul/25 pass: 802; fail: 25; error: 11 Build 6: aarch64/2019/jul/30 pass: 787; fail: 40; error: 11 Build 7: aarch64/2019/aug/01 pass: 800; fail: 26; error: 12 Build 8: aarch64/2019/aug/04 pass: 808; fail: 30; error: 2 Build 9: aarch64/2019/aug/06 pass: 799; fail: 29; error: 12 Build 10: aarch64/2019/aug/08 pass: 830; fail: 9; error: 1 Build 11: aarch64/2019/aug/11 pass: 825; fail: 14; error: 1 Build 12: aarch64/2019/aug/13 pass: 830; fail: 9; error: 1 Build 13: aarch64/2019/aug/15 pass: 837; fail: 9; error: 1 Build 14: aarch64/2019/aug/17 pass: 837; fail: 9; error: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/may/02 pass: 5,784; fail: 262; error: 22 Build 1: aarch64/2019/jun/15 pass: 5,827; fail: 242; error: 22 Build 2: aarch64/2019/jun/20 pass: 5,821; fail: 244; error: 26 Build 3: aarch64/2019/jun/29 pass: 5,799; fail: 265; error: 27 Build 4: aarch64/2019/jul/19 pass: 5,940; fail: 278; error: 22 Build 5: aarch64/2019/jul/25 pass: 5,938; fail: 276; error: 26 Build 6: aarch64/2019/jul/30 pass: 5,942; fail: 273; error: 25 Build 7: aarch64/2019/aug/01 pass: 5,945; fail: 271; error: 24 Build 8: aarch64/2019/aug/04 pass: 5,949; fail: 270; error: 24 Build 9: aarch64/2019/aug/06 pass: 5,945; fail: 275; error: 23 Build 10: aarch64/2019/aug/08 pass: 5,953; fail: 267; error: 23 Build 11: aarch64/2019/aug/11 pass: 5,947; fail: 272; error: 25 Build 12: aarch64/2019/aug/13 pass: 5,962; fail: 258; error: 24 Build 13: aarch64/2019/aug/15 pass: 5,955; fail: 266; error: 23 Build 14: aarch64/2019/aug/17 pass: 5,951; fail: 269; error: 24 ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/may/02 pass: 3,115; fail: 2 Build 1: aarch64/2019/jun/15 pass: 3,116; fail: 2 Build 2: aarch64/2019/jun/20 pass: 3,116; fail: 2 Build 3: aarch64/2019/jun/29 pass: 3,116; fail: 2 Build 4: aarch64/2019/jul/19 pass: 3,116; fail: 2 Build 5: aarch64/2019/jul/25 pass: 3,116; fail: 2 Build 6: aarch64/2019/jul/30 pass: 3,116; fail: 2 Build 7: aarch64/2019/aug/01 pass: 3,116; fail: 2 Build 8: aarch64/2019/aug/04 pass: 3,116; fail: 2 Build 9: aarch64/2019/aug/06 pass: 3,116; fail: 2 Build 10: aarch64/2019/aug/08 pass: 3,116; fail: 2 Build 11: aarch64/2019/aug/11 pass: 3,116; fail: 2 Build 12: aarch64/2019/aug/13 pass: 3,116; fail: 2 Build 13: aarch64/2019/aug/15 pass: 3,116; fail: 2 Build 14: aarch64/2019/aug/17 pass: 3,116; fail: 2 Previous results can be found here: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 6.89x Relative performance: Server critical-jOPS (nc): 8.57x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 172.13 Server 172.13 / Server 2014-04-01 (71.00): 2.42x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-05-02 pass rate: 8490/8490, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/122/results/ 2019-06-16 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/166/results/ 2019-06-21 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/171/results/ 2019-06-30 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/180/results/ 2019-07-20 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/200/results/ 2019-07-26 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/211/results/ 2019-08-02 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/213/results/ 2019-08-05 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/216/results/ 2019-08-07 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/218/results/ 2019-08-09 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/220/results/ 2019-08-12 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/223/results/ 2019-08-13 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/225/results/ 2019-08-16 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/227/results/ 2019-08-17 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/229/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From rwestrel at redhat.com Mon Aug 19 14:41:35 2019 From: rwestrel at redhat.com (Roland Westrelin) Date: Mon, 19 Aug 2019 16:41:35 +0200 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency In-Reply-To: References: Message-ID: <87y2zprzds.fsf@redhat.com> > I think this is ok to push. However, I would be happier if Roland could > also check it before you do that. The patch looks reasonable to me. Roland. From ci_notify at linaro.org Tue Aug 20 02:48:55 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Tue, 20 Aug 2019 02:48:55 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <1686565307.1882.1566269335838.JavaMail.javamailuser@localhost> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2019/231/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/15 pass: 5,699; fail: 1 Build 1: aarch64/2019/jul/17 pass: 5,700; fail: 1; error: 1 Build 2: aarch64/2019/jul/19 pass: 5,699; fail: 3; error: 1 Build 3: aarch64/2019/jul/22 pass: 5,705; fail: 2 Build 4: aarch64/2019/jul/24 pass: 5,706; fail: 1 Build 5: aarch64/2019/jul/26 pass: 5,707; fail: 2 Build 6: aarch64/2019/jul/29 pass: 5,705; fail: 4 Build 7: aarch64/2019/jul/31 pass: 5,711; fail: 1 Build 8: aarch64/2019/aug/02 pass: 5,711; fail: 2 Build 9: aarch64/2019/aug/05 pass: 5,712; fail: 1 Build 10: aarch64/2019/aug/07 pass: 5,711; fail: 1 Build 11: aarch64/2019/aug/12 pass: 5,713; fail: 2 Build 12: aarch64/2019/aug/14 pass: 5,717; fail: 1 Build 13: aarch64/2019/aug/16 pass: 5,718 Build 14: aarch64/2019/aug/19 pass: 5,718 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/15 pass: 8,602; fail: 533; error: 25 Build 1: aarch64/2019/jul/17 pass: 8,614; fail: 522; error: 24 Build 2: aarch64/2019/jul/19 pass: 8,611; fail: 526; error: 26 Build 3: aarch64/2019/jul/22 pass: 8,628; fail: 511; error: 24 Build 4: aarch64/2019/jul/24 pass: 8,617; fail: 538; error: 26 Build 5: aarch64/2019/jul/26 pass: 8,649; fail: 518; error: 17 Build 6: aarch64/2019/jul/29 pass: 8,640; fail: 520; error: 26 Build 7: aarch64/2019/jul/31 pass: 8,640; fail: 526; error: 24 Build 8: aarch64/2019/aug/02 pass: 8,637; fail: 524; error: 29 Build 9: aarch64/2019/aug/05 pass: 8,642; fail: 519; error: 29 Build 10: aarch64/2019/aug/07 pass: 8,638; fail: 529; error: 23 Build 11: aarch64/2019/aug/12 pass: 8,659; fail: 515; error: 19 Build 12: aarch64/2019/aug/14 pass: 8,674; fail: 505; error: 19 Build 13: aarch64/2019/aug/16 pass: 8,673; fail: 506; error: 21 Build 14: aarch64/2019/aug/19 pass: 8,676; fail: 503; error: 22 5 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/15 pass: 3,968 Build 1: aarch64/2019/jul/17 pass: 3,968 Build 2: aarch64/2019/jul/19 pass: 3,969 Build 3: aarch64/2019/jul/22 pass: 3,969 Build 4: aarch64/2019/jul/24 pass: 3,970 Build 5: aarch64/2019/jul/26 pass: 3,970 Build 6: aarch64/2019/jul/29 pass: 3,970 Build 7: aarch64/2019/jul/31 pass: 3,970 Build 8: aarch64/2019/aug/02 pass: 3,970 Build 9: aarch64/2019/aug/05 pass: 3,970 Build 10: aarch64/2019/aug/07 pass: 3,970 Build 11: aarch64/2019/aug/12 pass: 3,970 Build 12: aarch64/2019/aug/14 pass: 3,972 Build 13: aarch64/2019/aug/16 pass: 3,972 Build 14: aarch64/2019/aug/19 pass: 3,972 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.94x Relative performance: Server critical-jOPS (nc): 10.21x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 193.36 Server 193.36 / Server 2014-04-01 (71.00): 2.72x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-07-15 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/196/results/ 2019-07-17 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/198/results/ 2019-07-20 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/200/results/ 2019-07-22 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/203/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/205/results/ 2019-07-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/207/results/ 2019-07-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/210/results/ 2019-08-01 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/212/results/ 2019-08-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/214/results/ 2019-08-06 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/217/results/ 2019-08-08 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/219/results/ 2019-08-13 pass rate: 10487/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/224/results/ 2019-08-15 pass rate: 10488/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/226/results/ 2019-08-17 pass rate: 10488/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/228/results/ 2019-08-20 pass rate: 10489/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/231/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From felix.yang at huawei.com Tue Aug 20 08:38:14 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Tue, 20 Aug 2019 08:38:14 +0000 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency Message-ID: Hi, Thanks for reviewing this. I am still waiting for maintainer approval for backporting 2, 3 and 4 to jdk11u repo. Felix > I think this is ok to push. However, I would be happier if Roland > could also check it before you do that. The patch looks reasonable to me. Roland. From adinn at redhat.com Tue Aug 20 08:58:30 2019 From: adinn at redhat.com (Andrew Dinn) Date: Tue, 20 Aug 2019 09:58:30 +0100 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency In-Reply-To: References: Message-ID: <2519ec48-03b9-ff92-646f-e6653784fe54@redhat.com> Hi Felix, [I have included jdk-updates-dev in cc] On 20/08/2019 09:38, Yangfei (Felix) wrote: > Hi, > > Thanks for reviewing this. > I am still waiting for maintainer approval for backporting 2, 3 and 4 to jdk11u repo. I think you actually meant fixes 3, 4 and 5 using the numbering in your original request. Anyway, these are the corresponding JIRAs and I can see that you have added Fix-Request comments and jdk11u-fix-request labels: 3) https://bugs.openjdk.java.net/browse/JDK-8209420 4) https://bugs.openjdk.java.net/browse/JDK-8211233 5) https://bugs.openjdk.java.net/browse/JDK-8214857 Full details of the discussion on aarch64-port-dev appear to be provided in the fix-request comments (thanks Felix for doing such a thorough job). Could one of the jdk11u maintainers please check these fix requests for approval? 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 Tue Aug 20 09:20:00 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 20 Aug 2019 10:20:00 +0100 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency In-Reply-To: <2519ec48-03b9-ff92-646f-e6653784fe54@redhat.com> References: <2519ec48-03b9-ff92-646f-e6653784fe54@redhat.com> Message-ID: On 8/20/19 9:58 AM, Andrew Dinn wrote: > 4) https://bugs.openjdk.java.net/browse/JDK-8211233 Has this backport been reviewed by Roland? It's not by any means low risk to apply a patch like this without expert review. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From adinn at redhat.com Tue Aug 20 09:27:30 2019 From: adinn at redhat.com (Andrew Dinn) Date: Tue, 20 Aug 2019 10:27:30 +0100 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency In-Reply-To: References: <2519ec48-03b9-ff92-646f-e6653784fe54@redhat.com> Message-ID: On 20/08/2019 10:20, Andrew Haley wrote: > On 8/20/19 9:58 AM, Andrew Dinn wrote: >> 4) https://bugs.openjdk.java.net/browse/JDK-8211233 > > Has this backport been reviewed by Roland? It's not by any means > low risk to apply a patch like this without expert review. The three patches in question were made to jdk12 and apply without change to jdk11u (n.b. this is the second patch of that set of three). Roland and I have both reviewed the modified version of all three patched created by Felix for jdk8u. I certainly don't see any problem with applying this unmodified patch to jdk11u. It corrects an important omission in patch 1 of 3. 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 rwestrel at redhat.com Tue Aug 20 12:47:15 2019 From: rwestrel at redhat.com (Roland Westrelin) Date: Tue, 20 Aug 2019 14:47:15 +0200 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency In-Reply-To: References: <2519ec48-03b9-ff92-646f-e6653784fe54@redhat.com> Message-ID: <87d0h0roks.fsf@redhat.com> > The three patches in question were made to jdk12 and apply without > change to jdk11u (n.b. this is the second patch of that set of three). > > Roland and I have both reviewed the modified version of all three > patched created by Felix for jdk8u. > > I certainly don't see any problem with applying this unmodified patch to > jdk11u. It corrects an important omission in patch 1 of 3. I agree with Andrew: it the patches apply cleanly I see no reason not to move forward with them. Roland. From aph at redhat.com Tue Aug 20 17:00:49 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 20 Aug 2019 18:00:49 +0100 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency In-Reply-To: <87d0h0roks.fsf@redhat.com> References: <2519ec48-03b9-ff92-646f-e6653784fe54@redhat.com> <87d0h0roks.fsf@redhat.com> Message-ID: On 8/20/19 1:47 PM, Roland Westrelin wrote: > I agree with Andrew: it the patches apply cleanly I see no reason not to > move forward with them. OK. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From gnu.andrew at redhat.com Tue Aug 20 19:31:53 2019 From: gnu.andrew at redhat.com (Andrew John Hughes) Date: Tue, 20 Aug 2019 20:31:53 +0100 Subject: [aarch64-port-dev ] [RFR] [8u] 8u232-b04 Upstream Sync Message-ID: Webrevs: https://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/ Merge changesets: http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/corba/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/jaxp/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/jaxws/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/jdk/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/hotspot/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/langtools/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/nashorn/merge.changeset http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/root/merge.changeset Changes in aarch64-shenandoah-jdk8u232-b04: - S8188868: PPC64: Support AES intrinsics on Big Endian - S8213134: AArch64: vector shift failed with MaxVectorSize=8 - S8228725: AArch64: Purge method call format support Main issues of note: 8213134 & 8228725 are already upstream, so the only merge change is 8188868. diffstat for root b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for corba b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for jaxp b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for jaxws b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for langtools b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for nashorn b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for jdk b/.hgtags | 1 + 1 file changed, 1 insertion(+) diffstat for hotspot b/.hgtags | 1 b/src/cpu/ppc/vm/assembler_ppc.hpp | 1 b/src/cpu/ppc/vm/assembler_ppc.inline.hpp | 8 b/src/cpu/ppc/vm/stubGenerator_ppc.cpp | 385 +++++++++++++++--------------- b/src/cpu/ppc/vm/stubRoutines_ppc_64.hpp | 2 b/src/cpu/ppc/vm/vm_version_ppc.cpp | 13 - 6 files changed, 209 insertions(+), 201 deletions(-) Successfully built on x86, x86_64, s390, s390x, ppc64, ppc64le & aarch64. Ok to push? -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 https://keybase.io/gnu_andrew From shade at redhat.com Tue Aug 20 19:38:25 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Tue, 20 Aug 2019 21:38:25 +0200 Subject: [aarch64-port-dev ] [RFR] [8u] 8u232-b04 Upstream Sync In-Reply-To: References: Message-ID: <61f82d98-a0a3-7a32-6b6d-894bf5ad79be@redhat.com> On 8/20/19 9:31 PM, Andrew John Hughes wrote: > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/corba/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/jaxp/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/jaxws/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/jdk/merge.changeset Looks trivially good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/hotspot/merge.changeset Looks good. > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/langtools/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/nashorn/merge.changeset > http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/root/merge.changeset Looks trivially good. Thumbs up! Good to go in. -- Thanks, -Aleksey From gnu.andrew at redhat.com Tue Aug 20 21:34:52 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 20 Aug 2019 21:34:52 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/corba: 3 new changesets Message-ID: <201908202134.x7KLYqJQ018936@aojmv0008.oracle.com> Changeset: 836e5e2e10a5 Author: andrew Date: 2019-08-15 02:50 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/836e5e2e10a5 Added tag jdk8u232-b04 for changeset 1447921be802 ! .hgtags Changeset: 2a9fceb1f550 Author: andrew Date: 2019-08-19 18:14 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/2a9fceb1f550 Merge jdk8u232-b04 ! .hgtags Changeset: 6a5cf273ef68 Author: andrew Date: 2019-08-19 18:17 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/6a5cf273ef68 Added tag aarch64-shenandoah-jdk8u232-b04 for changeset 2a9fceb1f550 ! .hgtags From gnu.andrew at redhat.com Tue Aug 20 21:34:43 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 20 Aug 2019 21:34:43 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah: 3 new changesets Message-ID: <201908202134.x7KLYhmG018788@aojmv0008.oracle.com> Changeset: cd2e5f820a0d Author: andrew Date: 2019-08-15 02:50 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/cd2e5f820a0d Added tag jdk8u232-b04 for changeset 9611ccdff5fe ! .hgtags Changeset: 4a2254b8eaa9 Author: andrew Date: 2019-08-19 18:14 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/4a2254b8eaa9 Merge jdk8u232-b04 ! .hgtags Changeset: 94c2f82b9e57 Author: andrew Date: 2019-08-19 18:17 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/94c2f82b9e57 Added tag aarch64-shenandoah-jdk8u232-b04 for changeset 4a2254b8eaa9 ! .hgtags From gnu.andrew at redhat.com Tue Aug 20 21:34:59 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 20 Aug 2019 21:34:59 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxp: 3 new changesets Message-ID: <201908202134.x7KLYxF5019043@aojmv0008.oracle.com> Changeset: 2b9fdc450085 Author: andrew Date: 2019-08-15 02:50 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/2b9fdc450085 Added tag jdk8u232-b04 for changeset cf6d61173105 ! .hgtags Changeset: 4772883fc458 Author: andrew Date: 2019-08-19 18:14 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/4772883fc458 Merge jdk8u232-b04 ! .hgtags Changeset: c93e2334d0ff Author: andrew Date: 2019-08-19 18:17 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/c93e2334d0ff Added tag aarch64-shenandoah-jdk8u232-b04 for changeset 4772883fc458 ! .hgtags From gnu.andrew at redhat.com Tue Aug 20 21:35:07 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 20 Aug 2019 21:35:07 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxws: 3 new changesets Message-ID: <201908202135.x7KLZ8Ju019161@aojmv0008.oracle.com> Changeset: 298981215ad0 Author: andrew Date: 2019-08-15 02:51 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/298981215ad0 Added tag jdk8u232-b04 for changeset d8ecedf2321b ! .hgtags Changeset: ed40fcbee5b7 Author: andrew Date: 2019-08-19 18:14 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/ed40fcbee5b7 Merge jdk8u232-b04 ! .hgtags Changeset: d6dfb7eff7d8 Author: andrew Date: 2019-08-19 18:17 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/d6dfb7eff7d8 Added tag aarch64-shenandoah-jdk8u232-b04 for changeset ed40fcbee5b7 ! .hgtags From gnu.andrew at redhat.com Tue Aug 20 21:35:16 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 20 Aug 2019 21:35:16 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/langtools: 3 new changesets Message-ID: <201908202135.x7KLZGSg019256@aojmv0008.oracle.com> Changeset: 415c49110391 Author: andrew Date: 2019-08-15 02:51 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/415c49110391 Added tag jdk8u232-b04 for changeset 3de2732a8241 ! .hgtags Changeset: 0d8f4786ce8e Author: andrew Date: 2019-08-19 18:14 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/0d8f4786ce8e Merge jdk8u232-b04 ! .hgtags Changeset: 20dbef3883c4 Author: andrew Date: 2019-08-19 18:17 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/20dbef3883c4 Added tag aarch64-shenandoah-jdk8u232-b04 for changeset 0d8f4786ce8e ! .hgtags From gnu.andrew at redhat.com Tue Aug 20 21:35:24 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 20 Aug 2019 21:35:24 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 5 new changesets Message-ID: <201908202135.x7KLZOx7019346@aojmv0008.oracle.com> Changeset: 42118db355f5 Author: mdoerr Date: 2019-08-11 19:11 -0400 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/42118db355f5 8188868: PPC64: Support AES intrinsics on Big Endian Reviewed-by: goetz ! src/cpu/ppc/vm/assembler_ppc.hpp ! src/cpu/ppc/vm/assembler_ppc.inline.hpp ! src/cpu/ppc/vm/stubGenerator_ppc.cpp ! src/cpu/ppc/vm/stubRoutines_ppc_64.hpp ! src/cpu/ppc/vm/vm_version_ppc.cpp Changeset: 921c5ee7965f Author: andrew Date: 2019-08-12 05:04 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/921c5ee7965f Merge Changeset: bfac16f18d92 Author: andrew Date: 2019-08-15 02:51 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/bfac16f18d92 Added tag jdk8u232-b04 for changeset 921c5ee7965f ! .hgtags Changeset: 68952c11a249 Author: andrew Date: 2019-08-19 18:14 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/68952c11a249 Merge jdk8u232-b04 ! .hgtags Changeset: 4ba89af8db70 Author: andrew Date: 2019-08-19 18:17 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/4ba89af8db70 Added tag aarch64-shenandoah-jdk8u232-b04 for changeset 68952c11a249 ! .hgtags From gnu.andrew at redhat.com Tue Aug 20 21:35:34 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 20 Aug 2019 21:35:34 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jdk: 3 new changesets Message-ID: <201908202135.x7KLZY3s019967@aojmv0008.oracle.com> Changeset: f6a3bd14735c Author: andrew Date: 2019-08-15 02:51 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f6a3bd14735c Added tag jdk8u232-b04 for changeset 3ef3348195ff ! .hgtags Changeset: 1a0135574f39 Author: andrew Date: 2019-08-19 18:14 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/1a0135574f39 Merge jdk8u232-b04 ! .hgtags Changeset: dac8c5261016 Author: andrew Date: 2019-08-19 18:17 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/dac8c5261016 Added tag aarch64-shenandoah-jdk8u232-b04 for changeset 1a0135574f39 ! .hgtags From gnu.andrew at redhat.com Tue Aug 20 21:35:42 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 20 Aug 2019 21:35:42 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/nashorn: 3 new changesets Message-ID: <201908202135.x7KLZg8s020158@aojmv0008.oracle.com> Changeset: 52afbdfa7852 Author: andrew Date: 2019-08-15 02:51 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/52afbdfa7852 Added tag jdk8u232-b04 for changeset 41756665474f ! .hgtags Changeset: 75a66bb0142e Author: andrew Date: 2019-08-19 18:14 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/75a66bb0142e Merge jdk8u232-b04 ! .hgtags Changeset: 2bdebdab9a24 Author: andrew Date: 2019-08-19 18:17 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/2bdebdab9a24 Added tag aarch64-shenandoah-jdk8u232-b04 for changeset 75a66bb0142e ! .hgtags From gnu.andrew at redhat.com Tue Aug 20 21:42:07 2019 From: gnu.andrew at redhat.com (Andrew John Hughes) Date: Tue, 20 Aug 2019 22:42:07 +0100 Subject: [aarch64-port-dev ] [RFR] [8u] 8u232-b04 Upstream Sync In-Reply-To: <61f82d98-a0a3-7a32-6b6d-894bf5ad79be@redhat.com> References: <61f82d98-a0a3-7a32-6b6d-894bf5ad79be@redhat.com> Message-ID: On 20/08/2019 20:38, Aleksey Shipilev wrote: > On 8/20/19 9:31 PM, Andrew John Hughes wrote: >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/corba/merge.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/jaxp/merge.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/jaxws/merge.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/jdk/merge.changeset > > Looks trivially good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/hotspot/merge.changeset > > Looks good. > >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/langtools/merge.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/nashorn/merge.changeset >> http://cr.openjdk.java.net/~andrew/shenandoah-8/u232-b04/root/merge.changeset > Looks trivially good. > > Thumbs up! Good to go in. > Thanks. Pushed. -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 https://keybase.io/gnu_andrew From felix.yang at huawei.com Wed Aug 21 02:56:15 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Wed, 21 Aug 2019 02:56:15 +0000 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency Message-ID: Hi, Thanks for the help. Now for the three patches: 3) https://bugs.openjdk.java.net/browse/JDK-8209420 4) https://bugs.openjdk.java.net/browse/JDK-8211233 5) https://bugs.openjdk.java.net/browse/JDK-8214857 I can see that 3) and 5) are approved for 11u backport (labeled with 'jdk11u-fix-yes'). As a follow-up fix for 3), 4) is still pending there (labeled with both `jdk11u-critical-request` and `jdk11u-fix-request`). Is it OK now to add a 'jdk11u-fix-yes' label for 4) so that the three patches can be merged to jdk11u-dev repo? Felix On 8/20/19 1:47 PM, Roland Westrelin wrote: > I agree with Andrew: it the patches apply cleanly I see no reason not > to move forward with them. OK. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From shade at redhat.com Wed Aug 21 08:17:23 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Wed, 21 Aug 2019 10:17:23 +0200 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency In-Reply-To: References: Message-ID: <04d6fe76-0bb9-d5c2-f044-1827aa081a2d@redhat.com> On 8/21/19 4:56 AM, Yangfei (Felix) wrote: > Thanks for the help. Now for the three patches: > > 3) https://bugs.openjdk.java.net/browse/JDK-8209420 > 4) https://bugs.openjdk.java.net/browse/JDK-8211233 > 5) https://bugs.openjdk.java.net/browse/JDK-8214857 > > I can see that 3) and 5) are approved for 11u backport (labeled with 'jdk11u-fix-yes'). > As a follow-up fix for 3), 4) is still pending there (labeled with both `jdk11u-critical-request` and `jdk11u-fix-request`). > Is it OK now to add a 'jdk11u-fix-yes' label for 4) so that the three patches can be merged to jdk11u-dev repo? Yeah, Andrew needs to do that: add jdk11u-fix-yes to https://bugs.openjdk.java.net/browse/JDK-8211233. Felix, do you have anyone on the hook for actually pushing these to jdk11u-dev? If not, I can push. -- Thanks, -Aleksey From felix.yang at huawei.com Wed Aug 21 08:36:27 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Wed, 21 Aug 2019 08:36:27 +0000 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency Message-ID: Comments inlined: On 8/21/19 4:56 AM, Yangfei (Felix) wrote: > Thanks for the help. Now for the three patches: > > 3) https://bugs.openjdk.java.net/browse/JDK-8209420 > 4) https://bugs.openjdk.java.net/browse/JDK-8211233 > 5) https://bugs.openjdk.java.net/browse/JDK-8214857 > > I can see that 3) and 5) are approved for 11u backport (labeled with 'jdk11u-fix-yes'). > As a follow-up fix for 3), 4) is still pending there (labeled with both `jdk11u-critical-request` and `jdk11u-fix-request`). > Is it OK now to add a 'jdk11u-fix-yes' label for 4) so that the three patches can be merged to jdk11u-dev repo? Yeah, Andrew needs to do that: add jdk11u-fix-yes to https://bugs.openjdk.java.net/browse/JDK-8211233. fyang: I can see the jdk11u-fix-yes label now for JDK-8211233. Felix, do you have anyone on the hook for actually pushing these to jdk11u-dev? If not, I can push. fyang: I cannot access my laptop for now. Please help do the push. Thanks, Felix From shade at redhat.com Wed Aug 21 12:18:28 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Wed, 21 Aug 2019 14:18:28 +0200 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency In-Reply-To: References: Message-ID: On 8/21/19 10:36 AM, Yangfei (Felix) wrote: > On 8/21/19 4:56 AM, Yangfei (Felix) wrote: >> 3) https://bugs.openjdk.java.net/browse/JDK-8209420 >> 4) https://bugs.openjdk.java.net/browse/JDK-8211233 >> 5) https://bugs.openjdk.java.net/browse/JDK-8214857 >> > Felix, do you have anyone on the hook for actually pushing these to jdk11u-dev? If not, I can push. > > fyang: I cannot access my laptop for now. Please help do the push. Passed tier1 on aarch64 and x86_64. Pushed all three to jdk11u-dev: https://hg.openjdk.java.net/jdk-updates/jdk11u-dev/rev/4f787d0086fc https://hg.openjdk.java.net/jdk-updates/jdk11u-dev/rev/4cf59897e14f https://hg.openjdk.java.net/jdk-updates/jdk11u-dev/rev/04dd2501a9df -- Thanks, -Aleksey From felix.yang at huawei.com Wed Aug 21 13:49:18 2019 From: felix.yang at huawei.com (felix.yang at huawei.com) Date: Wed, 21 Aug 2019 13:49:18 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 5 new changesets Message-ID: <201908211349.x7LDnIIA023641@aojmv0008.oracle.com> Changeset: b9380e010fdc Author: aph Date: 2017-05-11 13:11 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/b9380e010fdc 8179954: AArch64: C1 and C2 volatile accesses are not sequentially consistent Reviewed-by: roland ! src/cpu/aarch64/vm/c1_LIRGenerator_aarch64.cpp ! src/cpu/aarch64/vm/templateTable_aarch64.cpp Changeset: 6ff3bed6d8fa Author: adinn Date: 2018-07-09 09:38 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/6ff3bed6d8fa 8206163: AArch64: incorrect code generation for StoreCM Summary: StoreCM may require planting a StoreStore barrier Reviewed-by: aph, zyao, roland ! src/cpu/aarch64/vm/aarch64.ad Changeset: f498b25d9c30 Author: roland Date: 2018-08-14 16:54 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/f498b25d9c30 8209420: Track membars for volatile accesses so they can be properly optimized Reviewed-by: adinn, aph, thartmann ! src/cpu/aarch64/vm/aarch64.ad ! src/share/vm/opto/compile.cpp ! src/share/vm/opto/library_call.cpp ! src/share/vm/opto/memnode.cpp ! src/share/vm/opto/memnode.hpp ! src/share/vm/opto/parse3.cpp Changeset: ffa9ff5b9217 Author: roland Date: 2018-09-27 17:46 +0200 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/ffa9ff5b9217 8211233: MemBarNode::trailing_membar() and MemBarNode::leading_membar() need to handle dying subgraphs better Reviewed-by: kvn, thartmann ! src/share/vm/opto/memnode.cpp Changeset: 7e641cd3d5b4 Author: roland Date: 2018-12-03 10:51 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/7e641cd3d5b4 8214857: "bad trailing membar" assert failure at memnode.cpp:3220 Reviewed-by: adinn, thartmann ! src/share/vm/opto/memnode.cpp From ci_notify at linaro.org Thu Aug 22 01:45:06 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Thu, 22 Aug 2019 01:45:06 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <802972926.2138.1566438307827.JavaMail.javamailuser@localhost> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2019/233/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/17 pass: 5,700; fail: 1; error: 1 Build 1: aarch64/2019/jul/19 pass: 5,699; fail: 3; error: 1 Build 2: aarch64/2019/jul/22 pass: 5,705; fail: 2 Build 3: aarch64/2019/jul/24 pass: 5,706; fail: 1 Build 4: aarch64/2019/jul/26 pass: 5,707; fail: 2 Build 5: aarch64/2019/jul/29 pass: 5,705; fail: 4 Build 6: aarch64/2019/jul/31 pass: 5,711; fail: 1 Build 7: aarch64/2019/aug/02 pass: 5,711; fail: 2 Build 8: aarch64/2019/aug/05 pass: 5,712; fail: 1 Build 9: aarch64/2019/aug/07 pass: 5,711; fail: 1 Build 10: aarch64/2019/aug/12 pass: 5,713; fail: 2 Build 11: aarch64/2019/aug/14 pass: 5,717; fail: 1 Build 12: aarch64/2019/aug/16 pass: 5,718 Build 13: aarch64/2019/aug/19 pass: 5,718 Build 14: aarch64/2019/aug/21 pass: 5,718; fail: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/17 pass: 8,614; fail: 522; error: 24 Build 1: aarch64/2019/jul/19 pass: 8,611; fail: 526; error: 26 Build 2: aarch64/2019/jul/22 pass: 8,628; fail: 511; error: 24 Build 3: aarch64/2019/jul/24 pass: 8,617; fail: 538; error: 26 Build 4: aarch64/2019/jul/26 pass: 8,649; fail: 518; error: 17 Build 5: aarch64/2019/jul/29 pass: 8,640; fail: 520; error: 26 Build 6: aarch64/2019/jul/31 pass: 8,640; fail: 526; error: 24 Build 7: aarch64/2019/aug/02 pass: 8,637; fail: 524; error: 29 Build 8: aarch64/2019/aug/05 pass: 8,642; fail: 519; error: 29 Build 9: aarch64/2019/aug/07 pass: 8,638; fail: 529; error: 23 Build 10: aarch64/2019/aug/12 pass: 8,659; fail: 515; error: 19 Build 11: aarch64/2019/aug/14 pass: 8,674; fail: 505; error: 19 Build 12: aarch64/2019/aug/16 pass: 8,673; fail: 506; error: 21 Build 13: aarch64/2019/aug/19 pass: 8,676; fail: 503; error: 22 Build 14: aarch64/2019/aug/21 pass: 8,676; fail: 506; error: 20 3 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/17 pass: 3,968 Build 1: aarch64/2019/jul/19 pass: 3,969 Build 2: aarch64/2019/jul/22 pass: 3,969 Build 3: aarch64/2019/jul/24 pass: 3,970 Build 4: aarch64/2019/jul/26 pass: 3,970 Build 5: aarch64/2019/jul/29 pass: 3,970 Build 6: aarch64/2019/jul/31 pass: 3,970 Build 7: aarch64/2019/aug/02 pass: 3,970 Build 8: aarch64/2019/aug/05 pass: 3,970 Build 9: aarch64/2019/aug/07 pass: 3,970 Build 10: aarch64/2019/aug/12 pass: 3,970 Build 11: aarch64/2019/aug/14 pass: 3,972 Build 12: aarch64/2019/aug/16 pass: 3,972 Build 13: aarch64/2019/aug/19 pass: 3,972 Build 14: aarch64/2019/aug/21 pass: 3,972 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.75x Relative performance: Server critical-jOPS (nc): 9.68x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 196.04 Server 196.04 / Server 2014-04-01 (71.00): 2.76x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-07-17 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/198/results/ 2019-07-20 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/200/results/ 2019-07-22 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/203/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/205/results/ 2019-07-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/207/results/ 2019-07-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/210/results/ 2019-08-01 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/212/results/ 2019-08-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/214/results/ 2019-08-06 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/217/results/ 2019-08-08 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/219/results/ 2019-08-13 pass rate: 10487/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/224/results/ 2019-08-15 pass rate: 10488/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/226/results/ 2019-08-17 pass rate: 10488/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/228/results/ 2019-08-20 pass rate: 10489/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/231/results/ 2019-08-22 pass rate: 10489/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/233/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From felix.yang at huawei.com Thu Aug 22 05:53:50 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Thu, 22 Aug 2019 05:53:50 +0000 Subject: [aarch64-port-dev ] Request for Approval: Backport patches to fix volatile access inconsistency Message-ID: > Felix, do you have anyone on the hook for actually pushing these to jdk11u-dev? If not, I can push. > > fyang: I cannot access my laptop for now. Please help do the push. Passed tier1 on aarch64 and x86_64. Pushed all three to jdk11u-dev: https://hg.openjdk.java.net/jdk-updates/jdk11u-dev/rev/4f787d0086fc https://hg.openjdk.java.net/jdk-updates/jdk11u-dev/rev/4cf59897e14f https://hg.openjdk.java.net/jdk-updates/jdk11u-dev/rev/04dd2501a9df Thanks for the help. Patches for 8u aarch64 repo also pushed: https://mail.openjdk.java.net/pipermail/aarch64-port-dev/2019-August/007938.html Felix From patrick at os.amperecomputing.com Thu Aug 22 11:20:00 2019 From: patrick at os.amperecomputing.com (Patrick Zhang OS) Date: Thu, 22 Aug 2019 11:20:00 +0000 Subject: [aarch64-port-dev ] [14] RFR(S): 8225670: compiler/types/correctness/* tests fail with "assert(recv == __null || recv->is_klass()) failed: wrong type" In-Reply-To: <47a506e5-f5c6-40ce-4c89-2a06853eff71@oracle.com> References: <678f82db-e5b9-c5ad-9f6c-439b4c7cecd7@oracle.com> <5b38061a-2069-8772-2f42-86fa1749ef15@oracle.com> <47a506e5-f5c6-40ce-4c89-2a06853eff71@oracle.com> Message-ID: Hi Christian, My test system shows this fix probably introduced a significant performance loss with a couple of apps/benchmarks on both aarch64 (Ampere eMAG) and x86 systems, I filed this ticket to track it. https://bugs.openjdk.java.net/browse/JDK-8230036 Regards Patrick -----Original Message----- From: hotspot-compiler-dev On Behalf Of Christian Hagedorn Sent: Friday, August 9, 2019 7:56 PM To: Erik ?sterlund ; hotspot-compiler-dev at openjdk.java.net; Tobias Hartmann Subject: Re: [14] RFR(S): 8225670: compiler/types/correctness/* tests fail with "assert(recv == __null || recv->is_klass()) failed: wrong type" Hi Erik, hi Tobias Thank you for your reviews! On 09.08.19 11:21, Erik ?sterlund wrote: > Hi Christian, > > Looks good - well spotted. > > To answer your question - yes the GC (ZGC in particular, and probably > soon Shenandoah when they hook in to the concurrent class unloading > framework) cleans the extra data section of MDOs concurrently, under > the extra data lock. > > However, they clear whole rows from the extra data section, under the > extra data lock of the MDOs; they never write that the Klass is NULL. > So I believe this bug only relates to the use of the WhiteBox API. That was my guess, too. Thanks for clearing that up and answering the question. > The row clearing of concurrent GCs synchronizes with a metadata > preparation phase for unpacking MDOs to ciMDOs. The preparation phase > will in a fixed-point iteration try to create ci handles for all > encountered metadata under the extradata lock. Every time it > encounters an uncached metadata instance, it has to release the lock > due to ranking issues, and may also run into safepoints then. Such > situations are detected, triggering a restart of the fixed-pont iteration. > > Once the fixed-point iteration has finished, we know that we under the > lock walked all metadata in the extra data section without ever > releasing the lock, have ci handles keeping all metadata alive, and > can't have gotten any safepoints due to being in VM state. After that, > the rows are copied and translated, and now we are guaranteed that the > translation will always already have the ci handles cached. Thanks for the detailed explanation! > There is some random original copy of the raw MDO extra data that is > performed before preparing the metadata. I don't think it is really > used or needed. Might be interesting to remove in a future RFE. It > gets overwritten by the subsequent row-by-row processing after > metadata preparation. I created a new RFE [1] and referenced this conversation. Best regards, Christian [1] https://bugs.openjdk.java.net/browse/JDK-8229353 From tobias.hartmann at oracle.com Thu Aug 22 11:39:49 2019 From: tobias.hartmann at oracle.com (Tobias Hartmann) Date: Thu, 22 Aug 2019 13:39:49 +0200 Subject: [aarch64-port-dev ] [14] RFR(S): 8225670: compiler/types/correctness/* tests fail with "assert(recv == __null || recv->is_klass()) failed: wrong type" In-Reply-To: References: <678f82db-e5b9-c5ad-9f6c-439b4c7cecd7@oracle.com> <5b38061a-2069-8772-2f42-86fa1749ef15@oracle.com> <47a506e5-f5c6-40ce-4c89-2a06853eff71@oracle.com> Message-ID: <8b9cc13d-8969-603d-cadf-c698d07a14fe@oracle.com> Hi Patrick, thanks, we've already noticed that regression and backed the fix out: https://bugs.openjdk.java.net/browse/JDK-8230020 Best regards, Tobias On 22.08.19 13:20, Patrick Zhang OS wrote: > Hi Christian, > > My test system shows this fix probably introduced a significant performance loss with a couple of apps/benchmarks on both aarch64 (Ampere eMAG) and x86 systems, I filed this ticket to track it. https://bugs.openjdk.java.net/browse/JDK-8230036 > > Regards > Patrick > > -----Original Message----- > From: hotspot-compiler-dev On Behalf Of Christian Hagedorn > Sent: Friday, August 9, 2019 7:56 PM > To: Erik ?sterlund ; hotspot-compiler-dev at openjdk.java.net; Tobias Hartmann > Subject: Re: [14] RFR(S): 8225670: compiler/types/correctness/* tests fail with "assert(recv == __null || recv->is_klass()) failed: wrong type" > > Hi Erik, hi Tobias > > Thank you for your reviews! > > On 09.08.19 11:21, Erik ?sterlund wrote: >> Hi Christian, >> >> Looks good - well spotted. >> >> To answer your question - yes the GC (ZGC in particular, and probably >> soon Shenandoah when they hook in to the concurrent class unloading >> framework) cleans the extra data section of MDOs concurrently, under >> the extra data lock. >> >> However, they clear whole rows from the extra data section, under the >> extra data lock of the MDOs; they never write that the Klass is NULL. >> So I believe this bug only relates to the use of the WhiteBox API. > > That was my guess, too. Thanks for clearing that up and answering the question. > >> The row clearing of concurrent GCs synchronizes with a metadata >> preparation phase for unpacking MDOs to ciMDOs. The preparation phase >> will in a fixed-point iteration try to create ci handles for all >> encountered metadata under the extradata lock. Every time it >> encounters an uncached metadata instance, it has to release the lock >> due to ranking issues, and may also run into safepoints then. Such >> situations are detected, triggering a restart of the fixed-pont iteration. >> >> Once the fixed-point iteration has finished, we know that we under the >> lock walked all metadata in the extra data section without ever >> releasing the lock, have ci handles keeping all metadata alive, and >> can't have gotten any safepoints due to being in VM state. After that, >> the rows are copied and translated, and now we are guaranteed that the >> translation will always already have the ci handles cached. > > Thanks for the detailed explanation! > >> There is some random original copy of the raw MDO extra data that is >> performed before preparing the metadata. I don't think it is really >> used or needed. Might be interesting to remove in a future RFE. It >> gets overwritten by the subsequent row-by-row processing after >> metadata preparation. > > I created a new RFE [1] and referenced this conversation. > > Best regards, > Christian > > > [1] https://bugs.openjdk.java.net/browse/JDK-8229353 > From ci_notify at linaro.org Fri Aug 23 09:46:03 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 23 Aug 2019 09:46:03 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 11u on AArch64 Message-ID: <983903822.2225.1566553564183.JavaMail.javamailuser@localhost> 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/jdk11u/openjdk-jtreg-nightly-tests/summary/2019/234/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/19 pass: 5,721; fail: 9; not run: 11,618 Build 1: aarch64/2019/mar/28 pass: 5,722; fail: 8; not run: 11,618 Build 2: aarch64/2019/apr/02 pass: 5,723; fail: 8; not run: 11,618 Build 3: aarch64/2019/apr/04 pass: 5,722; fail: 9; not run: 11,618 Build 4: aarch64/2019/apr/18 pass: 5,723; fail: 8; not run: 11,618 Build 5: aarch64/2019/may/16 pass: 5,734; fail: 5; not run: 11,623 Build 6: aarch64/2019/may/25 pass: 5,735; fail: 5; not run: 11,623 Build 7: aarch64/2019/jun/05 pass: 5,737; fail: 5; not run: 11,623 Build 8: aarch64/2019/jun/15 pass: 5,737; fail: 5; not run: 11,623 Build 9: aarch64/2019/jun/27 pass: 5,737; fail: 5 Build 10: aarch64/2019/jul/02 pass: 5,737; fail: 5 Build 11: aarch64/2019/aug/03 pass: 5,746; fail: 4 Build 12: aarch64/2019/aug/10 pass: 5,747; fail: 4 Build 13: aarch64/2019/aug/15 pass: 5,753; fail: 4 Build 14: aarch64/2019/aug/22 pass: 5,755; fail: 4 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/19 pass: 8,365; fail: 527; error: 24 Build 1: aarch64/2019/mar/28 pass: 8,374; fail: 521; error: 21 Build 2: aarch64/2019/apr/02 pass: 8,354; fail: 536; error: 26 Build 3: aarch64/2019/apr/04 pass: 8,382; fail: 510; error: 24 Build 4: aarch64/2019/apr/18 pass: 8,398; fail: 501; error: 19 Build 5: aarch64/2019/may/16 pass: 8,397; fail: 514; error: 22 Build 6: aarch64/2019/may/25 pass: 8,403; fail: 511; error: 21 Build 7: aarch64/2019/jun/05 pass: 8,427; fail: 489; error: 19 Build 8: aarch64/2019/jun/15 pass: 8,409; fail: 506; error: 20 Build 9: aarch64/2019/jun/27 pass: 8,401; fail: 512; error: 22 Build 10: aarch64/2019/jul/02 pass: 8,407; fail: 498; error: 31 Build 11: aarch64/2019/aug/03 pass: 8,429; fail: 509; error: 18 Build 12: aarch64/2019/aug/10 pass: 8,450; fail: 485; error: 16 Build 13: aarch64/2019/aug/15 pass: 8,443; fail: 496; error: 13 Build 14: aarch64/2019/aug/22 pass: 8,446; fail: 494; error: 15 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/mar/19 pass: 3,904 Build 1: aarch64/2019/mar/28 pass: 3,904 Build 2: aarch64/2019/apr/02 pass: 3,904 Build 3: aarch64/2019/apr/04 pass: 3,904 Build 4: aarch64/2019/apr/18 pass: 3,904 Build 5: aarch64/2019/may/16 pass: 3,908 Build 6: aarch64/2019/may/25 pass: 3,908 Build 7: aarch64/2019/jun/05 pass: 3,908 Build 8: aarch64/2019/jun/15 pass: 3,908 Build 9: aarch64/2019/jun/27 pass: 3,908 Build 10: aarch64/2019/jul/02 pass: 3,908 Build 11: aarch64/2019/aug/03 pass: 3,908 Build 12: aarch64/2019/aug/10 pass: 3,909 Build 13: aarch64/2019/aug/15 pass: 3,909 Build 14: aarch64/2019/aug/22 pass: 3,909 Previous results can be found here: http://openjdk.linaro.org/jdk11u/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.84x Relative performance: Server critical-jOPS (nc): 8.35x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk11u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 207.57 Server 207.57 / Server 2014-04-01 (71.00): 2.92x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk11u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-03-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/078/results/ 2019-03-29 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/087/results/ 2019-04-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/092/results/ 2019-04-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/094/results/ 2019-04-19 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/108/results/ 2019-05-17 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/136/results/ 2019-05-26 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/145/results/ 2019-06-05 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/156/results/ 2019-06-16 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/166/results/ 2019-06-28 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/178/results/ 2019-07-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/183/results/ 2019-08-04 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/215/results/ 2019-08-11 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/222/results/ 2019-08-16 pass rate: 10489/10489, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/227/results/ 2019-08-23 pass rate: 10489/10489, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/234/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/ From ci_notify at linaro.org Fri Aug 23 09:50:26 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 23 Aug 2019 09:50:26 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <148458854.2227.1566553827134.JavaMail.javamailuser@localhost> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/summary/2019/234/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/15 pass: 815; fail: 22; error: 1 Build 1: aarch64/2019/jun/20 pass: 820; fail: 16; error: 2 Build 2: aarch64/2019/jun/29 pass: 807; fail: 25; error: 6 Build 3: aarch64/2019/jul/19 pass: 814; fail: 20; error: 4 Build 4: aarch64/2019/jul/25 pass: 802; fail: 25; error: 11 Build 5: aarch64/2019/jul/30 pass: 787; fail: 40; error: 11 Build 6: aarch64/2019/aug/01 pass: 800; fail: 26; error: 12 Build 7: aarch64/2019/aug/04 pass: 808; fail: 30; error: 2 Build 8: aarch64/2019/aug/06 pass: 799; fail: 29; error: 12 Build 9: aarch64/2019/aug/08 pass: 830; fail: 9; error: 1 Build 10: aarch64/2019/aug/11 pass: 825; fail: 14; error: 1 Build 11: aarch64/2019/aug/13 pass: 830; fail: 9; error: 1 Build 12: aarch64/2019/aug/15 pass: 837; fail: 9; error: 1 Build 13: aarch64/2019/aug/17 pass: 837; fail: 9; error: 1 Build 14: aarch64/2019/aug/22 pass: 837; fail: 9; error: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/15 pass: 5,827; fail: 242; error: 22 Build 1: aarch64/2019/jun/20 pass: 5,821; fail: 244; error: 26 Build 2: aarch64/2019/jun/29 pass: 5,799; fail: 265; error: 27 Build 3: aarch64/2019/jul/19 pass: 5,940; fail: 278; error: 22 Build 4: aarch64/2019/jul/25 pass: 5,938; fail: 276; error: 26 Build 5: aarch64/2019/jul/30 pass: 5,942; fail: 273; error: 25 Build 6: aarch64/2019/aug/01 pass: 5,945; fail: 271; error: 24 Build 7: aarch64/2019/aug/04 pass: 5,949; fail: 270; error: 24 Build 8: aarch64/2019/aug/06 pass: 5,945; fail: 275; error: 23 Build 9: aarch64/2019/aug/08 pass: 5,953; fail: 267; error: 23 Build 10: aarch64/2019/aug/11 pass: 5,947; fail: 272; error: 25 Build 11: aarch64/2019/aug/13 pass: 5,962; fail: 258; error: 24 Build 12: aarch64/2019/aug/15 pass: 5,955; fail: 266; error: 23 Build 13: aarch64/2019/aug/17 pass: 5,951; fail: 269; error: 24 Build 14: aarch64/2019/aug/22 pass: 5,945; fail: 279; error: 20 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jun/15 pass: 3,116; fail: 2 Build 1: aarch64/2019/jun/20 pass: 3,116; fail: 2 Build 2: aarch64/2019/jun/29 pass: 3,116; fail: 2 Build 3: aarch64/2019/jul/19 pass: 3,116; fail: 2 Build 4: aarch64/2019/jul/25 pass: 3,116; fail: 2 Build 5: aarch64/2019/jul/30 pass: 3,116; fail: 2 Build 6: aarch64/2019/aug/01 pass: 3,116; fail: 2 Build 7: aarch64/2019/aug/04 pass: 3,116; fail: 2 Build 8: aarch64/2019/aug/06 pass: 3,116; fail: 2 Build 9: aarch64/2019/aug/08 pass: 3,116; fail: 2 Build 10: aarch64/2019/aug/11 pass: 3,116; fail: 2 Build 11: aarch64/2019/aug/13 pass: 3,116; fail: 2 Build 12: aarch64/2019/aug/15 pass: 3,116; fail: 2 Build 13: aarch64/2019/aug/17 pass: 3,116; fail: 2 Build 14: aarch64/2019/aug/22 pass: 3,116; fail: 2 Previous results can be found here: http://openjdk.linaro.org/jdk8u/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 7.05x Relative performance: Server critical-jOPS (nc): 8.47x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 172.13 Server 172.13 / Server 2014-04-01 (71.00): 2.42x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-06-16 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/166/results/ 2019-06-21 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/171/results/ 2019-06-30 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/180/results/ 2019-07-20 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/200/results/ 2019-07-26 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/206/results/ 2019-07-31 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/211/results/ 2019-08-02 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/213/results/ 2019-08-05 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/216/results/ 2019-08-07 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/218/results/ 2019-08-09 pass rate: 8229/8229, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/220/results/ 2019-08-12 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/223/results/ 2019-08-13 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/225/results/ 2019-08-16 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/227/results/ 2019-08-17 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/229/results/ 2019-08-23 pass rate: 8230/8230, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/234/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From ci_notify at linaro.org Sat Aug 24 05:48:49 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sat, 24 Aug 2019 05:48:49 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <208804325.2301.1566625730717.JavaMail.javamailuser@localhost> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2019/235/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/19 pass: 5,699; fail: 3; error: 1 Build 1: aarch64/2019/jul/22 pass: 5,705; fail: 2 Build 2: aarch64/2019/jul/24 pass: 5,706; fail: 1 Build 3: aarch64/2019/jul/26 pass: 5,707; fail: 2 Build 4: aarch64/2019/jul/29 pass: 5,705; fail: 4 Build 5: aarch64/2019/jul/31 pass: 5,711; fail: 1 Build 6: aarch64/2019/aug/02 pass: 5,711; fail: 2 Build 7: aarch64/2019/aug/05 pass: 5,712; fail: 1 Build 8: aarch64/2019/aug/07 pass: 5,711; fail: 1 Build 9: aarch64/2019/aug/12 pass: 5,713; fail: 2 Build 10: aarch64/2019/aug/14 pass: 5,717; fail: 1 Build 11: aarch64/2019/aug/16 pass: 5,718 Build 12: aarch64/2019/aug/19 pass: 5,718 Build 13: aarch64/2019/aug/21 pass: 5,718; fail: 1 Build 14: aarch64/2019/aug/23 pass: 5,716; fail: 2 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/19 pass: 8,611; fail: 526; error: 26 Build 1: aarch64/2019/jul/22 pass: 8,628; fail: 511; error: 24 Build 2: aarch64/2019/jul/24 pass: 8,617; fail: 538; error: 26 Build 3: aarch64/2019/jul/26 pass: 8,649; fail: 518; error: 17 Build 4: aarch64/2019/jul/29 pass: 8,640; fail: 520; error: 26 Build 5: aarch64/2019/jul/31 pass: 8,640; fail: 526; error: 24 Build 6: aarch64/2019/aug/02 pass: 8,637; fail: 524; error: 29 Build 7: aarch64/2019/aug/05 pass: 8,642; fail: 519; error: 29 Build 8: aarch64/2019/aug/07 pass: 8,638; fail: 529; error: 23 Build 9: aarch64/2019/aug/12 pass: 8,659; fail: 515; error: 19 Build 10: aarch64/2019/aug/14 pass: 8,674; fail: 505; error: 19 Build 11: aarch64/2019/aug/16 pass: 8,673; fail: 506; error: 21 Build 12: aarch64/2019/aug/19 pass: 8,676; fail: 503; error: 22 Build 13: aarch64/2019/aug/21 pass: 8,676; fail: 506; error: 20 Build 14: aarch64/2019/aug/23 pass: 8,685; fail: 506; error: 22 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/19 pass: 3,969 Build 1: aarch64/2019/jul/22 pass: 3,969 Build 2: aarch64/2019/jul/24 pass: 3,970 Build 3: aarch64/2019/jul/26 pass: 3,970 Build 4: aarch64/2019/jul/29 pass: 3,970 Build 5: aarch64/2019/jul/31 pass: 3,970 Build 6: aarch64/2019/aug/02 pass: 3,970 Build 7: aarch64/2019/aug/05 pass: 3,970 Build 8: aarch64/2019/aug/07 pass: 3,970 Build 9: aarch64/2019/aug/12 pass: 3,970 Build 10: aarch64/2019/aug/14 pass: 3,972 Build 11: aarch64/2019/aug/16 pass: 3,972 Build 12: aarch64/2019/aug/19 pass: 3,972 Build 13: aarch64/2019/aug/21 pass: 3,972 Build 14: aarch64/2019/aug/23 pass: 3,972 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 8.14x Relative performance: Server critical-jOPS (nc): 9.17x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 207.57 Server 207.57 / Server 2014-04-01 (71.00): 2.92x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-07-20 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/200/results/ 2019-07-22 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/203/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/205/results/ 2019-07-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/207/results/ 2019-07-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/210/results/ 2019-08-01 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/212/results/ 2019-08-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/214/results/ 2019-08-06 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/217/results/ 2019-08-08 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/219/results/ 2019-08-13 pass rate: 10487/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/224/results/ 2019-08-15 pass rate: 10488/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/226/results/ 2019-08-17 pass rate: 10488/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/228/results/ 2019-08-20 pass rate: 10489/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/231/results/ 2019-08-22 pass rate: 10489/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/233/results/ 2019-08-24 pass rate: 10489/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/235/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From ci_notify at linaro.org Tue Aug 27 02:36:09 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Tue, 27 Aug 2019 02:36:09 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <344343962.2703.1566873369901.JavaMail.javamailuser@localhost> This is a summary of the JTREG test results =========================================== The build and test results are cycled every 15 days. For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/summary/2019/238/summary.html ------------------------------------------------------------------------------- client-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,780; fail: 19; not run: 90 ------------------------------------------------------------------------------- client-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,495; fail: 670; error: 23 ------------------------------------------------------------------------------- client-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/22 pass: 5,705; fail: 2 Build 1: aarch64/2019/jul/24 pass: 5,706; fail: 1 Build 2: aarch64/2019/jul/26 pass: 5,707; fail: 2 Build 3: aarch64/2019/jul/29 pass: 5,705; fail: 4 Build 4: aarch64/2019/jul/31 pass: 5,711; fail: 1 Build 5: aarch64/2019/aug/02 pass: 5,711; fail: 2 Build 6: aarch64/2019/aug/05 pass: 5,712; fail: 1 Build 7: aarch64/2019/aug/07 pass: 5,711; fail: 1 Build 8: aarch64/2019/aug/12 pass: 5,713; fail: 2 Build 9: aarch64/2019/aug/14 pass: 5,717; fail: 1 Build 10: aarch64/2019/aug/16 pass: 5,718 Build 11: aarch64/2019/aug/19 pass: 5,718 Build 12: aarch64/2019/aug/21 pass: 5,718; fail: 1 Build 13: aarch64/2019/aug/23 pass: 5,716; fail: 2 Build 14: aarch64/2019/aug/26 pass: 5,718; error: 1 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/22 pass: 8,628; fail: 511; error: 24 Build 1: aarch64/2019/jul/24 pass: 8,617; fail: 538; error: 26 Build 2: aarch64/2019/jul/26 pass: 8,649; fail: 518; error: 17 Build 3: aarch64/2019/jul/29 pass: 8,640; fail: 520; error: 26 Build 4: aarch64/2019/jul/31 pass: 8,640; fail: 526; error: 24 Build 5: aarch64/2019/aug/02 pass: 8,637; fail: 524; error: 29 Build 6: aarch64/2019/aug/05 pass: 8,642; fail: 519; error: 29 Build 7: aarch64/2019/aug/07 pass: 8,638; fail: 529; error: 23 Build 8: aarch64/2019/aug/12 pass: 8,659; fail: 515; error: 19 Build 9: aarch64/2019/aug/14 pass: 8,674; fail: 505; error: 19 Build 10: aarch64/2019/aug/16 pass: 8,673; fail: 506; error: 21 Build 11: aarch64/2019/aug/19 pass: 8,676; fail: 503; error: 22 Build 12: aarch64/2019/aug/21 pass: 8,676; fail: 506; error: 20 Build 13: aarch64/2019/aug/23 pass: 8,685; fail: 506; error: 22 Build 14: aarch64/2019/aug/26 pass: 8,683; fail: 509; error: 21 4 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jul/22 pass: 3,969 Build 1: aarch64/2019/jul/24 pass: 3,970 Build 2: aarch64/2019/jul/26 pass: 3,970 Build 3: aarch64/2019/jul/29 pass: 3,970 Build 4: aarch64/2019/jul/31 pass: 3,970 Build 5: aarch64/2019/aug/02 pass: 3,970 Build 6: aarch64/2019/aug/05 pass: 3,970 Build 7: aarch64/2019/aug/07 pass: 3,970 Build 8: aarch64/2019/aug/12 pass: 3,970 Build 9: aarch64/2019/aug/14 pass: 3,972 Build 10: aarch64/2019/aug/16 pass: 3,972 Build 11: aarch64/2019/aug/19 pass: 3,972 Build 12: aarch64/2019/aug/21 pass: 3,972 Build 13: aarch64/2019/aug/23 pass: 3,972 Build 14: aarch64/2019/aug/26 pass: 3,972 ------------------------------------------------------------------------------- server-release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 5,787; fail: 18; not run: 90 ------------------------------------------------------------------------------- server-release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 8,476; fail: 686; error: 27 ------------------------------------------------------------------------------- server-release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/oct/15 pass: 3,970; fail: 5 Previous results can be found here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/index.html SPECjbb2015 composite regression test completed =============================================== This test measures the relative performance of the server compiler running the SPECjbb2015 composite tests and compares the performance against the baseline performance of the server compiler taken on 2016-11-21. In accordance with [1], the SPECjbb2015 tests are run on a system which is not production ready and does not meet all the requirements for publishing compliant results. The numbers below shall be treated as non-compliant (nc) and are for experimental purposes only. Relative performance: Server max-jOPS (nc): 8.04x Relative performance: Server critical-jOPS (nc): 9.28x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 207.57 Server 207.57 / Server 2014-04-01 (71.00): 2.92x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdkX/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-07-22 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/203/results/ 2019-07-24 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/205/results/ 2019-07-26 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/207/results/ 2019-07-30 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/210/results/ 2019-08-01 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/212/results/ 2019-08-03 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/214/results/ 2019-08-06 pass rate: 10487/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/217/results/ 2019-08-08 pass rate: 10488/10488, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/219/results/ 2019-08-13 pass rate: 10487/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/224/results/ 2019-08-15 pass rate: 10488/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/226/results/ 2019-08-17 pass rate: 10488/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/228/results/ 2019-08-20 pass rate: 10489/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/231/results/ 2019-08-22 pass rate: 10489/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/233/results/ 2019-08-24 pass rate: 10489/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/235/results/ 2019-08-27 pass rate: 10489/10489, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/238/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From adinn at redhat.com Tue Aug 27 14:52:22 2019 From: adinn at redhat.com (Andrew Dinn) Date: Tue, 27 Aug 2019 15:52:22 +0100 Subject: [aarch64-port-dev ] RFR: [8u] JDK-8216350: AArch64: monitor unlock fast path not called Message-ID: <25037986-31aa-262d-3517-517c98e5a9b0@redhat.com> Could I please have a review of the following backport to the aarch64 jdk8u-shenandoah repo. JIRA: https://bugs.openjdk.java.net/browse/JDK-8216350 webrev: http://cr.openjdk.java.net/~adinn/8220668-jdk8u/webrev.00 The original patch failed to apply properly (after adjusting the file paths) because of 3 minor differences: 1) jdk8u-shenandoah aarch64.ad had tabs instead of spaces in some deleted lines 2) jdk8u-shenandoah aarch64.ad references VM_Version::cpu_cpuFeatures in both deleted and new lines where upstrema code references VM_Version::features 3) jdk8u-shenandoah assembler_aarch64.hpp omits a comment that gets matched in the upstream code (// rscratch1 is zero) Testing: tier1 tests succeed as before 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 shade at redhat.com Tue Aug 27 15:08:52 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Tue, 27 Aug 2019 17:08:52 +0200 Subject: [aarch64-port-dev ] RFR: [8u] JDK-8216350: AArch64: monitor unlock fast path not called In-Reply-To: <25037986-31aa-262d-3517-517c98e5a9b0@redhat.com> References: <25037986-31aa-262d-3517-517c98e5a9b0@redhat.com> Message-ID: <63691023-e35a-0443-82b8-932fcd6dd461@redhat.com> On 8/27/19 4:52 PM, Andrew Dinn wrote: > JIRA: https://bugs.openjdk.java.net/browse/JDK-8216350 > webrev: http://cr.openjdk.java.net/~adinn/8220668-jdk8u/webrev.00 Backport looks good to me. -- Thanks, -Aleksey From adinn at redhat.com Tue Aug 27 15:10:55 2019 From: adinn at redhat.com (adinn at redhat.com) Date: Tue, 27 Aug 2019 15:10:55 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 8216350: AArch64: monitor unlock fast path not called Message-ID: <201908271510.x7RFAtQs019655@aojmv0008.oracle.com> Changeset: c99ce621059e Author: ngasson Date: 2019-08-27 15:54 +0100 URL: https://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/c99ce621059e 8216350: AArch64: monitor unlock fast path not called Reviewed-by: aph, drwhite, fyang ! src/cpu/aarch64/vm/aarch64.ad ! src/cpu/aarch64/vm/assembler_aarch64.hpp From adinn at redhat.com Tue Aug 27 16:18:57 2019 From: adinn at redhat.com (Andrew Dinn) Date: Tue, 27 Aug 2019 17:18:57 +0100 Subject: [aarch64-port-dev ] RFR: [8u] JDK-8211320: AArch64: unsafe.compareAndSetByte() and unsafe.compareAndSetShort() c2 intrinsics broken with negative expected value Message-ID: <9634b7e2-f863-57d6-255f-2e6a2cb04f97@redhat.com> I was asked to look at backporting this patch to jdk8u-shenandoah. However, I don't believe a backport is appropriate. The patch updates ad file encodings and associated assembler cmpxchg method code for rules that match CompareAndExchangeB/S and CompareAndSwapB/S. Those cases do not apply to jdk8u where there are no CompareAndExchange rules and CompareAndSwap rules are only defined for I/L/N/P. I'm bery happy to be corrected if I am missing something. 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 shade at redhat.com Tue Aug 27 17:03:00 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Tue, 27 Aug 2019 19:03:00 +0200 Subject: [aarch64-port-dev ] RFR: [8u] JDK-8211320: AArch64: unsafe.compareAndSetByte() and unsafe.compareAndSetShort() c2 intrinsics broken with negative expected value In-Reply-To: <9634b7e2-f863-57d6-255f-2e6a2cb04f97@redhat.com> References: <9634b7e2-f863-57d6-255f-2e6a2cb04f97@redhat.com> Message-ID: <6d4bbfb3-8481-b1d1-4ea2-4ab47172666e@redhat.com> On 8/27/19 6:18 PM, Andrew Dinn wrote: > I was asked to look at backporting this patch to jdk8u-shenandoah. > However, I don't believe a backport is appropriate. > > The patch updates ad file encodings and associated assembler cmpxchg > method code for rules that match CompareAndExchangeB/S and > CompareAndSwapB/S. Those cases do not apply to jdk8u where there are no > CompareAndExchange rules and CompareAndSwap rules are only defined for > I/L/N/P. I'm bery happy to be corrected if I am missing something. The patch does not indeed look as important for 8u-aarch64. We are sure it does not affect I/L/N/P shapes, right? On the other hand, having a generic MacroAssembler::compare_eq and the new test might be beneficial. If we to adapt that to 8u-aarch64, would we have to mangle out a lot of test code, rendering the whole thing futile? I am leaning towards dropping this from 8u-aarch64 backports. -- Thanks, -Aleksey From aph at redhat.com Tue Aug 27 17:11:10 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 27 Aug 2019 18:11:10 +0100 Subject: [aarch64-port-dev ] RFR: [8u] JDK-8211320: AArch64: unsafe.compareAndSetByte() and unsafe.compareAndSetShort() c2 intrinsics broken with negative expected value In-Reply-To: <6d4bbfb3-8481-b1d1-4ea2-4ab47172666e@redhat.com> References: <9634b7e2-f863-57d6-255f-2e6a2cb04f97@redhat.com> <6d4bbfb3-8481-b1d1-4ea2-4ab47172666e@redhat.com> Message-ID: <5824e064-a1d2-82dd-d25b-54ac5c9e5098@redhat.com> On 8/27/19 6:03 PM, Aleksey Shipilev wrote: > I am leaning towards dropping this from 8u-aarch64 backports. You and me both. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From felix.yang at huawei.com Wed Aug 28 07:01:01 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Wed, 28 Aug 2019 07:01:01 +0000 Subject: [aarch64-port-dev ] RFR: [8u] 8209835: Aarch64: elide barriers on all volatile operations Message-ID: Hi, Could I have a review for this backport to aarch64 8u repo please? Webrev: http://cr.openjdk.java.net/~fyang/8209835-8u-backport/webrev.00/ Changes related to CompareAndExchange* and WeakCompareAndSwap* in the original patch are not needed for the aarch64 8u repo. Volatile access inconsistency still exists for some unsafe operations. One example is AtomicReference. For the volatile field 'value', compareAndSet() method accesses it through unsafe.compareAndSwapObject(). And getAndSet() method accessed it through unsafe.getAndSetObject(). Currently, C2 will emit ldar & stlr to implement unsafe.compareAndSwapObject(), but that is not the case for unsafe.getAndSetObject(). C2 still emits explicit dmb instructions to implement unsafe.getAndSetObject(). Jtreg tested with aarch64 fastdebug build. Also passed jcstress test. Corresponding 11u backport link: https://mail.openjdk.java.net/pipermail/jdk-updates-dev/2019-August/001740.html Thanks, Felix From aph at redhat.com Wed Aug 28 08:04:45 2019 From: aph at redhat.com (Andrew Haley) Date: Wed, 28 Aug 2019 09:04:45 +0100 Subject: [aarch64-port-dev ] RFR: [8u] 8209835: Aarch64: elide barriers on all volatile operations In-Reply-To: References: Message-ID: On 8/28/19 8:01 AM, Yangfei (Felix) wrote: > Webrev: http://cr.openjdk.java.net/~fyang/8209835-8u-backport/webrev.00/ > Changes related to CompareAndExchange* and WeakCompareAndSwap* in the original patch are not needed for the aarch64 8u repo. > > Volatile access inconsistency still exists for some unsafe operations. One example is AtomicReference. > For the volatile field 'value', compareAndSet() method accesses it through unsafe.compareAndSwapObject(). > And getAndSet() method accessed it through unsafe.getAndSetObject(). > Currently, C2 will emit ldar & stlr to implement unsafe.compareAndSwapObject(), but that is not the case for unsafe.getAndSetObject(). > > C2 still emits explicit dmb instructions to implement unsafe.getAndSetObject(). I am not convinced. Please provide me with a test case of incorrect behaviour. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From adinn at redhat.com Wed Aug 28 09:12:10 2019 From: adinn at redhat.com (Andrew Dinn) Date: Wed, 28 Aug 2019 10:12:10 +0100 Subject: [aarch64-port-dev ] RFR: [8u] JDK-8219006: AArch64: Register corruption in slow subtype check Message-ID: <160bcfbd-4af4-ab51-e4c9-0c400e4168c1@redhat.com> I would like permission to backport JDK-8219006 to the aarch64 jdk8u-shenandoah repo. JIRA: https://bugs.openjdk.java.net/browse/JDK-8219006 The upstream jdk11u patch applies cleanly Why: The patch does not affect product code but it can cause a crash in debug builds. Testing: tier1 tests complete as before (modulo two tests that timed out before patching but completed successfully within the allotted time after patching -- I was running other jobs in the before case). 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 felix.yang at huawei.com Wed Aug 28 09:18:51 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Wed, 28 Aug 2019 09:18:51 +0000 Subject: [aarch64-port-dev ] RFR: [8u] 8209835: Aarch64: elide barriers on all volatile operations Message-ID: >> Volatile access inconsistency still exists for some unsafe operations. One example is AtomicReference. >> For the volatile field 'value', compareAndSet() method accesses it through unsafe.compareAndSwapObject(). >> And getAndSet() method accessed it through unsafe.getAndSetObject(). >> Currently, C2 will emit ldar & stlr to implement unsafe.compareAndSwapObject(), but that is not the case for unsafe.getAndSetObject(). >> >> C2 still emits explicit dmb instructions to implement unsafe.getAndSetObject(). > I am not convinced. Please provide me with a test case of incorrect behaviour. Well, I think I won't be able to provide such a test case after some throughts. Now I agree that this will not affect basic functionality. As we have handled unsafe.compareAndSwap, I don't see a reason to not handle unsafe.getAndSet: the risk should be low and we get consistent and improved C2 JIT code. What do you think? Thanks, Felix From adinn at redhat.com Wed Aug 28 09:20:21 2019 From: adinn at redhat.com (Andrew Dinn) Date: Wed, 28 Aug 2019 10:20:21 +0100 Subject: [aarch64-port-dev ] RFR: [8u] JDK-8211320: AArch64: unsafe.compareAndSetByte() and unsafe.compareAndSetShort() c2 intrinsics broken with negative expected value In-Reply-To: <5824e064-a1d2-82dd-d25b-54ac5c9e5098@redhat.com> References: <9634b7e2-f863-57d6-255f-2e6a2cb04f97@redhat.com> <6d4bbfb3-8481-b1d1-4ea2-4ab47172666e@redhat.com> <5824e064-a1d2-82dd-d25b-54ac5c9e5098@redhat.com> Message-ID: <7e52785b-ccee-f759-bb78-569e69dadabc@redhat.com> On 27/08/2019 18:11, Andrew Haley wrote: > On 8/27/19 6:03 PM, Aleksey Shipilev wrote: >> I am leaning towards dropping this from 8u-aarch64 backports. > > You and me both. Ok, I'm going to drop this backport then. At first I was, as per Aleksey, concerned that method MacroAssembler::compare_eq might be needed for 8217368: AArch64: C2 recursive stack locking optimisation not triggered (that's the one I split into two parts where the first part replaces inline compare and exchange encoding in fast_lock/unlock with a call to MacroAssembler::cmpxchg). However, compare_eq is not needed. The existing 32/64 bit (word/xword) cmpxchg code caters for the fast_lock/unlock case. 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 Wed Aug 28 09:27:19 2019 From: aph at redhat.com (Andrew Haley) Date: Wed, 28 Aug 2019 10:27:19 +0100 Subject: [aarch64-port-dev ] RFR: [8u] 8209835: Aarch64: elide barriers on all volatile operations In-Reply-To: References: Message-ID: On 8/28/19 10:18 AM, Yangfei (Felix) wrote: > Well, I think I won't be able to provide such a test case after some > throughts. Now I agree that this will not affect basic > functionality. As we have handled unsafe.compareAndSwap, I don't > see a reason to not handle unsafe.getAndSet: the risk should be low > and we get consistent and improved C2 JIT code. What do you think? I think that's a powerful argument for the development code because it's an improvement; conversely I don't think it's an argument for a backport. Having said that, I can sort-of imagine a jcstress failure if we had a test that was doing compareAndSwap in one thread and getAndSet in another. That would be a seriously compelling reason for a backport! It would be interesting to see such a jcstress test. Even if the test does not fail, we could look at the generated code to see if it might fail according to the Arm memory model. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From felix.yang at huawei.com Wed Aug 28 10:39:19 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Wed, 28 Aug 2019 10:39:19 +0000 Subject: [aarch64-port-dev ] RFR: [8u] 8209835: Aarch64: elide barriers on all volatile operations Message-ID: On 8/28/19 10:18 AM, Yangfei (Felix) wrote: >> Well, I think I won't be able to provide such a test case after some >> throughts. Now I agree that this will not affect basic functionality. >> As we have handled unsafe.compareAndSwap, I don't see a reason to not >> handle unsafe.getAndSet: the risk should be low and we get consistent >> and improved C2 JIT code. What do you think? > I think that's a powerful argument for the development code because it's an improvement; conversely I don't think it's an argument for a backport. > Having said that, I can sort-of imagine a jcstress failure if we had a test that was doing compareAndSwap in one thread and getAndSet in another. That would be a seriously compelling reason for a backport! Can you elaborate more please? especially the possible code sequence. Currently, we have C2 JIT for getAndSet like this: 33 ;; membar_release 34 0x0000ffffa416ae74: dmb ish 35 ;; 0x40000000000 36 0x0000ffffa416ae78: orr x11, xzr, #0x40000000000 37 0x0000ffffa416ae7c: add x10, x1, #0x10 38 0x0000ffffa416ae80: prfm pstl1strm, [x10] 39 0x0000ffffa416ae84: ldxr x9, [x10] 40 0x0000ffffa416ae88: stxr w8, x11, [x10] 41 0x0000ffffa416ae8c: cbnz w8, 0x0000ffffa416ae84 42 0x0000ffffa416ae90: mov x10, x9 43 ;; membar_acquire 44 0x0000ffffa416ae94: dmb ishld ;*invokevirtual getAndSetLong I think the two dmb instructions at the head and tail should ensure the consistency. Isn't it? > It would be interesting to see such a jcstress test. Even if the test does not fail, we could look at the generated code to see if it might fail according to the Arm memory model. From adinn at redhat.com Wed Aug 28 13:48:19 2019 From: adinn at redhat.com (Andrew Dinn) Date: Wed, 28 Aug 2019 14:48:19 +0100 Subject: [aarch64-port-dev ] RFR: [8u] JDK-8219006: AArch64: Register corruption in slow subtype check Message-ID: <62165d90-6c3e-285f-67e9-8491a219c255@redhat.com> I would like permission to backport JDK-8219006 to the aarch64 jdk8u-shenandoah repo. JIRA: https://bugs.openjdk.java.net/browse/JDK-8219006 The upstream jdk11u patch applies cleanly Why: The patch does not affect product code but it can cause a crash in debug builds. Testing: tier1 tests complete as before (modulo two tests that timed out before patching but completed successfully within the allotted time after patching -- I was running other jobs in the before case). 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 Thu Aug 29 08:24:04 2019 From: aph at redhat.com (Andrew Haley) Date: Thu, 29 Aug 2019 09:24:04 +0100 Subject: [aarch64-port-dev ] RFR: [8u] JDK-8219006: AArch64: Register corruption in slow subtype check In-Reply-To: <62165d90-6c3e-285f-67e9-8491a219c255@redhat.com> References: <62165d90-6c3e-285f-67e9-8491a219c255@redhat.com> Message-ID: <2c3b0f1b-a697-44b3-dff5-e1d5671a6a8e@redhat.com> On 8/28/19 2:48 PM, Andrew Dinn wrote: > I would like permission to backport JDK-8219006 to the aarch64 > jdk8u-shenandoah repo. > > JIRA: https://bugs.openjdk.java.net/browse/JDK-8219006 > > The upstream jdk11u patch applies cleanly OK, I'm sure that's fine. -- Andrew Haley (he/him) Java Platform Lead Engineer Red Hat UK Ltd. https://keybase.io/andrewhaley EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671