From Nick.Gasson at arm.com Fri Feb 1 02:50:25 2019 From: Nick.Gasson at arm.com (Nick Gasson (Arm Technology China)) Date: Fri, 1 Feb 2019 02:50:25 +0000 Subject: [aarch64-port-dev ] RFC: 64 bit literal oops In-Reply-To: References: Message-ID: <3a606763-b49f-b902-f4d3-180c386bed96@arm.com> Hi Stuart Just a few minor comments from looking through your patch. src/hotspot/cpu/aarch64/c1_CodeStubs_aarch64.cpp +// SRDM: Use64BitLiteralAddresses isn't initialized for the static _patch_info_offset to be uses. +int PatchingStub::patch_info_offset() { return -NativeGeneralJump::get_instruction_size(); } "to be uses" -> "to be used"? src/hotspot/cpu/aarch64/globals_aarch64.hpp + experimental(bool, Use64BitLiteralAddresses, false, \ + "Use 64 bit in literal addresses instead of 48 bits.") "Use 64 *bits* in ..." or "Use 64 bit literal addresses instead of 48 bit"? src/hotspot/cpu/aarch64/jvmciCodeInstaller_aarch64.cpp + // is therefore disables Use64BitLiteralAddresses until support is enabled. s/is/it/ + // mov, movk, movk, [movk] <- SRDM This fails with Use64BitLiteralAddresses Can we make this assert(!Use64BitLiteralAddresses, "...")? src/hotspot/cpu/aarch64/macroAssembler_aarch64.cpp + + if (Use64BitLiteralAddresses) { + assert(nativeInstruction_at(insn_addr+12)->is_movk(), "wrong insns in patch"); + Instruction_aarch64::patch(insn_addr+12, 20, 5, (dest >>= 16) & 0xffff); + instructions = 4; + } Does it make sense to add `else assert(dest == 0, ">48 bit literal address without Use64BitLiteralAddresses");' here? src/hotspot/cpu/aarch64/nativeInst_aarch64.cpp + if (!Use64BitLiteralAddresses) { + // movz, movk, movk. + return 3 * 4; + } else { + return 4 * 4; + } It's clearer if the * 4 is * NativeInstruction::instruction_size; src/hotspot/cpu/aarch64/nativeInst_aarch64.hpp + return 4 * 4; Same here. src/hotspot/share/aot/aotLoader.cpp + if (Use64BitLiteralAddresses && UseAOT) { + warning("64-bit Literal Addresses disabled due to UseAOT."); + FLAG_SET_CMDLINE(bool, UseAOT, false); + } Shouldn't it be FLAG_SET_CMDLINE(bool, Use64BitLiteralAddresses, false) to match the warning? Probably don't need to capitalize "Literal Addresses". Thanks, Nick On 31/01/2019 21:55, Stuart Monteith wrote: > I've redone the patch such that whether or not it is an oop, > addresses are emitted and patched as 64-bit (movz + 3 x movk) when > -XX:+Use64BitLiteralAdddresses is passed. > > I've annotated some more sections to clarify what instructions are > being patched or sized, as well as some areas where it hasn't changed > - it was worthwhile to do thi > The Aarch64_specific_constant::instruction_size enum has been changed > to a method. This has encroached on shared code. Arguably this could > do with even more refactoring in NativeInst_aarch.(cpp|hpp) and the > users thereof if it is to be consistent. > > Regarding JVM CI and Graal - ZGC doesn't support them yet. Graal will > need to be changed to recognise the option and conditionally emit > 64-bit addresses (at least in > AArch64MacroAssembler::movNativeAddress(Register, long) > I've added some more logic to disable Use64BitLiteralAddresses when > UseAOT or JVMCI are enabled. > > The patch is: > http://cr.openjdk.java.net/~smonteith/oop64/webrev-20190130/ > > I've opened a bug in JBS: https://bugs.openjdk.java.net/browse/JDK-8216491 > > I've been trying to track down the source of some of the constants for > the sizes of code. In one instance we have: > http://cr.openjdk.java.net/~smonteith/oop64/webrev-20190130/src/hotspot/cpu/aarch64/c1_LIRAssembler_aarch64.hpp.udiff.html > > ... there are apparently 12 instructions for each call stub. The > emit_static_call_stub() method only uses 8 instructions, but with > Use64BitLiteralAddresses enabled the warning "compilation bailout: > exception handler overflow" is generated. > I've changed the code to emit 14 instructions instead, but I've yet to > find the call stub that requires 12 instructions. > > I'll follow up with the ZGC patch soon - there was a change upstream > to lea that needs to be accommodated. > > BR, > Stuart > > > > > > On Mon, 3 Dec 2018 at 18:40, Andrew Haley wrote: >> >> On 12/3/18 4:53 PM, Stuart Monteith wrote: >> >>> There is another possible option, which is to just avoid 48-bit >>> literals, and just use 64-bit unconditionally everywhere. It would >>> mean that we could be easily consistent and 52-bit VA would be easier >>> to implement on top of it. Again, I seek people's opinions. >> >> Could well be. I am starting to wonder if it is worth the effort. >> Maybe the best thing to do is have a global 48- to 64-bit switch >> and use it everywhere we want a pointer literal. >> >> Please don't put code of any complexity into header files. Put it >> into .c files instead. >> >> The logic in MacroAssembler::movoop is a already a mess, and >> adding an isOop flag to pass to doesn't help. I think it would >> make more sense to have explicit 48- and 64-bit mov methods, and >> let MacroAssembler::mov(Register, Address) control which one is >> called. >> >> This hunk makes no sense. The comment directly contradicts >> the code: >> >> enum Aarch64_specific_constants { >> instruction_size = 3 * 4, // movz, movk, movk, [movk]. See movptr(). >> instruction_offset = 0, >> displacement_offset = 0, >> }; >> >> It makes no sense to have instruction_size be a constant here. >> I guess it never did. >> >> -- >> Andrew Haley >> Java Platform Lead Engineer >> Red Hat UK Ltd. >> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From felix.yang at huawei.com Fri Feb 1 06:05:15 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Fri, 1 Feb 2019 06:05:15 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> Message-ID: Hi, That's a good catch. Also LGTM (Not an official reviewer). I will prepare a webrev. BTW: Should this fix go to the aarch64 jdk8u repos? Thanks, Felix > > > Could this be a potential bug? > > We've never seen any test failures, but that doesn't prove > anything. It is a bug, so we should fix it. Thank you. > > -- From Nick.Gasson at arm.com Fri Feb 1 09:22:39 2019 From: Nick.Gasson at arm.com (Nick Gasson (Arm Technology China)) Date: Fri, 1 Feb 2019 09:22:39 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command Message-ID: Hi all, Please review this patch to fix a crash in the clhsdb "jstack -v" command on AArch64: Bug: https://bugs.openjdk.java.net/browse/JDK-8209413 Webrev: http://cr.openjdk.java.net/~ngasson/8209413/webrev.01/ On AArch64, if you use "jhsdb clhsdb --pid=..." to attach a debugger to a Java process, and then run "jstack -v" while any thread is executing a native method, you will get a NullPointerException like this: java.lang.NullPointerException at jdk.hotspot.agent/sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:83) at jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor$24.doit(CommandProcessor.java:1066) The problem is this constructor of AARCH64Frame, which is called by when trying to construct the frame for the native method (wrapper): AARCH64Frame(Address raw_sp, Address raw_fp) It takes the last-known Java SP and FP, and tries to find the PC following the BL instruction that jumped to the native code. At the moment it assumes this is at SP[-1]: this.pc = raw_sp.getAddressAt(-1 * VM.getVM().getAddressSize()); I think this comes from x86 where the CALL instruction will push it there. The fix in this patch is to scan the stack of the native (C++) function looking for a pointer back to the frame of the native wrapper. If we find this then the LR on entry should be saved in the stack slot above. This fails if the native function stack frame is too big, or it's a leaf function that didn't push FP/LR. But in this case setting this.pc to null makes the frame object look invalid and so won't be printed, instead of crashing. Sample output from the ClhsdbJstack.java jtreg test which passes now with this patch: - java.lang.Thread.sleep(long) @bci=0, pc=0x0000ffffa05bb68c, Method*=0x0000000800143410 (Compiled frame; information may be imprecise) - jdk.test.lib.apps.LingeredApp.main(java.lang.String[]) @bci=53, line=502, pc=0x0000ffff9892572c, Method*=0x0000ffff2e870d48 (Interpreted frame) An alternative to scanning the native functions's stack might be to use the last-known Java PC saved by set_last_Java_frame, this is off by a few instructions but I don't think that matters. But this constructor potentially has other users so we'd have to fix it anyway. Thanks, Nick From felix.yang at huawei.com Fri Feb 1 14:10:49 2019 From: felix.yang at huawei.com (felix.yang at huawei.com) Date: Fri, 01 Feb 2019 14:10:49 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/hotspot: 8215951: AArch64: jtreg test vmTestbase/nsk/jvmti/PopFrame/popframe005 segfaults Message-ID: <201902011410.x11EAo4G027701@aojmv0008.oracle.com> Changeset: aaf813bab520 Author: fyang Date: 2019-01-03 13:53 +0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/aaf813bab520 8215951: AArch64: jtreg test vmTestbase/nsk/jvmti/PopFrame/popframe005 segfaults Reviewed-by: aph Contributed-by: nick.gasson at arm.com ! src/cpu/aarch64/vm/templateInterpreter_aarch64.cpp From felix.yang at huawei.com Fri Feb 1 14:12:01 2019 From: felix.yang at huawei.com (felix.yang at huawei.com) Date: Fri, 01 Feb 2019 14:12:01 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 8215951: AArch64: jtreg test vmTestbase/nsk/jvmti/PopFrame/popframe005 segfaults Message-ID: <201902011412.x11EC12O028186@aojmv0008.oracle.com> Changeset: 67b1ac19ec82 Author: fyang Date: 2019-01-03 13:53 +0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/67b1ac19ec82 8215951: AArch64: jtreg test vmTestbase/nsk/jvmti/PopFrame/popframe005 segfaults Reviewed-by: aph Contributed-by: nick.gasson at arm.com ! src/cpu/aarch64/vm/templateInterpreter_aarch64.cpp From felix.yang at huawei.com Sat Feb 2 02:46:53 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Sat, 2 Feb 2019 02:46:53 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> Message-ID: Webrev: http://cr.openjdk.java.net/~fyang/8218185/webrev.00/ 8218185: aarch64: missing LoadStore barrier in TemplateTable::putfield_or_static Reviewed-by: aph Contributed-by: lunliu93 at gmail.com Jcstress tested, OK? Thanks, Felix > > Hi, > > That's a good catch. Also LGTM (Not an official reviewer). > I will prepare a webrev. BTW: Should this fix go to the aarch64 jdk8u repos? > > Thanks, > Felix > > > > > > Could this be a potential bug? > > > > We've never seen any test failures, but that doesn't prove > > anything. It is a bug, so we should fix it. Thank you. > > > > -- From patrick at os.amperecomputing.com Sat Feb 2 03:47:27 2019 From: patrick at os.amperecomputing.com (Patrick Zhang) Date: Sat, 2 Feb 2019 03:47:27 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> Message-ID: I am interested in this topic, here are two questions. 1. Is the right process that the patch firstly gets applied on jdk/jdk/../aarch64, then backported to jdk8u? BTW, I wonder if there is any "failed" test, and right now could get "pass" with the patch? http://hg.openjdk.java.net/jdk/jdk/file/00baec44c94e/src/hotspot/cpu/aarch64/templateTable_aarch64.cpp#l2723 2. Compared the original patch (back to Jun 2013) on aarch64-port/jdk8u with x86's implementation, at the end of the putfield_or_static function, was the StoreStore intentionally dropped? http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/ed26923dcc83#l3.118 http://hg.openjdk.java.net/jdk/jdk/file/00baec44c94e/src/hotspot/cpu/x86/templateTable_x86.cpp#l3134 - // TODO : restore this volatile barrier call - // - // Check for volatile store - // __ andw(r3, r3, r3); - // __ br(Assembler::EQ, notVolatile); - // volatile_barrier(Assembler::Membar_mask_bits(Assembler::StoreLoad | - // Assembler::StoreStore)); - // __ bind(notVolatile); + { + Label notVolatile; + __ tbz(r3, ConstantPoolCacheEntry::is_volatile_shift, notVolatile); + __ membar(MacroAssembler::Membar_mask_bits(MacroAssembler::StoreLoad)); + __ bind(notVolatile); + } Regards Patrick -----Original Message----- From: aarch64-port-dev On Behalf Of Andrew Haley Sent: Thursday, January 31, 2019 6:39 PM To: Lun Liu ; aarch64-port-dev at openjdk.java.net Subject: Re: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? On 1/30/19 8:36 PM, Lun Liu wrote: > I noticed in the template interpreter only a StoreStore barrier is > used before a volatile write. According to JMM cookbook I think a > LoadStore barrier is also needed to prevent reordering between a > normal read and a volatile write. Yes, you're right. When I translated the code from x86, I mistakenly did this: @@ -2382,13 +2382,16 @@ jvmti_post_field_mod(rcpool, index, is_static); load_field_cp_cache_entry(obj, cache, index, off, flags, is_static); - // [jk] not needed currently - // volatile_barrier(Assembler::Membar_mask_bits(Assembler::LoadStore | - // Assembler::StoreStore)); - - Label notVolatile, Done; + Label Done; __ mov(r5, flags); + { + Label notVolatile; + __ tbz(r5, ConstantPoolCacheEntry::is_volatile_shift, notVolatile); + __ membar(MacroAssembler::Membar_mask_bits(MacroAssembler::StoreStore)); + __ bind(notVolatile); + } + // field address const Address field(obj, off); As you can see, the x86 comment is correct, but I didn't follow it. > In the template interpreter it seems like LoadLoad | LoadStore > barriers are inserted after both normal read and volatile read so it > should be fine but I think this might cause a problem if the compiler > generates a normal read using dmb barriers and the interpreter is > executing the volatile write. I'm not sure. The LoadStore should prevent a load (any kind) from being reordered with the volatile store. This only matters if another thread stores to the memory in the load, and that store in the other thread is sequenced after the volatile store in this thread. > Could this be a potential bug? We've never seen any test failures, but that doesn't prove anything. It is a bug, so we should fix it. Thank you. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Sat Feb 2 10:25:24 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sat, 2 Feb 2019 10:25:24 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 12 on AArch64 Message-ID: <662822966.6055.1549103125288.JavaMail.jenkins@4bd97a938c38> 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/jdk12/openjdk-jtreg-nightly-tests/summary/2019/031/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 5,510; fail: 4; error: 1; not run: 93 Build 1: aarch64/2019/jan/25 pass: 5,523; fail: 7; not run: 93 Build 2: aarch64/2019/jan/27 pass: 5,524; fail: 5; error: 1; not run: 93 Build 3: aarch64/2019/jan/29 pass: 5,524; fail: 5; error: 1; not run: 93 Build 4: aarch64/2019/jan/31 pass: 5,518; fail: 5; error: 1; not run: 93 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 8,528; fail: 482; error: 29 Build 1: aarch64/2019/jan/25 pass: 8,522; fail: 491; error: 27 Build 2: aarch64/2019/jan/27 pass: 8,540; fail: 488; error: 12 Build 3: aarch64/2019/jan/29 pass: 8,543; fail: 483; error: 14 Build 4: aarch64/2019/jan/31 pass: 8,530; fail: 491; error: 21 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 3,992 Build 1: aarch64/2019/jan/25 pass: 3,992 Build 2: aarch64/2019/jan/27 pass: 3,992 Build 3: aarch64/2019/jan/29 pass: 3,992 Build 4: aarch64/2019/jan/31 pass: 3,992 Previous results can be found here: http://openjdk.linaro.org/jdk12/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.29x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk12/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/jdk12/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-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/022/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/027/results/ 2019-01-30 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/031/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/ From ci_notify at linaro.org Sat Feb 2 10:29:49 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sat, 2 Feb 2019 10:29:49 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 11u on AArch64 Message-ID: <177257734.6057.1549103389459.JavaMail.jenkins@4bd97a938c38> 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/031/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 5,705; fail: 9; not run: 11,618 Build 1: aarch64/2019/jan/12 pass: 5,705; fail: 9; not run: 11,618 Build 2: aarch64/2019/jan/15 pass: 5,705; fail: 9; not run: 11,618 Build 3: aarch64/2019/jan/17 pass: 5,709; fail: 9; not run: 11,618 Build 4: aarch64/2019/jan/22 pass: 5,709; fail: 9; not run: 11,618 Build 5: aarch64/2019/jan/24 pass: 5,708; fail: 10; not run: 11,618 Build 6: aarch64/2019/jan/29 pass: 5,709; fail: 9; not run: 11,618 Build 7: aarch64/2019/jan/31 pass: 5,707; fail: 11; not run: 11,618 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 8,344; fail: 522; error: 29 Build 1: aarch64/2019/jan/12 pass: 8,376; fail: 496; error: 23 Build 2: aarch64/2019/jan/15 pass: 8,353; fail: 510; error: 32 Build 3: aarch64/2019/jan/17 pass: 8,386; fail: 493; error: 19 Build 4: aarch64/2019/jan/22 pass: 8,369; fail: 506; error: 23 Build 5: aarch64/2019/jan/24 pass: 8,366; fail: 507; error: 25 Build 6: aarch64/2019/jan/29 pass: 8,353; fail: 524; error: 22 Build 7: aarch64/2019/jan/31 pass: 8,372; fail: 502; error: 25 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 3,903 Build 1: aarch64/2019/jan/12 pass: 3,903 Build 2: aarch64/2019/jan/15 pass: 3,903 Build 3: aarch64/2019/jan/17 pass: 3,903 Build 4: aarch64/2019/jan/22 pass: 3,903 Build 5: aarch64/2019/jan/24 pass: 3,903 Build 6: aarch64/2019/jan/29 pass: 3,903 Build 7: aarch64/2019/jan/31 pass: 3,903 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.54x Relative performance: Server critical-jOPS (nc): 7.82x 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-01-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/010/results/ 2019-01-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/012/results/ 2019-01-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/015/results/ 2019-01-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/017/results/ 2019-01-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/022/results/ 2019-01-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/024/results/ 2019-01-30 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/031/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/ From aph at redhat.com Sat Feb 2 13:43:24 2019 From: aph at redhat.com (Andrew Haley) Date: Sat, 2 Feb 2019 13:43:24 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> Message-ID: <396b9bb2-48c7-d844-ce54-3d397a48f698@redhat.com> On 2/2/19 3:47 AM, Patrick Zhang wrote: > 1. Is the right process that the patch firstly gets applied on jdk/jdk/../aarch64, then backported to jdk8u? Yes. > BTW, I wonder if there is any "failed" test, and right now could get "pass" with the patch? > http://hg.openjdk.java.net/jdk/jdk/file/00baec44c94e/src/hotspot/cpu/aarch64/templateTable_aarch64.cpp#l2723 We could try to write a custom jcstress test, but I don't think there's much point.. > 2. Compared the original patch (back to Jun 2013) on aarch64-port/jdk8u with x86's implementation, at the end of the putfield_or_static function, was the StoreStore intentionally dropped? > http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/ed26923dcc83#l3.118 > http://hg.openjdk.java.net/jdk/jdk/file/00baec44c94e/src/hotspot/cpu/x86/templateTable_x86.cpp#l3134 > - // TODO : restore this volatile barrier call It's not necessary because of the x86 TSO memory model. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Sat Feb 2 14:39:14 2019 From: aph at redhat.com (Andrew Haley) Date: Sat, 2 Feb 2019 14:39:14 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> Message-ID: On 2/2/19 2:46 AM, Yangfei (Felix) wrote: > Webrev: http://cr.openjdk.java.net/~fyang/8218185/webrev.00/ > > 8218185: aarch64: missing LoadStore barrier in TemplateTable::putfield_or_static > Reviewed-by: aph > Contributed-by: lunliu93 at gmail.com > > Jcstress tested, OK? OK, thanks. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From patrick at os.amperecomputing.com Sun Feb 3 02:55:28 2019 From: patrick at os.amperecomputing.com (Patrick Zhang) Date: Sun, 3 Feb 2019 02:55:28 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: <396b9bb2-48c7-d844-ce54-3d397a48f698@redhat.com> References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> <396b9bb2-48c7-d844-ce54-3d397a48f698@redhat.com> Message-ID: > It's not necessary because of the x86 TSO memory model. Hi Andrew, Could you please explain this a little bit more? It looks aarch64 has a StoreLoad there, while x86 has StoreLoad|StoreStore, did you mean the StoreStore can be dropped by aarch64 because x86 TSO needs more protection here? Thanks. http://hg.openjdk.java.net/jdk/jdk/file/00baec44c94e/src/hotspot/cpu/aarch64/templateTable_aarch64.cpp#l2723 __ membar(MacroAssembler::StoreLoad); http://hg.openjdk.java.net/jdk/jdk/file/00baec44c94e/src/hotspot/cpu/x86/templateTable_x86.cpp#l3134 volatile_barrier(Assembler::Membar_mask_bits(Assembler::StoreLoad | Assembler::StoreStore)); Regards Patrick -----Original Message----- From: Andrew Haley Sent: Saturday, February 2, 2019 9:43 PM To: Patrick Zhang ; Lun Liu ; aarch64-port-dev at openjdk.java.net Cc: jiangning.liu at os.amperecomputing.com Subject: Re: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? On 2/2/19 3:47 AM, Patrick Zhang wrote: > 1. Is the right process that the patch firstly gets applied on jdk/jdk/../aarch64, then backported to jdk8u? Yes. > BTW, I wonder if there is any "failed" test, and right now could get "pass" with the patch? > http://hg.openjdk.java.net/jdk/jdk/file/00baec44c94e/src/hotspot/cpu/aarch64/templateTable_aarch64.cpp#l2723 We could try to write a custom jcstress test, but I don't think there's much point.. > 2. Compared the original patch (back to Jun 2013) on aarch64-port/jdk8u with x86's implementation, at the end of the putfield_or_static function, was the StoreStore intentionally dropped? > http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/ed26923dcc83#l3.118 > http://hg.openjdk.java.net/jdk/jdk/file/00baec44c94e/src/hotspot/cpu/x86/templateTable_x86.cpp#l3134 > - // TODO : restore this volatile barrier call It's not necessary because of the x86 TSO memory model. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From Nick.Gasson at arm.com Sun Feb 3 03:01:38 2019 From: Nick.Gasson at arm.com (Nick Gasson (Arm Technology China)) Date: Sun, 3 Feb 2019 03:01:38 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: <4de13272-0f19-7897-3f4d-f4b5b56ca73f@oracle.com> References: <4de13272-0f19-7897-3f4d-f4b5b56ca73f@oracle.com> Message-ID: <5a9ebe53-0dea-6259-c070-6ed090f6895f@arm.com> Hi Jini, On 02/02/2019 02:16, Jini George wrote: > Do we reach here after AARCH64CurrentFrameGuess.run() fails to get the > PC ? Yes, that's right. It's the else branch (not interpreter and not compiler) that sets this.pc to null. > If so, was wondering if it would make more sense to scan from the > top of stack sp obtained from > context.getRegisterAsAddress(AARCH64ThreadContext.SP) to the sp of the > last known java frame with thread.getLastJavaSP() in > AARCH64CurrentFrameGuess.run() -- otherwise was wondering if we are > risking an exception by running off the top of the stack while scanning > in the upward direction (towards lower addresses) for > CALLEE_FRAME_SEARCH_LIMIT * addressSize from the previous Java SP > (though the scan range is small). > I think this is much better, thanks. But we still have the problem that the two-argument AARCH64Frame constructor is wrong: I don't think it's ever correct to assume the PC is at SP[-1]. And so we need to fix the other uses of it. I've made another patch that moves the frame scanning into LinuxAARCH64JavaThreadPDAccess.java, searching between the last-known Java SP and and current thread SP as described above. And we now use this to find a PC any time we would have called the two argument constructor before. http://cr.openjdk.java.net/~ngasson/8209413/webrev.02/ Please let me know what you think. + Assert.that(jcw.getLastJavaPC() != null, "last Java pc should be set"); I believe this is OK because the last Java SP/FP/PC are set by MacroAssembler::set_last_Java_frame, and I can't see any case where it would set SP and FP but not PC. Thanks, Nick From ci_notify at linaro.org Sun Feb 3 16:24:13 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sun, 3 Feb 2019 16:24:13 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 11u on AArch64 Message-ID: <178960454.11.1549211053988.JavaMail.jenkins@dc828b94788c> 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/033/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 5,705; fail: 9; not run: 11,618 Build 1: aarch64/2019/jan/12 pass: 5,705; fail: 9; not run: 11,618 Build 2: aarch64/2019/jan/15 pass: 5,705; fail: 9; not run: 11,618 Build 3: aarch64/2019/jan/17 pass: 5,709; fail: 9; not run: 11,618 Build 4: aarch64/2019/jan/22 pass: 5,709; fail: 9; not run: 11,618 Build 5: aarch64/2019/jan/24 pass: 5,708; fail: 10; not run: 11,618 Build 6: aarch64/2019/jan/29 pass: 5,709; fail: 9; not run: 11,618 Build 7: aarch64/2019/jan/31 pass: 5,707; fail: 11; not run: 11,618 Build 8: aarch64/2019/feb/02 pass: 5,708; fail: 10; not run: 11,618 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 8,344; fail: 522; error: 29 Build 1: aarch64/2019/jan/12 pass: 8,376; fail: 496; error: 23 Build 2: aarch64/2019/jan/15 pass: 8,353; fail: 510; error: 32 Build 3: aarch64/2019/jan/17 pass: 8,386; fail: 493; error: 19 Build 4: aarch64/2019/jan/22 pass: 8,369; fail: 506; error: 23 Build 5: aarch64/2019/jan/24 pass: 8,366; fail: 507; error: 25 Build 6: aarch64/2019/jan/29 pass: 8,353; fail: 524; error: 22 Build 7: aarch64/2019/jan/31 pass: 8,372; fail: 502; error: 25 Build 8: aarch64/2019/feb/02 pass: 8,378; fail: 501; error: 21 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 3,903 Build 1: aarch64/2019/jan/12 pass: 3,903 Build 2: aarch64/2019/jan/15 pass: 3,903 Build 3: aarch64/2019/jan/17 pass: 3,903 Build 4: aarch64/2019/jan/22 pass: 3,903 Build 5: aarch64/2019/jan/24 pass: 3,903 Build 6: aarch64/2019/jan/29 pass: 3,903 Build 7: aarch64/2019/jan/31 pass: 3,903 Build 8: aarch64/2019/feb/02 pass: 3,903 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.54x Relative performance: Server critical-jOPS (nc): 7.97x 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-01-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/010/results/ 2019-01-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/012/results/ 2019-01-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/015/results/ 2019-01-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/017/results/ 2019-01-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/022/results/ 2019-01-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/024/results/ 2019-01-30 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/031/results/ 2019-02-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/033/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/ From aph at redhat.com Sun Feb 3 18:26:24 2019 From: aph at redhat.com (Andrew Haley) Date: Sun, 3 Feb 2019 18:26:24 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> <396b9bb2-48c7-d844-ce54-3d397a48f698@redhat.com> Message-ID: <785a8250-b5b7-73c2-14d2-bfedb3af7158@redhat.com> On 2/3/19 2:55 AM, Patrick Zhang wrote: > Could you please explain this a little bit more? It looks aarch64 has a StoreLoad there, while x86 has StoreLoad|StoreStore, did you mean the StoreStore can be dropped by aarch64 because x86 TSO needs more protection here? Oh, I see what you're asking. StoreLoad|StoreStore generates the same code as StoreLoad on both Intel and AArch64, so it does not matter. I guess it should be changed in order not to confuse people. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From patrick at os.amperecomputing.com Mon Feb 4 08:17:13 2019 From: patrick at os.amperecomputing.com (Patrick Zhang) Date: Mon, 4 Feb 2019 08:17:13 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: <785a8250-b5b7-73c2-14d2-bfedb3af7158@redhat.com> References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> <396b9bb2-48c7-d844-ce54-3d397a48f698@redhat.com> <785a8250-b5b7-73c2-14d2-bfedb3af7158@redhat.com> Message-ID: I see, thanks. x86 only handles StoreLoad so StoreStore can be ignored, while aarch64 uses ISH (Any-Any) for StoreLoad barrier option which covers ISHST for StoreStore so ignorable too. In order to have self-documenting code here, I would rather keep SotreLoad|StoreStore, or simply create a new enum side by side in assembler_aarch64.hpp as StoreLoadOrStoreStore = ISH /* (ISH == ISH | ISHST) */ to hide the details. Which is better? Regards Patrick -----Original Message----- From: Andrew Haley Sent: Monday, February 4, 2019 2:26 AM To: Patrick Zhang Cc: aarch64-port-dev at openjdk.java.net; JiangNing-OS ; Lun Liu Subject: Re: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? On 2/3/19 2:55 AM, Patrick Zhang wrote: > Could you please explain this a little bit more? It looks aarch64 has a StoreLoad there, while x86 has StoreLoad|StoreStore, did you mean the StoreStore can be dropped by aarch64 because x86 TSO needs more protection here? Oh, I see what you're asking. StoreLoad|StoreStore generates the same code as StoreLoad on both Intel and AArch64, so it does not matter. I guess it should be changed in order not to confuse people. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Mon Feb 4 09:30:24 2019 From: aph at redhat.com (Andrew Haley) Date: Mon, 4 Feb 2019 09:30:24 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> <396b9bb2-48c7-d844-ce54-3d397a48f698@redhat.com> <785a8250-b5b7-73c2-14d2-bfedb3af7158@redhat.com> Message-ID: <5960e122-1aee-8bdb-187e-bda894f84644@redhat.com> On 2/4/19 8:17 AM, Patrick Zhang wrote: > x86 only handles StoreLoad so StoreStore can be ignored, while > aarch64 uses ISH (Any-Any) for StoreLoad barrier option which covers > ISHST for StoreStore so ignorable too. In order to have > self-documenting code here, I would rather keep > SotreLoad|StoreStore, or simply create a new enum side by side in > assembler_aarch64.hpp as StoreLoadOrStoreStore = ISH /* (ISH == ISH > | ISHST) */ to hide the details. Which is better? The first one. We do not need any new interfaces. :-) -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From bsrbnd at gmail.com Sun Feb 3 12:57:04 2019 From: bsrbnd at gmail.com (B. Blaser) Date: Sun, 3 Feb 2019 13:57:04 +0100 Subject: [aarch64-port-dev ] RFR(M): 8212043: Add floating-point Math.min/max intrinsics In-Reply-To: <02FCFB8477C4EF43A2AD8E0C60F3DA2BB1A579A7@FMSMSX126.amr.corp.intel.com> References: <5bf1c593-2e96-8a10-88c6-98afdd9a04f2@redhat.com> <0c7de175-17d8-f3f5-a47b-2b9b3f45af71@redhat.com> <1e7af2c4-8610-2ee9-9955-298ffb715fa7@redhat.com> <06048878-effe-7d24-bb87-b140e662aeb8@redhat.com> <7c97719b-e83a-ba40-43a3-8cec8273df1c@redhat.com> <3df16666-a10b-41bb-7439-b967e1d76735@redhat.com> <4a10fa17-197b-2da9-7890-9544a407832f@redhat.com> <02FCFB8477C4EF43A2AD8E0C60F3DA2BB1A579A7@FMSMSX126.amr.corp.intel.com> Message-ID: Hi All, On Sat, 2 Feb 2019 at 18:02, Viswanathan, Sandhya wrote: > > Hi Pengfei/Andrew, > > It will be good if you could push the test case for min/max optimization since it is your contribution and missed pushing from http://cr.openjdk.java.net/~pli/rfr/8212043/webrev.04/. > The file that got missed is: test/hotspot/jtreg/compiler/intrinsic/math/TestFpMinMaxIntrinsics.java. > > Best Regards, > Sandhya Another possibility would be to push it (which I can do if there isn't any objection) as part of JDK-8217561 once approved by a Reviewer, see [1]. Bernard [1] http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2019-February/032644.html From jini.george at oracle.com Fri Feb 1 18:16:00 2019 From: jini.george at oracle.com (Jini George) Date: Fri, 1 Feb 2019 23:46:00 +0530 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: References: Message-ID: <4de13272-0f19-7897-3f4d-f4b5b56ca73f@oracle.com> Hi Nick, Do we reach here after AARCH64CurrentFrameGuess.run() fails to get the PC ? If so, was wondering if it would make more sense to scan from the top of stack sp obtained from context.getRegisterAsAddress(AARCH64ThreadContext.SP) to the sp of the last known java frame with thread.getLastJavaSP() in AARCH64CurrentFrameGuess.run() -- otherwise was wondering if we are risking an exception by running off the top of the stack while scanning in the upward direction (towards lower addresses) for CALLEE_FRAME_SEARCH_LIMIT * addressSize from the previous Java SP (though the scan range is small). Thanks, Jini. P.S.:- BTW, I was referring to this to understand your change: (from page 15 of http://infocenter.arm.com/help/topic/com.arm.doc.ihi0055b/IHI0055B_aapcs64.pdf) Conforming code shall construct a linked list of stack-frames. Each frame shall link to the frame of its caller by means of a frame record of two 64-bit values on the stack. The frame record for the innermost frame (belonging to the most recent routine invocation) shall be pointed to by the Frame Pointer register (FP). The lowest addressed double-word shall point to the previous frame record and the highest addressed double-word shall contain the value passed in LR on entry to the current function. The end of the frame record chain is indicated by the address zero in the address for the previous frame. The location of the frame record within a stack frame is not specified. Note: There will always be a short period during construction or destruction of each frame record during which the frame pointer will point to the caller?s record. On 2/1/2019 2:52 PM, Nick Gasson (Arm Technology China) wrote: > Hi all, > > Please review this patch to fix a crash in the clhsdb "jstack -v" > command on AArch64: > > Bug: https://bugs.openjdk.java.net/browse/JDK-8209413 > Webrev: http://cr.openjdk.java.net/~ngasson/8209413/webrev.01/ > > On AArch64, if you use "jhsdb clhsdb --pid=..." to attach a debugger to > a Java process, and then run "jstack -v" while any thread is executing a > native method, you will get a NullPointerException like this: > > java.lang.NullPointerException > at > jdk.hotspot.agent/sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:83) > at > jdk.hotspot.agent/sun.jvm.hotspot.CommandProcessor$24.doit(CommandProcessor.java:1066) > > The problem is this constructor of AARCH64Frame, which is called by when > trying to construct the frame for the native method (wrapper): > > AARCH64Frame(Address raw_sp, Address raw_fp) > > It takes the last-known Java SP and FP, and tries to find the PC > following the BL instruction that jumped to the native code. At the > moment it assumes this is at SP[-1]: > > this.pc = raw_sp.getAddressAt(-1 * VM.getVM().getAddressSize()); > > I think this comes from x86 where the CALL instruction will push it > there. The fix in this patch is to scan the stack of the native (C++) > function looking for a pointer back to the frame of the native wrapper. > If we find this then the LR on entry should be saved in the stack slot > above. This fails if the native function stack frame is too big, or it's > a leaf function that didn't push FP/LR. But in this case setting this.pc > to null makes the frame object look invalid and so won't be printed, > instead of crashing. > > Sample output from the ClhsdbJstack.java jtreg test which passes now > with this patch: > > - java.lang.Thread.sleep(long) @bci=0, pc=0x0000ffffa05bb68c, > Method*=0x0000000800143410 (Compiled frame; information may be imprecise) > - jdk.test.lib.apps.LingeredApp.main(java.lang.String[]) @bci=53, > line=502, pc=0x0000ffff9892572c, Method*=0x0000ffff2e870d48 (Interpreted > frame) > > An alternative to scanning the native functions's stack might be to use > the last-known Java PC saved by set_last_Java_frame, this is off by a > few instructions but I don't think that matters. But this constructor > potentially has other users so we'd have to fix it anyway. > > Thanks, > Nick > From sandhya.viswanathan at intel.com Sat Feb 2 17:02:25 2019 From: sandhya.viswanathan at intel.com (Viswanathan, Sandhya) Date: Sat, 2 Feb 2019 17:02:25 +0000 Subject: [aarch64-port-dev ] RFR(M): 8212043: Add floating-point Math.min/max intrinsics In-Reply-To: References: <5bf1c593-2e96-8a10-88c6-98afdd9a04f2@redhat.com> <0c7de175-17d8-f3f5-a47b-2b9b3f45af71@redhat.com> <1e7af2c4-8610-2ee9-9955-298ffb715fa7@redhat.com> <06048878-effe-7d24-bb87-b140e662aeb8@redhat.com> <7c97719b-e83a-ba40-43a3-8cec8273df1c@redhat.com> <3df16666-a10b-41bb-7439-b967e1d76735@redhat.com> <4a10fa17-197b-2da9-7890-9544a407832f@redhat.com> Message-ID: <02FCFB8477C4EF43A2AD8E0C60F3DA2BB1A579A7@FMSMSX126.amr.corp.intel.com> Hi Pengfei/Andrew, It will be good if you could push the test case for min/max optimization since it is your contribution and missed pushing from http://cr.openjdk.java.net/~pli/rfr/8212043/webrev.04/. The file that got missed is: test/hotspot/jtreg/compiler/intrinsic/math/TestFpMinMaxIntrinsics.java. Best Regards, Sandhya _____________________________________________ From: Bhateja, Jatin Sent: Wednesday, January 16, 2019 1:53 AM To: Pengfei.Li at arm.com Cc: adinn at redhat.com; aph at redhat.com; hotspot-compiler-dev at openjdk.java.net; aarch64-port-dev at openjdk.java.net; nd at arm.com; Viswanathan, Sandhya ; Bhateja, Jatin Subject: RE: [aarch64-port-dev ] RFR(M): 8212043: Add floating-point Math.min/max intrinsics Hi Pengfei, Your final patch (http://cr.openjdk.java.net/~pli/rfr/8212043/webrev.04/) to support floating point scalar max/min intrinsic also included following test case which is not up streamed to jdk repository. test/hotspot/jtreg/compiler/intrinsics/math/TestFpMinMaxIntrinsics.java Can you kindly add this test case, I?m working on supporting these new intrinsics for X86 platform and will like to use the test case you created. Thanks and Regards, Jatin Bhateja From: Pengfei Li (Arm Technology China) > ---------- Forwarded message --------- Date: Wed, Dec 19, 2018 at 6:38 PM Subject: RE: [aarch64-port-dev ] RFR(M): 8212043: Add floating-point Math.min/max intrinsics To: Andrew Dinn >, Andrew Haley >, hotspot-compiler-dev at openjdk.java.net >, aarch64-port-dev at openjdk.java.net > Cc: nd > Hi > Pengfei, I am sure you will be pleased to know this has finally been pushed to > the dev repo. Thanks a lot Andrew Dinn and Andrew Haley! This could not happen without your help. And for the next step, the follow-up patch for vectorization is almost ready. I will post it in another new thread soon later. -- Thanks, Pengfei From ci_notify at linaro.org Mon Feb 4 16:25:12 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Mon, 4 Feb 2019 16:25:12 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 12 on AArch64 Message-ID: <599114685.126.1549297513235.JavaMail.jenkins@dc828b94788c> 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/jdk12/openjdk-jtreg-nightly-tests/summary/2019/034/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 5,510; fail: 4; error: 1; not run: 93 Build 1: aarch64/2019/jan/25 pass: 5,523; fail: 7; not run: 93 Build 2: aarch64/2019/jan/27 pass: 5,524; fail: 5; error: 1; not run: 93 Build 3: aarch64/2019/jan/29 pass: 5,524; fail: 5; error: 1; not run: 93 Build 4: aarch64/2019/jan/31 pass: 5,518; fail: 5; error: 1; not run: 93 Build 5: aarch64/2019/feb/03 pass: 5,517; fail: 6; error: 1; not run: 93 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 8,528; fail: 482; error: 29 Build 1: aarch64/2019/jan/25 pass: 8,522; fail: 491; error: 27 Build 2: aarch64/2019/jan/27 pass: 8,540; fail: 488; error: 12 Build 3: aarch64/2019/jan/29 pass: 8,543; fail: 483; error: 14 Build 4: aarch64/2019/jan/31 pass: 8,530; fail: 491; error: 21 Build 5: aarch64/2019/feb/03 pass: 8,523; fail: 502; error: 17 3 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 3,992 Build 1: aarch64/2019/jan/25 pass: 3,992 Build 2: aarch64/2019/jan/27 pass: 3,992 Build 3: aarch64/2019/jan/29 pass: 3,992 Build 4: aarch64/2019/jan/31 pass: 3,992 Build 5: aarch64/2019/feb/03 pass: 3,992 Previous results can be found here: http://openjdk.linaro.org/jdk12/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): 7.57x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk12/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/jdk12/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-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/022/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/027/results/ 2019-01-30 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/031/results/ 2019-02-04 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/034/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/ From ci_notify at linaro.org Mon Feb 4 16:26:41 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Mon, 4 Feb 2019 16:26:41 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <1014181591.128.1549297602518.JavaMail.jenkins@dc828b94788c> 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/034/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 792; fail: 16; error: 3 Build 1: aarch64/2019/feb/03 pass: 800; fail: 9; error: 2 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 5,778; fail: 236; error: 28 Build 1: aarch64/2019/feb/03 pass: 5,756; fail: 261; error: 25 ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 3,114; fail: 2 Build 1: aarch64/2019/feb/03 pass: 3,114; 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): 9.07x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 176.44 Server 176.44 / Server 2014-04-01 (71.00): 2.49x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-02-04 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/034/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From aph at redhat.com Mon Feb 4 17:43:21 2019 From: aph at redhat.com (Andrew Haley) Date: Mon, 4 Feb 2019 17:43:21 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: <5a9ebe53-0dea-6259-c070-6ed090f6895f@arm.com> References: <4de13272-0f19-7897-3f4d-f4b5b56ca73f@oracle.com> <5a9ebe53-0dea-6259-c070-6ed090f6895f@arm.com> Message-ID: <2f5666be-ee9c-e6bf-aa72-eb999ad6aba5@redhat.com> On 2/3/19 3:01 AM, Nick Gasson (Arm Technology China) wrote: > I think this is much better, thanks. But we still have the problem > that the two-argument AARCH64Frame constructor is wrong: I don't > think it's ever correct to assume the PC is at SP[-1]. Really? We push it there when we make runtime calls from C2 and that's also where we put it in all compiler-generated code. I'll grant you that's not where native-compiler-generated code puts it, so we can't guarantee it'll be there. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Mon Feb 4 18:25:34 2019 From: aph at redhat.com (Andrew Haley) Date: Mon, 4 Feb 2019 18:25:34 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: References: Message-ID: On 2/1/19 9:22 AM, Nick Gasson (Arm Technology China) wrote: > It takes the last-known Java SP and FP, and tries to find the PC > following the BL instruction that jumped to the native code. At the > moment it assumes this is at SP[-1]: That's where it should be. Please tell me which code it is that jumps to the native code. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From Nick.Gasson at arm.com Mon Feb 4 18:51:52 2019 From: Nick.Gasson at arm.com (Nick Gasson (Arm Technology China)) Date: Mon, 4 Feb 2019 18:51:52 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: References: , Message-ID: Hi Andrew > Please tell me which code it is that jumps to the native code. SharedRuntime::generate_native_wrapper. The SP here is saved in the thread state by set_last_Java_frame. Nick ________________________________ From: Andrew Haley Sent: 05 February 2019 02:25:34 To: Nick Gasson (Arm Technology China); serviceability-dev at openjdk.java.net Cc: nd; aarch64-port-dev at openjdk.java.net Subject: Re: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command On 2/1/19 9:22 AM, Nick Gasson (Arm Technology China) wrote: > It takes the last-known Java SP and FP, and tries to find the PC > following the BL instruction that jumped to the native code. At the > moment it assumes this is at SP[-1]: That's where it should be. Please tell me which code it is that jumps to the native code. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Tue Feb 5 07:45:43 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Tue, 5 Feb 2019 07:45:43 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <685835951.179.1549352743706.JavaMail.jenkins@dc828b94788c> 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/035/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/2018/dec/26 pass: 5,555; fail: 20; error: 1; not run: 93 Build 1: aarch64/2018/dec/28 pass: 5,554; fail: 21; error: 1; not run: 93 Build 2: aarch64/2018/dec/31 pass: 5,556; fail: 19; error: 1; not run: 93 Build 3: aarch64/2019/jan/02 pass: 5,554; fail: 21; error: 1; not run: 93 Build 4: aarch64/2019/jan/04 pass: 5,562; fail: 19; error: 2; not run: 93 Build 5: aarch64/2019/jan/07 pass: 5,563; fail: 19; error: 1; not run: 93 Build 6: aarch64/2019/jan/09 pass: 5,564; fail: 20; error: 1; not run: 93 Build 7: aarch64/2019/jan/11 pass: 5,504; fail: 5; error: 1; not run: 93 Build 8: aarch64/2019/jan/16 pass: 5,511; fail: 6; error: 2; not run: 93 Build 9: aarch64/2019/jan/21 pass: 5,514; fail: 8; error: 1; not run: 93 Build 10: aarch64/2019/jan/24 pass: 5,520; fail: 5; error: 1; not run: 93 Build 11: aarch64/2019/jan/25 pass: 5,533; fail: 6; error: 1; not run: 93 Build 12: aarch64/2019/jan/28 pass: 5,533; fail: 6; error: 1; not run: 93 Build 13: aarch64/2019/jan/30 pass: 5,527; fail: 5; error: 2; not run: 93 Build 14: aarch64/2019/feb/04 pass: 5,527; fail: 7; error: 2; not run: 93 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/dec/26 pass: 8,592; fail: 665; error: 30 Build 1: aarch64/2018/dec/28 pass: 8,576; fail: 684; error: 27 Build 2: aarch64/2018/dec/31 pass: 8,590; fail: 670; error: 27 Build 3: aarch64/2019/jan/02 pass: 8,574; fail: 689; error: 24 Build 4: aarch64/2019/jan/04 pass: 8,591; fail: 677; error: 19 Build 5: aarch64/2019/jan/07 pass: 8,534; fail: 490; error: 16 Build 6: aarch64/2019/jan/09 pass: 8,545; fail: 483; error: 15 Build 7: aarch64/2019/jan/11 pass: 8,501; fail: 518; error: 25 Build 8: aarch64/2019/jan/16 pass: 8,553; fail: 480; error: 15 Build 9: aarch64/2019/jan/21 pass: 8,521; fail: 511; error: 20 Build 10: aarch64/2019/jan/24 pass: 8,533; fail: 503; error: 18 Build 11: aarch64/2019/jan/25 pass: 8,538; fail: 500; error: 20 Build 12: aarch64/2019/jan/28 pass: 8,543; fail: 496; error: 20 Build 13: aarch64/2019/jan/30 pass: 8,541; fail: 503; error: 19 Build 14: aarch64/2019/feb/04 pass: 8,539; fail: 506; error: 18 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/dec/26 pass: 3,996; fail: 4 Build 1: aarch64/2018/dec/28 pass: 3,996; fail: 4 Build 2: aarch64/2018/dec/31 pass: 3,996; fail: 4 Build 3: aarch64/2019/jan/02 pass: 3,996; fail: 4 Build 4: aarch64/2019/jan/04 pass: 3,996; fail: 4 Build 5: aarch64/2019/jan/07 pass: 3,993 Build 6: aarch64/2019/jan/09 pass: 3,993 Build 7: aarch64/2019/jan/11 pass: 3,991 Build 8: aarch64/2019/jan/16 pass: 3,993 Build 9: aarch64/2019/jan/21 pass: 3,993; fail: 1 Build 10: aarch64/2019/jan/24 pass: 3,993; fail: 1 Build 11: aarch64/2019/jan/25 pass: 3,993; fail: 1 Build 12: aarch64/2019/jan/28 pass: 3,994; fail: 1 Build 13: aarch64/2019/jan/30 pass: 3,994; fail: 1 Build 14: aarch64/2019/feb/04 pass: 3,994; fail: 1 ------------------------------------------------------------------------------- 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.88x Relative performance: Server critical-jOPS (nc): 9.03x 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. 2018-12-27 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/360/results/ 2018-12-29 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/362/results/ 2019-01-01 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/365/results/ 2019-01-03 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/002/results/ 2019-01-05 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/004/results/ 2019-01-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/007/results/ 2019-01-10 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/009/results/ 2019-01-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/011/results/ 2019-01-16 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/016/results/ 2019-01-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/021/results/ 2019-01-24 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/024/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/028/results/ 2019-01-31 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/030/results/ 2019-02-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/035/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From tobias.hartmann at oracle.com Tue Feb 5 14:45:27 2019 From: tobias.hartmann at oracle.com (Tobias Hartmann) Date: Tue, 5 Feb 2019 15:45:27 +0100 Subject: [aarch64-port-dev ] RFR(L) Valhalla support for AArch64 In-Reply-To: <7d2bd953-8df2-1071-4e64-5c03c6c894eb@oracle.com> References: <6a452e66-3fd9-dc98-fa1f-dd4b684b651a@samersoff.net> <7d2bd953-8df2-1071-4e64-5c03c6c894eb@oracle.com> Message-ID: <904a890b-0e13-564c-b695-8b2744212342@oracle.com> Hi Dmitry, On 29.01.19 09:40, Tobias Hartmann wrote: > FYI, I'm working on JDK-8215559 which will introduce new entry points and change all the related > code code a lot (refactoring/cleanups/bug fixes). My patch is not yet stable but I expect it to be > ready by the end of this week. It might be worth holding off on your side until this is in. I've just sent it out for review: http://mail.openjdk.java.net/pipermail/valhalla-dev/2019-February/005421.html Best regards, Tobias From aph at redhat.com Tue Feb 5 17:14:52 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 5 Feb 2019 17:14:52 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: References: Message-ID: On 2/1/19 9:22 AM, Nick Gasson (Arm Technology China) wrote: > On AArch64, if you use "jhsdb clhsdb --pid=..." to attach a debugger to > a Java process, and then run "jstack -v" while any thread is executing a > native method, you will get a NullPointerException like this: This does not happen for me. I have a test case which runs a native method; the native method does not return. I then run jstack -v and get a clean stack trace, regardless of whether it's interpreted or compiled: "main" #1 prio=5 tid=0x0000ffff7001a000 nid=0x596c runnable [0x0000ffff7624e000] java.lang.Thread.State: RUNNABLE JavaThread state: _thread_in_native - Spinner.main(java.lang.String[]) @bci=0, line=9, pc=0x0000ffff6d6954d8, Method*=0x0000ffff2321e380 (Compiled frame; information may be imprecise) Locked ownable synchronizers: - None I tries various combinations of Xcomp and tiered compilation. What did you do? -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Tue Feb 5 17:26:41 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 5 Feb 2019 17:26:41 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: References: Message-ID: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> On 2/1/19 9:22 AM, Nick Gasson (Arm Technology China) wrote: > On AArch64, if you use "jhsdb clhsdb --pid=..." to attach a debugger to > a Java process, and then run "jstack -v" while any thread is executing a > native method, you will get a NullPointerException like this: This does not happen for me. I have a test case which runs a native method; the native method does not return. I then run jstack -v and get a clean stack trace, regardless of whether it's interpreted or compiled: "main" #1 prio=5 tid=0x0000ffff7001a000 nid=0x596c runnable [0x0000ffff7624e000] java.lang.Thread.State: RUNNABLE JavaThread state: _thread_in_native - Spinner.main(java.lang.String[]) @bci=0, line=9, pc=0x0000ffff6d6954d8, Method*=0x0000ffff2321e380 (Compiled frame; information may be imprecise) Locked ownable synchronizers: - None I tried various combinations of Xcomp and tiered compilation, release and debug builds. What did you do? -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From Nick.Gasson at arm.com Tue Feb 5 17:55:10 2019 From: Nick.Gasson at arm.com (Nick Gasson (Arm Technology China)) Date: Tue, 5 Feb 2019 17:55:10 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> References: , <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> Message-ID: Hi Andrew, I followed the same steps as the serviceabilty/sa/ClhsdbJstack.java test. You can see this failing in Linaro's results here: http://openjdk.linaro.org/jdkX/openjdk-jtreg-nightly-tests/builds/release/2019/028/JTwork-hotspot/serviceability/sa/ClhsdbJstack.jtr The stack trace you sent below is incomplete, it's missing the frame for Spinner.run (i.e. the AARCH64Frame object corresponding to the native wrapper frame). Did you try on x86 or with the patch I posted? I'm not able to test at the moment but I think you will get one exra frame in the output. I don't know why you don't get the NPE, I guess it depends on what's in that stack slot. Nick ________________________________ From: Andrew Haley Sent: 06 February 2019 01:26:41 To: Nick Gasson (Arm Technology China); serviceability-dev at openjdk.java.net Cc: nd; aarch64-port-dev at openjdk.java.net Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command On 2/1/19 9:22 AM, Nick Gasson (Arm Technology China) wrote: > On AArch64, if you use "jhsdb clhsdb --pid=..." to attach a debugger to > a Java process, and then run "jstack -v" while any thread is executing a > native method, you will get a NullPointerException like this: This does not happen for me. I have a test case which runs a native method; the native method does not return. I then run jstack -v and get a clean stack trace, regardless of whether it's interpreted or compiled: "main" #1 prio=5 tid=0x0000ffff7001a000 nid=0x596c runnable [0x0000ffff7624e000] java.lang.Thread.State: RUNNABLE JavaThread state: _thread_in_native - Spinner.main(java.lang.String[]) @bci=0, line=9, pc=0x0000ffff6d6954d8, Method*=0x0000ffff2321e380 (Compiled frame; information may be imprecise) Locked ownable synchronizers: - None I tried various combinations of Xcomp and tiered compilation, release and debug builds. What did you do? -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Tue Feb 5 17:57:07 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 5 Feb 2019 17:57:07 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: References: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> Message-ID: <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com> On 2/5/19 5:55 PM, Nick Gasson (Arm Technology China) wrote: > The stack trace you sent below is incomplete, it's missing the frame for Spinner.run (i.e. the AARCH64Frame object corresponding to the native wrapper frame). Did you try on x86 or with the patch I posted? I'm not able to test at the moment but I think you will get one exra frame in the output. I don't know why you don't get the NPE, I guess it depends on what's in that stack slot. Never mind, found it. A more complex test is needed. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Wed Feb 6 08:02:39 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Wed, 6 Feb 2019 08:02:39 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 12 on AArch64 Message-ID: <1499713699.310.1549440160488.JavaMail.jenkins@dc828b94788c> 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/jdk12/openjdk-jtreg-nightly-tests/summary/2019/036/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 5,510; fail: 4; error: 1; not run: 93 Build 1: aarch64/2019/jan/25 pass: 5,523; fail: 7; not run: 93 Build 2: aarch64/2019/jan/27 pass: 5,524; fail: 5; error: 1; not run: 93 Build 3: aarch64/2019/jan/29 pass: 5,524; fail: 5; error: 1; not run: 93 Build 4: aarch64/2019/jan/31 pass: 5,518; fail: 5; error: 1; not run: 93 Build 5: aarch64/2019/feb/03 pass: 5,517; fail: 6; error: 1; not run: 93 Build 6: aarch64/2019/feb/05 pass: 5,517; fail: 6; error: 1; not run: 93 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 8,528; fail: 482; error: 29 Build 1: aarch64/2019/jan/25 pass: 8,522; fail: 491; error: 27 Build 2: aarch64/2019/jan/27 pass: 8,540; fail: 488; error: 12 Build 3: aarch64/2019/jan/29 pass: 8,543; fail: 483; error: 14 Build 4: aarch64/2019/jan/31 pass: 8,530; fail: 491; error: 21 Build 5: aarch64/2019/feb/03 pass: 8,523; fail: 502; error: 17 Build 6: aarch64/2019/feb/05 pass: 8,492; fail: 520; error: 30 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 3,992 Build 1: aarch64/2019/jan/25 pass: 3,992 Build 2: aarch64/2019/jan/27 pass: 3,992 Build 3: aarch64/2019/jan/29 pass: 3,992 Build 4: aarch64/2019/jan/31 pass: 3,992 Build 5: aarch64/2019/feb/03 pass: 3,992 Build 6: aarch64/2019/feb/05 pass: 3,992 Previous results can be found here: http://openjdk.linaro.org/jdk12/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.65x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk12/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/jdk12/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-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/022/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/027/results/ 2019-01-30 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/031/results/ 2019-02-04 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/034/results/ 2019-02-06 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/036/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/ From aph at redhat.com Wed Feb 6 10:00:16 2019 From: aph at redhat.com (Andrew Haley) Date: Wed, 6 Feb 2019 10:00:16 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com> References: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com> Message-ID: On 2/5/19 5:57 PM, Andrew Haley wrote: > On 2/5/19 5:55 PM, Nick Gasson (Arm Technology China) wrote: >> The stack trace you sent below is incomplete, it's missing the frame for Spinner.run (i.e. the AARCH64Frame object corresponding to the native wrapper frame). Did you try on x86 or with the patch I posted? I'm not able to test at the moment but I think you will get one exra frame in the output. I don't know why you don't get the NPE, I guess it depends on what's in that stack slot. > > Never mind, found it. A more complex test is needed. Here's the test that reveals the problem: it seems that you need an entry frame which calls compiled Java code. [aph at merino ~]$ cat Spinner.c #include #include /* * Class: Spinner * Method: run * Signature: ()V */ JNIEXPORT void JNICALL Java_Spinner_run(JNIEnv *env, jclass cls) { jmethodID mid = (*env)->GetStaticMethodID(env, cls, "test", "()V"); (*env)->CallStaticVoidMethod(env, cls, mid); // printf("Spinning...\n"); // for(;;); } [aph at merino ~]$ cat Spinner.java public class Spinner { static native void run(); static { System.loadLibrary("Spinner"); } static volatile int nn; public static void test() { System.out.println("Spinning"); for(int i = 1; i !=0; i = (i + 1) | 1) nn = (int)Math.log(i); } public static void main(String[] args) { run(); } } -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From adinn at redhat.com Wed Feb 6 10:47:09 2019 From: adinn at redhat.com (Andrew Dinn) Date: Wed, 6 Feb 2019 10:47:09 +0000 Subject: [aarch64-port-dev ] RFR(M): 8212043: Add floating-point Math.min/max intrinsics In-Reply-To: References: <1e7af2c4-8610-2ee9-9955-298ffb715fa7@redhat.com> <06048878-effe-7d24-bb87-b140e662aeb8@redhat.com> <7c97719b-e83a-ba40-43a3-8cec8273df1c@redhat.com> <3df16666-a10b-41bb-7439-b967e1d76735@redhat.com> <4a10fa17-197b-2da9-7890-9544a407832f@redhat.com> <02FCFB8477C4EF43A2AD8E0C60F3DA2BB1A579A7@FMSMSX126.amr.corp.intel.com> Message-ID: <6332babc-f2c9-1478-42f4-2e2e0f8ae6a7@redhat.com> Hi Bernard, On 03/02/2019 12:57, B. Blaser wrote: > On Sat, 2 Feb 2019 at 18:02, Viswanathan, Sandhya > wrote: >> >> It will be good if you could push the test case for min/max >> optimization since it is your contribution and missed pushing from >> http://cr.openjdk.java.net/~pli/rfr/8212043/webrev.04/. The file >> that got missed is: >> test/hotspot/jtreg/compiler/intrinsic/math/TestFpMinMaxIntrinsics.java. >> >> > > Another possibility would be to push it (which I can do if there > isn't any objection) as part of JDK-8217561 once approved by a > Reviewer, see [1]. > > [1]> http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2019-February/032644.html I prefer to create a separate issue to cover addition this test so that it does not get wrapped up with the review of the Intel implementation which is really a separate task. I have created JDK-8218550 for this purpose. 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 Wed Feb 6 10:54:38 2019 From: Nick.Gasson at arm.com (Nick Gasson (Arm Technology China)) Date: Wed, 6 Feb 2019 10:54:38 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: References: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com>, Message-ID: Hi Andrew > Here's the test that reveals the problem: it seems that you need an entry frame which calls compiled Java code. This seems slightly different to the original problem, although maybe related. Because here the top-most frame is a compiled Java frame we'll take the vm.isJavaPCDbg and !vm.isClientCompiler branches of AARCH64CurrentFrameGuess::run which as far as I can tell always gets the PC from the thread context. The original crash I was looking at happened when the top frame was native (else branch on line 183) where the PC is set to null which causes the two-argument AARCH64Frame constructor to be used. Unfortunately I'm on holiday until next Thursday so can't test anything. Did you try Thread.sleep? That's what LingeredApp that the jtreg tests is trying to get a stack trace of calls. Thanks, Nick ________________________________ From: Andrew Haley Sent: 06 February 2019 18:00:16 To: Nick Gasson (Arm Technology China); serviceability-dev at openjdk.java.net Cc: nd; aarch64-port-dev at openjdk.java.net Subject: Re: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command On 2/5/19 5:57 PM, Andrew Haley wrote: > On 2/5/19 5:55 PM, Nick Gasson (Arm Technology China) wrote: >> The stack trace you sent below is incomplete, it's missing the frame for Spinner.run (i.e. the AARCH64Frame object corresponding to the native wrapper frame). Did you try on x86 or with the patch I posted? I'm not able to test at the moment but I think you will get one exra frame in the output. I don't know why you don't get the NPE, I guess it depends on what's in that stack slot. > > Never mind, found it. A more complex test is needed. Here's the test that reveals the problem: it seems that you need an entry frame which calls compiled Java code. [aph at merino ~]$ cat Spinner.c #include #include /* * Class: Spinner * Method: run * Signature: ()V */ JNIEXPORT void JNICALL Java_Spinner_run(JNIEnv *env, jclass cls) { jmethodID mid = (*env)->GetStaticMethodID(env, cls, "test", "()V"); (*env)->CallStaticVoidMethod(env, cls, mid); // printf("Spinning...\n"); // for(;;); } [aph at merino ~]$ cat Spinner.java public class Spinner { static native void run(); static { System.loadLibrary("Spinner"); } static volatile int nn; public static void test() { System.out.println("Spinning"); for(int i = 1; i !=0; i = (i + 1) | 1) nn = (int)Math.log(i); } public static void main(String[] args) { run(); } } -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From adinn at redhat.com Wed Feb 6 15:53:43 2019 From: adinn at redhat.com (Andrew Dinn) Date: Wed, 6 Feb 2019 15:53:43 +0000 Subject: [aarch64-port-dev ] RFR: (T) AArch64: 8218550: Add test omitted from JDK-8212043 Message-ID: <2a7188f7-c88e-bb87-cbb7-2ccea7801de3@redhat.com> Please review this trivial patch which includes a test omitted from the check-in for JDK-8212043. The test was already reviewed by Andrew Haley and me as part of the original review. JIRA: https://bugs.openjdk.java.net/browse/JDK-8218550 Webrev: http://cr.openjdk.java.net/~adinn/8218550/ Testing: I reran the test with an image built from the latest tree and it passes. 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 -------------- next part -------------- A non-text attachment was scrubbed... Name: 8218550.patch Type: text/x-patch Size: 6014 bytes Desc: not available URL: From shade at redhat.com Wed Feb 6 15:58:11 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Wed, 6 Feb 2019 16:58:11 +0100 Subject: [aarch64-port-dev ] RFR: (T) AArch64: 8218550: Add test omitted from JDK-8212043 In-Reply-To: <2a7188f7-c88e-bb87-cbb7-2ccea7801de3@redhat.com> References: <2a7188f7-c88e-bb87-cbb7-2ccea7801de3@redhat.com> Message-ID: <365531d4-55b2-1ae0-784b-71e636bc1fa8@redhat.com> On 2/6/19 4:53 PM, Andrew Dinn wrote: > Please review this trivial patch which includes a test omitted from the > check-in for JDK-8212043. The test was already reviewed by Andrew Haley > and me as part of the original review. > > JIRA: https://bugs.openjdk.java.net/browse/JDK-8218550 > Webrev: http://cr.openjdk.java.net/~adinn/8218550/ Looks good and trivial. I added some metadata to the issue itself (links, assignees, etc.) -Aleksey From adinn at redhat.com Wed Feb 6 16:22:51 2019 From: adinn at redhat.com (Andrew Dinn) Date: Wed, 6 Feb 2019 16:22:51 +0000 Subject: [aarch64-port-dev ] RFR: (T) AArch64: 8218550: Add test omitted from JDK-8212043 In-Reply-To: <365531d4-55b2-1ae0-784b-71e636bc1fa8@redhat.com> References: <2a7188f7-c88e-bb87-cbb7-2ccea7801de3@redhat.com> <365531d4-55b2-1ae0-784b-71e636bc1fa8@redhat.com> Message-ID: <5b00deab-10fb-a5be-52b7-192926f17671@redhat.com> On 06/02/2019 15:58, Aleksey Shipilev wrote: > On 2/6/19 4:53 PM, Andrew Dinn wrote: >> Please review this trivial patch which includes a test omitted from the >> check-in for JDK-8212043. The test was already reviewed by Andrew Haley >> and me as part of the original review. >> >> JIRA: https://bugs.openjdk.java.net/browse/JDK-8218550 >> Webrev: http://cr.openjdk.java.net/~adinn/8218550/ > > Looks good and trivial. I added some metadata to the issue itself (links, assignees, etc.) Ok, thanks. I will push it following this single review as it is trivial and AArch64 only. 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 Feb 6 18:42:29 2019 From: aph at redhat.com (Andrew Haley) Date: Wed, 6 Feb 2019 18:42:29 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: References: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com> Message-ID: On 2/6/19 10:54 AM, Nick Gasson (Arm Technology China) wrote: > Hi Andrew > >> Here's the test that reveals the problem: it seems that you need an entry frame which calls compiled Java code. > > This seems slightly different to the original problem, although > maybe related. Because here the top-most frame is a compiled Java > frame we'll take the vm.isJavaPCDbg and !vm.isClientCompiler > branches of AARCH64CurrentFrameGuess::run which as far as I can tell > always gets the PC from the thread context. The original crash I was > looking at happened when the top frame was native (else branch on > line 183) where the PC is set to null which causes the two-argument > AARCH64Frame constructor to be used. OK. > Unfortunately I'm on holiday until next Thursday so can't test > anything. Did you try Thread.sleep? That's what LingeredApp that the > jtreg tests is trying to get a stack trace of calls. Well, that was fun. When generally assume that we can find a saved PC in a fixed place in the frame, and this is always the word above the FP. However, when we're in JNI native code, as you've noticed the C[++] compiler isn't helpful enough to lave the caller PC in a well-known place. When the frame is created by our AArch64 assembly- langage code we'll be fine because we always do the right thing. The problem is that when we save the Java frame state in the Thread, we're doing it for the sake of the runtime, not for debuggers, so we don't always save all the information that a debugger might need. This patch should work for compiled native methods, but I'm not at all sure about all of the other places where we call out from runtime stubs to the VM. We perhaps check that the PC returned by raw_sp.getAddressAt(-1 * VM.getVM().getAddressSize()) is in the code cache before we use it. Anyway, try this: it should fix your immediate bug. diff -r 3954d70e1c50 src/hotspot/cpu/aarch64/sharedRuntime_aarch64.cpp --- a/src/hotspot/cpu/aarch64/sharedRuntime_aarch64.cpp Wed Feb 06 08:31:27 2019 +0100 +++ b/src/hotspot/cpu/aarch64/sharedRuntime_aarch64.cpp Wed Feb 06 18:22:09 2019 +0000 @@ -1916,10 +1916,20 @@ default: ShouldNotReachHere(); } + + // Leave a breadcrumb for + // sun.jvm.hotspot.runtime.aarch64.AARCH64Frame(sp, fp) + Label retaddr; + __ adr(rscratch2, retaddr); + __ stp(zr, rscratch2, Address(__ pre(sp, -2 * wordSize))); + rt_call(masm, native_func, int_args + 2, // AArch64 passes up to 8 args in int registers float_args, // and up to 8 float args return_type); + + __ bind(retaddr); + __ add(sp, sp, 2 * wordSize); } // Unpack native results. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Thu Feb 7 01:48:15 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Thu, 7 Feb 2019 01:48:15 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <194309732.405.1549504095868.JavaMail.jenkins@dc828b94788c> 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/037/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/2018/dec/28 pass: 5,554; fail: 21; error: 1; not run: 93 Build 1: aarch64/2018/dec/31 pass: 5,556; fail: 19; error: 1; not run: 93 Build 2: aarch64/2019/jan/02 pass: 5,554; fail: 21; error: 1; not run: 93 Build 3: aarch64/2019/jan/04 pass: 5,562; fail: 19; error: 2; not run: 93 Build 4: aarch64/2019/jan/07 pass: 5,563; fail: 19; error: 1; not run: 93 Build 5: aarch64/2019/jan/09 pass: 5,564; fail: 20; error: 1; not run: 93 Build 6: aarch64/2019/jan/11 pass: 5,504; fail: 5; error: 1; not run: 93 Build 7: aarch64/2019/jan/16 pass: 5,511; fail: 6; error: 2; not run: 93 Build 8: aarch64/2019/jan/21 pass: 5,514; fail: 8; error: 1; not run: 93 Build 9: aarch64/2019/jan/24 pass: 5,520; fail: 5; error: 1; not run: 93 Build 10: aarch64/2019/jan/25 pass: 5,533; fail: 6; error: 1; not run: 93 Build 11: aarch64/2019/jan/28 pass: 5,533; fail: 6; error: 1; not run: 93 Build 12: aarch64/2019/jan/30 pass: 5,527; fail: 5; error: 2; not run: 93 Build 13: aarch64/2019/feb/04 pass: 5,527; fail: 7; error: 2; not run: 93 Build 14: aarch64/2019/feb/06 pass: 5,532; fail: 4; error: 1; not run: 93 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/dec/28 pass: 8,576; fail: 684; error: 27 Build 1: aarch64/2018/dec/31 pass: 8,590; fail: 670; error: 27 Build 2: aarch64/2019/jan/02 pass: 8,574; fail: 689; error: 24 Build 3: aarch64/2019/jan/04 pass: 8,591; fail: 677; error: 19 Build 4: aarch64/2019/jan/07 pass: 8,534; fail: 490; error: 16 Build 5: aarch64/2019/jan/09 pass: 8,545; fail: 483; error: 15 Build 6: aarch64/2019/jan/11 pass: 8,501; fail: 518; error: 25 Build 7: aarch64/2019/jan/16 pass: 8,553; fail: 480; error: 15 Build 8: aarch64/2019/jan/21 pass: 8,521; fail: 511; error: 20 Build 9: aarch64/2019/jan/24 pass: 8,533; fail: 503; error: 18 Build 10: aarch64/2019/jan/25 pass: 8,538; fail: 500; error: 20 Build 11: aarch64/2019/jan/28 pass: 8,543; fail: 496; error: 20 Build 12: aarch64/2019/jan/30 pass: 8,541; fail: 503; error: 19 Build 13: aarch64/2019/feb/04 pass: 8,539; fail: 506; error: 18 Build 14: aarch64/2019/feb/06 pass: 8,537; fail: 499; error: 27 5 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/dec/28 pass: 3,996; fail: 4 Build 1: aarch64/2018/dec/31 pass: 3,996; fail: 4 Build 2: aarch64/2019/jan/02 pass: 3,996; fail: 4 Build 3: aarch64/2019/jan/04 pass: 3,996; fail: 4 Build 4: aarch64/2019/jan/07 pass: 3,993 Build 5: aarch64/2019/jan/09 pass: 3,993 Build 6: aarch64/2019/jan/11 pass: 3,991 Build 7: aarch64/2019/jan/16 pass: 3,993 Build 8: aarch64/2019/jan/21 pass: 3,993; fail: 1 Build 9: aarch64/2019/jan/24 pass: 3,993; fail: 1 Build 10: aarch64/2019/jan/25 pass: 3,993; fail: 1 Build 11: aarch64/2019/jan/28 pass: 3,994; fail: 1 Build 12: aarch64/2019/jan/30 pass: 3,994; fail: 1 Build 13: aarch64/2019/feb/04 pass: 3,994; fail: 1 Build 14: aarch64/2019/feb/06 pass: 3,994; fail: 1 ------------------------------------------------------------------------------- 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.86x Relative performance: Server critical-jOPS (nc): 9.11x 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. 2018-12-29 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/362/results/ 2019-01-01 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2018/365/results/ 2019-01-03 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/002/results/ 2019-01-05 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/004/results/ 2019-01-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/007/results/ 2019-01-10 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/009/results/ 2019-01-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/011/results/ 2019-01-16 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/016/results/ 2019-01-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/021/results/ 2019-01-24 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/024/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/028/results/ 2019-01-31 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/030/results/ 2019-02-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/035/results/ 2019-02-07 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/037/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From tobias.hartmann at oracle.com Thu Feb 7 09:40:49 2019 From: tobias.hartmann at oracle.com (Tobias Hartmann) Date: Thu, 7 Feb 2019 10:40:49 +0100 Subject: [aarch64-port-dev ] RFR(L) Valhalla support for AArch64 In-Reply-To: <904a890b-0e13-564c-b695-8b2744212342@oracle.com> References: <6a452e66-3fd9-dc98-fa1f-dd4b684b651a@samersoff.net> <7d2bd953-8df2-1071-4e64-5c03c6c894eb@oracle.com> <904a890b-0e13-564c-b695-8b2744212342@oracle.com> Message-ID: <38e51140-cffd-7f72-69a2-aa77645cfd28@oracle.com> Hi Dmitry, just noticed that you probably want to change the "@requires os.simpleArch == "x64"" statements that we currently use for the value type tests such that these are also executed on AARCH64. Best regards, Tobias On 05.02.19 15:45, Tobias Hartmann wrote: > Hi Dmitry, > > On 29.01.19 09:40, Tobias Hartmann wrote: >> FYI, I'm working on JDK-8215559 which will introduce new entry points and change all the related >> code code a lot (refactoring/cleanups/bug fixes). My patch is not yet stable but I expect it to be >> ready by the end of this week. It might be worth holding off on your side until this is in. > > I've just sent it out for review: > http://mail.openjdk.java.net/pipermail/valhalla-dev/2019-February/005421.html > > Best regards, > Tobias > From aph at redhat.com Thu Feb 7 13:03:29 2019 From: aph at redhat.com (Andrew Haley) Date: Thu, 7 Feb 2019 13:03:29 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: References: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com> Message-ID: <1fd9aa7f-c5f5-80ef-dd47-73756a318d31@redhat.com> On 2/6/19 6:42 PM, Andrew Haley wrote: > On 2/6/19 10:54 AM, Nick Gasson (Arm Technology China) wrote: >> Hi Andrew >> >>> Here's the test that reveals the problem: it seems that you need an entry frame which calls compiled Java code. >> >> This seems slightly different to the original problem, although >> maybe related. Because here the top-most frame is a compiled Java >> frame we'll take the vm.isJavaPCDbg and !vm.isClientCompiler >> branches of AARCH64CurrentFrameGuess::run which as far as I can tell >> always gets the PC from the thread context. The original crash I was >> looking at happened when the top frame was native (else branch on >> line 183) where the PC is set to null which causes the two-argument >> AARCH64Frame constructor to be used. > > OK. > >> Unfortunately I'm on holiday until next Thursday so can't test >> anything. Did you try Thread.sleep? That's what LingeredApp that the >> jtreg tests is trying to get a stack trace of calls. > > Well, that was fun. When generally assume that we can find a saved PC > in a fixed place in the frame, and this is always the word above the > FP. However, when we're in JNI native code, as you've noticed the > C[++] compiler isn't helpful enough to lave the caller PC in a > well-known place. When the frame is created by our AArch64 assembly- > langage code we'll be fine because we always do the right thing. > > The problem is that when we save the Java frame state in the Thread, > we're doing it for the sake of the runtime, not for debuggers, so we > don't always save all the information that a debugger might need. > > This patch should work for compiled native methods, but I'm not at all > sure about all of the other places where we call out from runtime > stubs to the VM. We perhaps check that the PC returned by > raw_sp.getAddressAt(-1 * VM.getVM().getAddressSize()) is in the code > cache before we use it. > > Anyway, try this: it should fix your immediate bug. I had a much better idea. We usually save the PC in the frame anchor, so we should use it if we can. Add a little sanity checking, and we should be good to go, and we won't need to grovel about in the stack. I looked in all the places where we save information in the frame anchor, and we almost always set the PC appropriately. I tried this patch with a few basic smoke tests, and it seems to be considerably better than what we have right now. The only place it fails is when we're executing some C++-compiled code which is called directly from the interpreter or from compiled code. We could apply some magic in those cases, but it would incur some overhead and I'm not sure it's worthwhile. Please try this instead and let me know how you get on. Thanks. diff -r 3954d70e1c50 src/jdk.hotspot.agent/share/classes/sun/jvm/hotspot/runtime/aarch64/AARCH64CurrentFrameGuess.java --- a/src/jdk.hotspot.agent/share/classes/sun/jvm/hotspot/runtime/aarch64/AARCH64CurrentFrameGuess.java Wed Feb 06 08:31:27 2019 +0100 +++ b/src/jdk.hotspot.agent/share/classes/sun/jvm/hotspot/runtime/aarch64/AARCH64CurrentFrameGuess.java Thu Feb 07 12:45:29 2019 +0000 @@ -223,8 +223,13 @@ } } - setValues(sp, fp, null); - + // We found a PC in the frame anchor. Check that it's plausible, and + // if it is, use it. + if (vm.isJavaPCDbg(pc)) { + setValues(sp, fp, pc); + } else { + setValues(sp, fp, null); + } return true; } } -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From Nick.Gasson at arm.com Thu Feb 7 14:36:05 2019 From: Nick.Gasson at arm.com (Nick Gasson (Arm Technology China)) Date: Thu, 7 Feb 2019 14:36:05 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: <1fd9aa7f-c5f5-80ef-dd47-73756a318d31@redhat.com> References: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com> , <1fd9aa7f-c5f5-80ef-dd47-73756a318d31@redhat.com> Message-ID: Hi Andrew, Yeah I tried this method too (see the end of my first email). It works fine except the PC is off by a few instructions. That can be fixed quite easily though if required, and it always points into the right method. I ended up doing the stack scanning thing because as far as I can tell that constructor is only used when we need to find the return PC from a native frame (I might have been wrong about this), so I couldn't see how it would ever get the right value. If we check vm.isJavaPCDbg() before we use the SP[-1] value that will make the remaining callers a bit safer (and set this.pc to null otherwise). Nick ________________________________ From: Andrew Haley Sent: 07 February 2019 21:03:29 To: Nick Gasson (Arm Technology China); serviceability-dev at openjdk.java.net Cc: nd; aarch64-port-dev at openjdk.java.net Subject: Re: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command On 2/6/19 6:42 PM, Andrew Haley wrote: > On 2/6/19 10:54 AM, Nick Gasson (Arm Technology China) wrote: >> Hi Andrew >> >>> Here's the test that reveals the problem: it seems that you need an entry frame which calls compiled Java code. >> >> This seems slightly different to the original problem, although >> maybe related. Because here the top-most frame is a compiled Java >> frame we'll take the vm.isJavaPCDbg and !vm.isClientCompiler >> branches of AARCH64CurrentFrameGuess::run which as far as I can tell >> always gets the PC from the thread context. The original crash I was >> looking at happened when the top frame was native (else branch on >> line 183) where the PC is set to null which causes the two-argument >> AARCH64Frame constructor to be used. > > OK. > >> Unfortunately I'm on holiday until next Thursday so can't test >> anything. Did you try Thread.sleep? That's what LingeredApp that the >> jtreg tests is trying to get a stack trace of calls. > > Well, that was fun. When generally assume that we can find a saved PC > in a fixed place in the frame, and this is always the word above the > FP. However, when we're in JNI native code, as you've noticed the > C[++] compiler isn't helpful enough to lave the caller PC in a > well-known place. When the frame is created by our AArch64 assembly- > langage code we'll be fine because we always do the right thing. > > The problem is that when we save the Java frame state in the Thread, > we're doing it for the sake of the runtime, not for debuggers, so we > don't always save all the information that a debugger might need. > > This patch should work for compiled native methods, but I'm not at all > sure about all of the other places where we call out from runtime > stubs to the VM. We perhaps check that the PC returned by > raw_sp.getAddressAt(-1 * VM.getVM().getAddressSize()) is in the code > cache before we use it. > > Anyway, try this: it should fix your immediate bug. I had a much better idea. We usually save the PC in the frame anchor, so we should use it if we can. Add a little sanity checking, and we should be good to go, and we won't need to grovel about in the stack. I looked in all the places where we save information in the frame anchor, and we almost always set the PC appropriately. I tried this patch with a few basic smoke tests, and it seems to be considerably better than what we have right now. The only place it fails is when we're executing some C++-compiled code which is called directly from the interpreter or from compiled code. We could apply some magic in those cases, but it would incur some overhead and I'm not sure it's worthwhile. Please try this instead and let me know how you get on. Thanks. diff -r 3954d70e1c50 src/jdk.hotspot.agent/share/classes/sun/jvm/hotspot/runtime/aarch64/AARCH64CurrentFrameGuess.java --- a/src/jdk.hotspot.agent/share/classes/sun/jvm/hotspot/runtime/aarch64/AARCH64CurrentFrameGuess.java Wed Feb 06 08:31:27 2019 +0100 +++ b/src/jdk.hotspot.agent/share/classes/sun/jvm/hotspot/runtime/aarch64/AARCH64CurrentFrameGuess.java Thu Feb 07 12:45:29 2019 +0000 @@ -223,8 +223,13 @@ } } - setValues(sp, fp, null); - + // We found a PC in the frame anchor. Check that it's plausible, and + // if it is, use it. + if (vm.isJavaPCDbg(pc)) { + setValues(sp, fp, pc); + } else { + setValues(sp, fp, null); + } return true; } } -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Thu Feb 7 15:39:46 2019 From: aph at redhat.com (Andrew Haley) Date: Thu, 7 Feb 2019 15:39:46 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: References: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com> <1fd9aa7f-c5f5-80ef-dd47-73756a318d31@redhat.com> Message-ID: <068399ec-fbb8-b881-7ea2-1b684a42652a@redhat.com> On 2/7/19 2:36 PM, Nick Gasson (Arm Technology China) wrote: > > Yeah I tried this method too (see the end of my first email). It > works fine except the PC is off by a few instructions. That can be > fixed quite easily though if required, and it always points into the > right method. We should fix those few cases. > I ended up doing the stack scanning thing because as far as I can > tell that constructor is only used when we need to find the return > PC from a native frame I don't think that ever happens. In the code I modified we know that we have a good PC in the frame anchor. In the cases where we have a native frame on the stack and nothing in the frame anchor we give up. At least, I can see no counter-cases. > (I might have been wrong about this), so I couldn't see how it would > ever get the right value. If we check vm.isJavaPCDbg() before we use > the SP[-1] value that will make the remaining callers a bit safer > (and set this.pc to null otherwise). That would be safe, for sure. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Fri Feb 8 23:45:26 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 8 Feb 2019 23:45:26 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 12 on AArch64 Message-ID: <95428742.754.1549669527134.JavaMail.jenkins@dc828b94788c> 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/jdk12/openjdk-jtreg-nightly-tests/summary/2019/038/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 5,510; fail: 4; error: 1; not run: 93 Build 1: aarch64/2019/jan/25 pass: 5,523; fail: 7; not run: 93 Build 2: aarch64/2019/jan/27 pass: 5,524; fail: 5; error: 1; not run: 93 Build 3: aarch64/2019/jan/29 pass: 5,524; fail: 5; error: 1; not run: 93 Build 4: aarch64/2019/jan/31 pass: 5,518; fail: 5; error: 1; not run: 93 Build 5: aarch64/2019/feb/03 pass: 5,517; fail: 6; error: 1; not run: 93 Build 6: aarch64/2019/feb/05 pass: 5,517; fail: 6; error: 1; not run: 93 Build 7: aarch64/2019/feb/07 pass: 5,518; fail: 6; not run: 93 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 8,528; fail: 482; error: 29 Build 1: aarch64/2019/jan/25 pass: 8,522; fail: 491; error: 27 Build 2: aarch64/2019/jan/27 pass: 8,540; fail: 488; error: 12 Build 3: aarch64/2019/jan/29 pass: 8,543; fail: 483; error: 14 Build 4: aarch64/2019/jan/31 pass: 8,530; fail: 491; error: 21 Build 5: aarch64/2019/feb/03 pass: 8,523; fail: 502; error: 17 Build 6: aarch64/2019/feb/05 pass: 8,492; fail: 520; error: 30 Build 7: aarch64/2019/feb/07 pass: 8,499; fail: 521; error: 22 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 3,992 Build 1: aarch64/2019/jan/25 pass: 3,992 Build 2: aarch64/2019/jan/27 pass: 3,992 Build 3: aarch64/2019/jan/29 pass: 3,992 Build 4: aarch64/2019/jan/31 pass: 3,992 Build 5: aarch64/2019/feb/03 pass: 3,992 Build 6: aarch64/2019/feb/05 pass: 3,992 Build 7: aarch64/2019/feb/07 pass: 3,992 Previous results can be found here: http://openjdk.linaro.org/jdk12/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.38x Relative performance: Server critical-jOPS (nc): 7.73x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk12/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/jdk12/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-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/022/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/027/results/ 2019-01-30 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/031/results/ 2019-02-04 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/034/results/ 2019-02-06 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/036/results/ 2019-02-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/038/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/ From ci_notify at linaro.org Fri Feb 8 23:49:20 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 8 Feb 2019 23:49:20 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 11u on AArch64 Message-ID: <1254242221.756.1549669761230.JavaMail.jenkins@dc828b94788c> 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/038/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 5,705; fail: 9; not run: 11,618 Build 1: aarch64/2019/jan/12 pass: 5,705; fail: 9; not run: 11,618 Build 2: aarch64/2019/jan/15 pass: 5,705; fail: 9; not run: 11,618 Build 3: aarch64/2019/jan/17 pass: 5,709; fail: 9; not run: 11,618 Build 4: aarch64/2019/jan/22 pass: 5,709; fail: 9; not run: 11,618 Build 5: aarch64/2019/jan/24 pass: 5,708; fail: 10; not run: 11,618 Build 6: aarch64/2019/jan/29 pass: 5,709; fail: 9; not run: 11,618 Build 7: aarch64/2019/jan/31 pass: 5,707; fail: 11; not run: 11,618 Build 8: aarch64/2019/feb/02 pass: 5,708; fail: 10; not run: 11,618 Build 9: aarch64/2019/feb/07 pass: 5,710; fail: 9; not run: 11,618 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 8,344; fail: 522; error: 29 Build 1: aarch64/2019/jan/12 pass: 8,376; fail: 496; error: 23 Build 2: aarch64/2019/jan/15 pass: 8,353; fail: 510; error: 32 Build 3: aarch64/2019/jan/17 pass: 8,386; fail: 493; error: 19 Build 4: aarch64/2019/jan/22 pass: 8,369; fail: 506; error: 23 Build 5: aarch64/2019/jan/24 pass: 8,366; fail: 507; error: 25 Build 6: aarch64/2019/jan/29 pass: 8,353; fail: 524; error: 22 Build 7: aarch64/2019/jan/31 pass: 8,372; fail: 502; error: 25 Build 8: aarch64/2019/feb/02 pass: 8,378; fail: 501; error: 21 Build 9: aarch64/2019/feb/07 pass: 8,364; fail: 507; error: 29 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 3,903 Build 1: aarch64/2019/jan/12 pass: 3,903 Build 2: aarch64/2019/jan/15 pass: 3,903 Build 3: aarch64/2019/jan/17 pass: 3,903 Build 4: aarch64/2019/jan/22 pass: 3,903 Build 5: aarch64/2019/jan/24 pass: 3,903 Build 6: aarch64/2019/jan/29 pass: 3,903 Build 7: aarch64/2019/jan/31 pass: 3,903 Build 8: aarch64/2019/feb/02 pass: 3,903 Build 9: aarch64/2019/feb/07 pass: 3,903 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.29x Relative performance: Server critical-jOPS (nc): 8.22x 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-01-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/010/results/ 2019-01-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/012/results/ 2019-01-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/015/results/ 2019-01-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/017/results/ 2019-01-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/022/results/ 2019-01-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/024/results/ 2019-01-30 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/031/results/ 2019-02-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/033/results/ 2019-02-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/038/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 Sat Feb 9 16:48:52 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sat, 9 Feb 2019 16:48:52 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <1006027338.829.1549730932890.JavaMail.jenkins@dc828b94788c> 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/039/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/2018/dec/31 pass: 5,556; fail: 19; error: 1; not run: 93 Build 1: aarch64/2019/jan/02 pass: 5,554; fail: 21; error: 1; not run: 93 Build 2: aarch64/2019/jan/04 pass: 5,562; fail: 19; error: 2; not run: 93 Build 3: aarch64/2019/jan/07 pass: 5,563; fail: 19; error: 1; not run: 93 Build 4: aarch64/2019/jan/09 pass: 5,564; fail: 20; error: 1; not run: 93 Build 5: aarch64/2019/jan/11 pass: 5,504; fail: 5; error: 1; not run: 93 Build 6: aarch64/2019/jan/16 pass: 5,511; fail: 6; error: 2; not run: 93 Build 7: aarch64/2019/jan/21 pass: 5,514; fail: 8; error: 1; not run: 93 Build 8: aarch64/2019/jan/24 pass: 5,520; fail: 5; error: 1; not run: 93 Build 9: aarch64/2019/jan/25 pass: 5,533; fail: 6; error: 1; not run: 93 Build 10: aarch64/2019/jan/28 pass: 5,533; fail: 6; error: 1; not run: 93 Build 11: aarch64/2019/jan/30 pass: 5,527; fail: 5; error: 2; not run: 93 Build 12: aarch64/2019/feb/04 pass: 5,527; fail: 7; error: 2; not run: 93 Build 13: aarch64/2019/feb/06 pass: 5,532; fail: 4; error: 1; not run: 93 Build 14: aarch64/2019/feb/08 pass: 5,519; fail: 19; error: 2; not run: 93 5 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2018/dec/31 pass: 8,590; fail: 670; error: 27 Build 1: aarch64/2019/jan/02 pass: 8,574; fail: 689; error: 24 Build 2: aarch64/2019/jan/04 pass: 8,591; fail: 677; error: 19 Build 3: aarch64/2019/jan/07 pass: 8,534; fail: 490; error: 16 Build 4: aarch64/2019/jan/09 pass: 8,545; fail: 483; error: 15 Build 5: aarch64/2019/jan/11 pass: 8,501; fail: 518; error: 25 Build 6: aarch64/2019/jan/16 pass: 8,553; fail: 480; error: 15 Build 7: aarch64/2019/jan/21 pass: 8,521; fail: 511; error: 20 Build 8: aarch64/2019/jan/24 pass: 8,533; fail: 503; error: 18 Build 9: aarch64/2019/jan/25 pass: 8,538; fail: 500; error: 20 Build 10: aarch64/2019/jan/28 pass: 8,543; fail: 496; error: 20 Build 11: aarch64/2019/jan/30 pass: 8,541; fail: 503; error: 19 Build 12: aarch64/2019/feb/04 pass: 8,539; fail: 506; error: 18 Build 13: aarch64/2019/feb/06 pass: 8,537; fail: 499; error: 27 Build 14: aarch64/2019/feb/08 pass: 8,530; fail: 515; error: 23 4 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2018/dec/31 pass: 3,996; fail: 4 Build 1: aarch64/2019/jan/02 pass: 3,996; fail: 4 Build 2: aarch64/2019/jan/04 pass: 3,996; fail: 4 Build 3: aarch64/2019/jan/07 pass: 3,993 Build 4: aarch64/2019/jan/09 pass: 3,993 Build 5: aarch64/2019/jan/11 pass: 3,991 Build 6: aarch64/2019/jan/16 pass: 3,993 Build 7: aarch64/2019/jan/21 pass: 3,993; fail: 1 Build 8: aarch64/2019/jan/24 pass: 3,993; fail: 1 Build 9: aarch64/2019/jan/25 pass: 3,993; fail: 1 Build 10: aarch64/2019/jan/28 pass: 3,994; fail: 1 Build 11: aarch64/2019/jan/30 pass: 3,994; fail: 1 Build 12: aarch64/2019/feb/04 pass: 3,994; fail: 1 Build 13: aarch64/2019/feb/06 pass: 3,994; fail: 1 Build 14: aarch64/2019/feb/08 pass: 3,994; fail: 1 ------------------------------------------------------------------------------- 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.48x 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: 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/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-01-03 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/002/results/ 2019-01-05 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/004/results/ 2019-01-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/007/results/ 2019-01-10 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/009/results/ 2019-01-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/011/results/ 2019-01-16 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/016/results/ 2019-01-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/021/results/ 2019-01-24 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/024/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/028/results/ 2019-01-31 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/030/results/ 2019-02-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/035/results/ 2019-02-07 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/037/results/ 2019-02-09 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/039/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 Mon Feb 11 07:54:57 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Mon, 11 Feb 2019 07:54:57 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 11u on AArch64 Message-ID: <1198835484.922.1549871698328.JavaMail.jenkins@dc828b94788c> 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/040/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 5,705; fail: 9; not run: 11,618 Build 1: aarch64/2019/jan/12 pass: 5,705; fail: 9; not run: 11,618 Build 2: aarch64/2019/jan/15 pass: 5,705; fail: 9; not run: 11,618 Build 3: aarch64/2019/jan/17 pass: 5,709; fail: 9; not run: 11,618 Build 4: aarch64/2019/jan/22 pass: 5,709; fail: 9; not run: 11,618 Build 5: aarch64/2019/jan/24 pass: 5,708; fail: 10; not run: 11,618 Build 6: aarch64/2019/jan/29 pass: 5,709; fail: 9; not run: 11,618 Build 7: aarch64/2019/jan/31 pass: 5,707; fail: 11; not run: 11,618 Build 8: aarch64/2019/feb/02 pass: 5,708; fail: 10; not run: 11,618 Build 9: aarch64/2019/feb/07 pass: 5,710; fail: 9; not run: 11,618 Build 10: aarch64/2019/feb/09 pass: 5,710; fail: 9; not run: 11,618 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 8,344; fail: 522; error: 29 Build 1: aarch64/2019/jan/12 pass: 8,376; fail: 496; error: 23 Build 2: aarch64/2019/jan/15 pass: 8,353; fail: 510; error: 32 Build 3: aarch64/2019/jan/17 pass: 8,386; fail: 493; error: 19 Build 4: aarch64/2019/jan/22 pass: 8,369; fail: 506; error: 23 Build 5: aarch64/2019/jan/24 pass: 8,366; fail: 507; error: 25 Build 6: aarch64/2019/jan/29 pass: 8,353; fail: 524; error: 22 Build 7: aarch64/2019/jan/31 pass: 8,372; fail: 502; error: 25 Build 8: aarch64/2019/feb/02 pass: 8,378; fail: 501; error: 21 Build 9: aarch64/2019/feb/07 pass: 8,364; fail: 507; error: 29 Build 10: aarch64/2019/feb/09 pass: 8,354; fail: 523; error: 23 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 3,903 Build 1: aarch64/2019/jan/12 pass: 3,903 Build 2: aarch64/2019/jan/15 pass: 3,903 Build 3: aarch64/2019/jan/17 pass: 3,903 Build 4: aarch64/2019/jan/22 pass: 3,903 Build 5: aarch64/2019/jan/24 pass: 3,903 Build 6: aarch64/2019/jan/29 pass: 3,903 Build 7: aarch64/2019/jan/31 pass: 3,903 Build 8: aarch64/2019/feb/02 pass: 3,903 Build 9: aarch64/2019/feb/07 pass: 3,903 Build 10: aarch64/2019/feb/09 pass: 3,903 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.04x Relative performance: Server critical-jOPS (nc): 7.72x 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-01-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/010/results/ 2019-01-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/012/results/ 2019-01-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/015/results/ 2019-01-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/017/results/ 2019-01-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/022/results/ 2019-01-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/024/results/ 2019-01-30 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/031/results/ 2019-02-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/033/results/ 2019-02-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/038/results/ 2019-02-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/040/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 Feb 11 07:57:54 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Mon, 11 Feb 2019 07:57:54 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 12 on AArch64 Message-ID: <1358448592.924.1549871874512.JavaMail.jenkins@dc828b94788c> 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/jdk12/openjdk-jtreg-nightly-tests/summary/2019/040/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 5,510; fail: 4; error: 1; not run: 93 Build 1: aarch64/2019/jan/25 pass: 5,523; fail: 7; not run: 93 Build 2: aarch64/2019/jan/27 pass: 5,524; fail: 5; error: 1; not run: 93 Build 3: aarch64/2019/jan/29 pass: 5,524; fail: 5; error: 1; not run: 93 Build 4: aarch64/2019/jan/31 pass: 5,518; fail: 5; error: 1; not run: 93 Build 5: aarch64/2019/feb/03 pass: 5,517; fail: 6; error: 1; not run: 93 Build 6: aarch64/2019/feb/05 pass: 5,517; fail: 6; error: 1; not run: 93 Build 7: aarch64/2019/feb/07 pass: 5,518; fail: 6; not run: 93 Build 8: aarch64/2019/feb/09 pass: 5,519; fail: 4; error: 1; not run: 93 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 8,528; fail: 482; error: 29 Build 1: aarch64/2019/jan/25 pass: 8,522; fail: 491; error: 27 Build 2: aarch64/2019/jan/27 pass: 8,540; fail: 488; error: 12 Build 3: aarch64/2019/jan/29 pass: 8,543; fail: 483; error: 14 Build 4: aarch64/2019/jan/31 pass: 8,530; fail: 491; error: 21 Build 5: aarch64/2019/feb/03 pass: 8,523; fail: 502; error: 17 Build 6: aarch64/2019/feb/05 pass: 8,492; fail: 520; error: 30 Build 7: aarch64/2019/feb/07 pass: 8,499; fail: 521; error: 22 Build 8: aarch64/2019/feb/09 pass: 8,525; fail: 501; error: 16 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 3,992 Build 1: aarch64/2019/jan/25 pass: 3,992 Build 2: aarch64/2019/jan/27 pass: 3,992 Build 3: aarch64/2019/jan/29 pass: 3,992 Build 4: aarch64/2019/jan/31 pass: 3,992 Build 5: aarch64/2019/feb/03 pass: 3,992 Build 6: aarch64/2019/feb/05 pass: 3,992 Build 7: aarch64/2019/feb/07 pass: 3,992 Build 8: aarch64/2019/feb/09 pass: 3,992 Previous results can be found here: http://openjdk.linaro.org/jdk12/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.12x Relative performance: Server critical-jOPS (nc): 7.80x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk12/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/jdk12/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-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/022/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/027/results/ 2019-01-30 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/031/results/ 2019-02-04 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/034/results/ 2019-02-06 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/036/results/ 2019-02-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/038/results/ 2019-02-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/040/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/ From stuart.monteith at linaro.org Mon Feb 11 13:27:10 2019 From: stuart.monteith at linaro.org (Stuart Monteith) Date: Mon, 11 Feb 2019 13:27:10 +0000 Subject: [aarch64-port-dev ] RFC: 64 bit literal oops In-Reply-To: <3a606763-b49f-b902-f4d3-180c386bed96@arm.com> References: <3a606763-b49f-b902-f4d3-180c386bed96@arm.com> Message-ID: Thanks for your comments Nick. I've updated the code with your comments: http://cr.openjdk.java.net/~smonteith/oop64/webrev-20190211/ BR, Stuart On Fri, 1 Feb 2019 at 02:50, Nick Gasson (Arm Technology China) wrote: > > Hi Stuart > > Just a few minor comments from looking through your patch. > > src/hotspot/cpu/aarch64/c1_CodeStubs_aarch64.cpp > > +// SRDM: Use64BitLiteralAddresses isn't initialized for the static > _patch_info_offset to be uses. > +int PatchingStub::patch_info_offset() { return > -NativeGeneralJump::get_instruction_size(); } > > "to be uses" -> "to be used"? > > src/hotspot/cpu/aarch64/globals_aarch64.hpp > > + experimental(bool, Use64BitLiteralAddresses, false, \ > + "Use 64 bit in literal addresses instead of 48 bits.") > > "Use 64 *bits* in ..." or "Use 64 bit literal addresses instead of 48 bit"? > > src/hotspot/cpu/aarch64/jvmciCodeInstaller_aarch64.cpp > > + // is therefore disables Use64BitLiteralAddresses until support > is enabled. > > s/is/it/ > > + // mov, movk, movk, [movk] <- SRDM This fails with > Use64BitLiteralAddresses > > Can we make this assert(!Use64BitLiteralAddresses, "...")? > > src/hotspot/cpu/aarch64/macroAssembler_aarch64.cpp > > + > + if (Use64BitLiteralAddresses) { > + assert(nativeInstruction_at(insn_addr+12)->is_movk(), "wrong > insns in patch"); > + Instruction_aarch64::patch(insn_addr+12, 20, 5, (dest >>= 16) & > 0xffff); > + instructions = 4; > + } > > Does it make sense to add `else assert(dest == 0, ">48 bit literal > address without Use64BitLiteralAddresses");' here? > > src/hotspot/cpu/aarch64/nativeInst_aarch64.cpp > > + if (!Use64BitLiteralAddresses) { > + // movz, movk, movk. > + return 3 * 4; > + } else { > + return 4 * 4; > + } > > It's clearer if the * 4 is * NativeInstruction::instruction_size; > > src/hotspot/cpu/aarch64/nativeInst_aarch64.hpp > > + return 4 * 4; > > Same here. > > src/hotspot/share/aot/aotLoader.cpp > > + if (Use64BitLiteralAddresses && UseAOT) { > + warning("64-bit Literal Addresses disabled due to UseAOT."); > + FLAG_SET_CMDLINE(bool, UseAOT, false); > + } > > Shouldn't it be FLAG_SET_CMDLINE(bool, Use64BitLiteralAddresses, false) > to match the warning? Probably don't need to capitalize "Literal Addresses". > > Thanks, > Nick > > > On 31/01/2019 21:55, Stuart Monteith wrote: > > I've redone the patch such that whether or not it is an oop, > > addresses are emitted and patched as 64-bit (movz + 3 x movk) when > > -XX:+Use64BitLiteralAdddresses is passed. > > > > I've annotated some more sections to clarify what instructions are > > being patched or sized, as well as some areas where it hasn't changed > > - it was worthwhile to do thi > > The Aarch64_specific_constant::instruction_size enum has been changed > > to a method. This has encroached on shared code. Arguably this could > > do with even more refactoring in NativeInst_aarch.(cpp|hpp) and the > > users thereof if it is to be consistent. > > > > Regarding JVM CI and Graal - ZGC doesn't support them yet. Graal will > > need to be changed to recognise the option and conditionally emit > > 64-bit addresses (at least in > > AArch64MacroAssembler::movNativeAddress(Register, long) > > I've added some more logic to disable Use64BitLiteralAddresses when > > UseAOT or JVMCI are enabled. > > > > The patch is: > > http://cr.openjdk.java.net/~smonteith/oop64/webrev-20190130/ > > > > I've opened a bug in JBS: https://bugs.openjdk.java.net/browse/JDK-8216491 > > > > I've been trying to track down the source of some of the constants for > > the sizes of code. In one instance we have: > > http://cr.openjdk.java.net/~smonteith/oop64/webrev-20190130/src/hotspot/cpu/aarch64/c1_LIRAssembler_aarch64.hpp.udiff.html > > > > ... there are apparently 12 instructions for each call stub. The > > emit_static_call_stub() method only uses 8 instructions, but with > > Use64BitLiteralAddresses enabled the warning "compilation bailout: > > exception handler overflow" is generated. > > I've changed the code to emit 14 instructions instead, but I've yet to > > find the call stub that requires 12 instructions. > > > > I'll follow up with the ZGC patch soon - there was a change upstream > > to lea that needs to be accommodated. > > > > BR, > > Stuart > > > > > > > > > > > > On Mon, 3 Dec 2018 at 18:40, Andrew Haley wrote: > >> > >> On 12/3/18 4:53 PM, Stuart Monteith wrote: > >> > >>> There is another possible option, which is to just avoid 48-bit > >>> literals, and just use 64-bit unconditionally everywhere. It would > >>> mean that we could be easily consistent and 52-bit VA would be easier > >>> to implement on top of it. Again, I seek people's opinions. > >> > >> Could well be. I am starting to wonder if it is worth the effort. > >> Maybe the best thing to do is have a global 48- to 64-bit switch > >> and use it everywhere we want a pointer literal. > >> > >> Please don't put code of any complexity into header files. Put it > >> into .c files instead. > >> > >> The logic in MacroAssembler::movoop is a already a mess, and > >> adding an isOop flag to pass to doesn't help. I think it would > >> make more sense to have explicit 48- and 64-bit mov methods, and > >> let MacroAssembler::mov(Register, Address) control which one is > >> called. > >> > >> This hunk makes no sense. The comment directly contradicts > >> the code: > >> > >> enum Aarch64_specific_constants { > >> instruction_size = 3 * 4, // movz, movk, movk, [movk]. See movptr(). > >> instruction_offset = 0, > >> displacement_offset = 0, > >> }; > >> > >> It makes no sense to have instruction_size be a constant here. > >> I guess it never did. > >> > >> -- > >> Andrew Haley > >> Java Platform Lead Engineer > >> Red Hat UK Ltd. > >> EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Tue Feb 12 02:04:17 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Tue, 12 Feb 2019 02:04:17 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <1732565116.1131.1549937057730.JavaMail.jenkins@dc828b94788c> 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/042/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/jan/02 pass: 5,554; fail: 21; error: 1; not run: 93 Build 1: aarch64/2019/jan/04 pass: 5,562; fail: 19; error: 2; not run: 93 Build 2: aarch64/2019/jan/07 pass: 5,563; fail: 19; error: 1; not run: 93 Build 3: aarch64/2019/jan/09 pass: 5,564; fail: 20; error: 1; not run: 93 Build 4: aarch64/2019/jan/11 pass: 5,504; fail: 5; error: 1; not run: 93 Build 5: aarch64/2019/jan/16 pass: 5,511; fail: 6; error: 2; not run: 93 Build 6: aarch64/2019/jan/21 pass: 5,514; fail: 8; error: 1; not run: 93 Build 7: aarch64/2019/jan/24 pass: 5,520; fail: 5; error: 1; not run: 93 Build 8: aarch64/2019/jan/25 pass: 5,533; fail: 6; error: 1; not run: 93 Build 9: aarch64/2019/jan/28 pass: 5,533; fail: 6; error: 1; not run: 93 Build 10: aarch64/2019/jan/30 pass: 5,527; fail: 5; error: 2; not run: 93 Build 11: aarch64/2019/feb/04 pass: 5,527; fail: 7; error: 2; not run: 93 Build 12: aarch64/2019/feb/06 pass: 5,532; fail: 4; error: 1; not run: 93 Build 13: aarch64/2019/feb/08 pass: 5,519; fail: 19; error: 2; not run: 93 Build 14: aarch64/2019/feb/11 pass: 5,527; fail: 11; error: 2; not run: 93 3 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/02 pass: 8,574; fail: 689; error: 24 Build 1: aarch64/2019/jan/04 pass: 8,591; fail: 677; error: 19 Build 2: aarch64/2019/jan/07 pass: 8,534; fail: 490; error: 16 Build 3: aarch64/2019/jan/09 pass: 8,545; fail: 483; error: 15 Build 4: aarch64/2019/jan/11 pass: 8,501; fail: 518; error: 25 Build 5: aarch64/2019/jan/16 pass: 8,553; fail: 480; error: 15 Build 6: aarch64/2019/jan/21 pass: 8,521; fail: 511; error: 20 Build 7: aarch64/2019/jan/24 pass: 8,533; fail: 503; error: 18 Build 8: aarch64/2019/jan/25 pass: 8,538; fail: 500; error: 20 Build 9: aarch64/2019/jan/28 pass: 8,543; fail: 496; error: 20 Build 10: aarch64/2019/jan/30 pass: 8,541; fail: 503; error: 19 Build 11: aarch64/2019/feb/04 pass: 8,539; fail: 506; error: 18 Build 12: aarch64/2019/feb/06 pass: 8,537; fail: 499; error: 27 Build 13: aarch64/2019/feb/08 pass: 8,530; fail: 515; error: 23 Build 14: aarch64/2019/feb/11 pass: 8,559; fail: 490; error: 15 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/02 pass: 3,996; fail: 4 Build 1: aarch64/2019/jan/04 pass: 3,996; fail: 4 Build 2: aarch64/2019/jan/07 pass: 3,993 Build 3: aarch64/2019/jan/09 pass: 3,993 Build 4: aarch64/2019/jan/11 pass: 3,991 Build 5: aarch64/2019/jan/16 pass: 3,993 Build 6: aarch64/2019/jan/21 pass: 3,993; fail: 1 Build 7: aarch64/2019/jan/24 pass: 3,993; fail: 1 Build 8: aarch64/2019/jan/25 pass: 3,993; fail: 1 Build 9: aarch64/2019/jan/28 pass: 3,994; fail: 1 Build 10: aarch64/2019/jan/30 pass: 3,994; fail: 1 Build 11: aarch64/2019/feb/04 pass: 3,994; fail: 1 Build 12: aarch64/2019/feb/06 pass: 3,994; fail: 1 Build 13: aarch64/2019/feb/08 pass: 3,994; fail: 1 Build 14: aarch64/2019/feb/11 pass: 3,994; fail: 1 ------------------------------------------------------------------------------- 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): 8.64x 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: 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/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-03 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/002/results/ 2019-01-05 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/004/results/ 2019-01-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/007/results/ 2019-01-10 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/009/results/ 2019-01-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/011/results/ 2019-01-16 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/016/results/ 2019-01-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/021/results/ 2019-01-24 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/024/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/028/results/ 2019-01-31 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/030/results/ 2019-02-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/035/results/ 2019-02-07 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/037/results/ 2019-02-09 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/039/results/ 2019-02-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/042/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 Feb 12 02:54:56 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Tue, 12 Feb 2019 02:54:56 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> Message-ID: Corresponding 8u backport patch: http://cr.openjdk.java.net/~fyang/8218185-backport/webrev.00/ Also Jcstress tested, OK? Thanks, Felix > > Webrev: http://cr.openjdk.java.net/~fyang/8218185/webrev.00/ > > 8218185: aarch64: missing LoadStore barrier in TemplateTable::putfield_or_static > Reviewed-by: aph > Contributed-by: lunliu93 at gmail.com From aph at redhat.com Tue Feb 12 08:58:23 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 12 Feb 2019 08:58:23 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> Message-ID: On 2/12/19 2:54 AM, Yangfei (Felix) wrote: > Corresponding 8u backport patch: > http://cr.openjdk.java.net/~fyang/8218185-backport/webrev.00/ > > Also Jcstress tested, OK? OK. It's never been know to cause any problems, but at least in theory it might break. But you need to post this to the 8u list. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From felix.yang at huawei.com Tue Feb 12 09:05:05 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Tue, 12 Feb 2019 09:05:05 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> Message-ID: This is aarch64-specific and is supposed to be merged into: aarch64-port/jdk8u-shenandoah and aarch64-port/jdk8u repos. Do we still need to send this to the 8u list ? If true, should I simply CC to that list? Thanks, Felix > > On 2/12/19 2:54 AM, Yangfei (Felix) wrote: > > Corresponding 8u backport patch: > > http://cr.openjdk.java.net/~fyang/8218185-backport/webrev.00/ > > > > Also Jcstress tested, OK? > > OK. It's never been know to cause any problems, but at least in theory it might > break. But you need to post this to the 8u list. > > -- > Andrew Haley > Java Platform Lead Engineer > Red Hat UK Ltd. > EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Tue Feb 12 09:28:56 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 12 Feb 2019 09:28:56 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> Message-ID: <1880b8f1-7563-f50e-aef9-5c6032672844@redhat.com> On 2/12/19 9:05 AM, Yangfei (Felix) wrote: > This is aarch64-specific and is supposed to be merged into: aarch64-port/jdk8u-shenandoah and aarch64-port/jdk8u repos. > > Do we still need to send this to the 8u list ? If true, should I simply CC to that list? Sorry, of course. No, don't post to 8u. Please forget I said that! :-) Only halfway down my first cup of coffee... -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From felix.yang at huawei.com Tue Feb 12 15:16:42 2019 From: felix.yang at huawei.com (felix.yang at huawei.com) Date: Tue, 12 Feb 2019 15:16:42 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 8218185: aarch64: missing LoadStore barrier in TemplateTable::putfield_or_static Message-ID: <201902121516.x1CFGhj5003505@aojmv0008.oracle.com> Changeset: f98005f3f634 Author: fyang Date: 2019-02-11 17:09 +0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/f98005f3f634 8218185: aarch64: missing LoadStore barrier in TemplateTable::putfield_or_static Reviewed-by: aph Contributed-by: lunliu93 at gmail.com ! src/cpu/aarch64/vm/templateTable_aarch64.cpp From felix.yang at huawei.com Tue Feb 12 15:17:46 2019 From: felix.yang at huawei.com (felix.yang at huawei.com) Date: Tue, 12 Feb 2019 15:17:46 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/hotspot: 8218185: aarch64: missing LoadStore barrier in TemplateTable::putfield_or_static Message-ID: <201902121517.x1CFHkUM004085@aojmv0008.oracle.com> Changeset: d1cf908df0a7 Author: fyang Date: 2019-02-11 17:09 +0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/d1cf908df0a7 8218185: aarch64: missing LoadStore barrier in TemplateTable::putfield_or_static Reviewed-by: aph Contributed-by: lunliu93 at gmail.com ! src/cpu/aarch64/vm/templateTable_aarch64.cpp From aph at redhat.com Tue Feb 12 15:32:48 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 12 Feb 2019 15:32:48 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: <068399ec-fbb8-b881-7ea2-1b684a42652a@redhat.com> References: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com> <1fd9aa7f-c5f5-80ef-dd47-73756a318d31@redhat.com> <068399ec-fbb8-b881-7ea2-1b684a42652a@redhat.com> Message-ID: <976b890a-79e6-e8d1-e516-97e15bdb6658@redhat.com> What's the status of this? Are you still looking at it? On 2/7/19 3:39 PM, Andrew Haley wrote: > On 2/7/19 2:36 PM, Nick Gasson (Arm Technology China) wrote: >> >> Yeah I tried this method too (see the end of my first email). It >> works fine except the PC is off by a few instructions. That can be >> fixed quite easily though if required, and it always points into the >> right method. > > We should fix those few cases. > >> I ended up doing the stack scanning thing because as far as I can >> tell that constructor is only used when we need to find the return >> PC from a native frame > > I don't think that ever happens. In the code I modified we know that > we have a good PC in the frame anchor. In the cases where we have a > native frame on the stack and nothing in the frame anchor we give > up. At least, I can see no counter-cases. > >> (I might have been wrong about this), so I couldn't see how it would >> ever get the right value. If we check vm.isJavaPCDbg() before we use >> the SP[-1] value that will make the remaining callers a bit safer >> (and set this.pc to null otherwise). > > That would be safe, for sure. > -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Tue Feb 12 18:49:44 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 12 Feb 2019 18:49:44 +0000 Subject: [aarch64-port-dev ] RFC: 64 bit literal oops In-Reply-To: References: <3a606763-b49f-b902-f4d3-180c386bed96@arm.com> Message-ID: On 2/11/19 1:27 PM, Stuart Monteith wrote: > Thanks for your comments Nick. > > I've updated the code with your comments: > http://cr.openjdk.java.net/~smonteith/oop64/webrev-20190211/ It's pretty close. Two things: I don't think you really have to calculate things like NativeGeneralJump::instruction_size every time. They don't have to be compile-time constants, they can be fields that you initialize immediately after you've set Use64BitLiteralAddresses. If you do that then you won't need to change so much code. +// SRDM: Use64BitLiteralAddresses isn't initialized for the static _patch_info_offset to be used. ? -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Wed Feb 13 03:31:54 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Wed, 13 Feb 2019 03:31:54 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 11u on AArch64 Message-ID: <1252423227.1327.1550028715142.JavaMail.jenkins@dc828b94788c> 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/043/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 5,705; fail: 9; not run: 11,618 Build 1: aarch64/2019/jan/12 pass: 5,705; fail: 9; not run: 11,618 Build 2: aarch64/2019/jan/15 pass: 5,705; fail: 9; not run: 11,618 Build 3: aarch64/2019/jan/17 pass: 5,709; fail: 9; not run: 11,618 Build 4: aarch64/2019/jan/22 pass: 5,709; fail: 9; not run: 11,618 Build 5: aarch64/2019/jan/24 pass: 5,708; fail: 10; not run: 11,618 Build 6: aarch64/2019/jan/29 pass: 5,709; fail: 9; not run: 11,618 Build 7: aarch64/2019/jan/31 pass: 5,707; fail: 11; not run: 11,618 Build 8: aarch64/2019/feb/02 pass: 5,708; fail: 10; not run: 11,618 Build 9: aarch64/2019/feb/07 pass: 5,710; fail: 9; not run: 11,618 Build 10: aarch64/2019/feb/09 pass: 5,710; fail: 9; not run: 11,618 Build 11: aarch64/2019/feb/12 pass: 5,709; fail: 10; not run: 11,618 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 8,344; fail: 522; error: 29 Build 1: aarch64/2019/jan/12 pass: 8,376; fail: 496; error: 23 Build 2: aarch64/2019/jan/15 pass: 8,353; fail: 510; error: 32 Build 3: aarch64/2019/jan/17 pass: 8,386; fail: 493; error: 19 Build 4: aarch64/2019/jan/22 pass: 8,369; fail: 506; error: 23 Build 5: aarch64/2019/jan/24 pass: 8,366; fail: 507; error: 25 Build 6: aarch64/2019/jan/29 pass: 8,353; fail: 524; error: 22 Build 7: aarch64/2019/jan/31 pass: 8,372; fail: 502; error: 25 Build 8: aarch64/2019/feb/02 pass: 8,378; fail: 501; error: 21 Build 9: aarch64/2019/feb/07 pass: 8,364; fail: 507; error: 29 Build 10: aarch64/2019/feb/09 pass: 8,354; fail: 523; error: 23 Build 11: aarch64/2019/feb/12 pass: 8,358; fail: 519; error: 24 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 3,903 Build 1: aarch64/2019/jan/12 pass: 3,903 Build 2: aarch64/2019/jan/15 pass: 3,903 Build 3: aarch64/2019/jan/17 pass: 3,903 Build 4: aarch64/2019/jan/22 pass: 3,903 Build 5: aarch64/2019/jan/24 pass: 3,903 Build 6: aarch64/2019/jan/29 pass: 3,903 Build 7: aarch64/2019/jan/31 pass: 3,903 Build 8: aarch64/2019/feb/02 pass: 3,903 Build 9: aarch64/2019/feb/07 pass: 3,903 Build 10: aarch64/2019/feb/09 pass: 3,903 Build 11: aarch64/2019/feb/12 pass: 3,903 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.04x Relative performance: Server critical-jOPS (nc): 7.60x 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-01-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/010/results/ 2019-01-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/012/results/ 2019-01-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/015/results/ 2019-01-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/017/results/ 2019-01-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/022/results/ 2019-01-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/024/results/ 2019-01-30 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/031/results/ 2019-02-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/033/results/ 2019-02-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/038/results/ 2019-02-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/040/results/ 2019-02-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/043/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 Thu Feb 14 00:55:57 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Thu, 14 Feb 2019 00:55:57 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <2057753037.1476.1550105757555.JavaMail.jenkins@dc828b94788c> 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/044/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/jan/04 pass: 5,562; fail: 19; error: 2; not run: 93 Build 1: aarch64/2019/jan/07 pass: 5,563; fail: 19; error: 1; not run: 93 Build 2: aarch64/2019/jan/09 pass: 5,564; fail: 20; error: 1; not run: 93 Build 3: aarch64/2019/jan/11 pass: 5,504; fail: 5; error: 1; not run: 93 Build 4: aarch64/2019/jan/16 pass: 5,511; fail: 6; error: 2; not run: 93 Build 5: aarch64/2019/jan/21 pass: 5,514; fail: 8; error: 1; not run: 93 Build 6: aarch64/2019/jan/24 pass: 5,520; fail: 5; error: 1; not run: 93 Build 7: aarch64/2019/jan/25 pass: 5,533; fail: 6; error: 1; not run: 93 Build 8: aarch64/2019/jan/28 pass: 5,533; fail: 6; error: 1; not run: 93 Build 9: aarch64/2019/jan/30 pass: 5,527; fail: 5; error: 2; not run: 93 Build 10: aarch64/2019/feb/04 pass: 5,527; fail: 7; error: 2; not run: 93 Build 11: aarch64/2019/feb/06 pass: 5,532; fail: 4; error: 1; not run: 93 Build 12: aarch64/2019/feb/08 pass: 5,519; fail: 19; error: 2; not run: 93 Build 13: aarch64/2019/feb/11 pass: 5,527; fail: 11; error: 2; not run: 93 Build 14: aarch64/2019/feb/13 pass: 5,537; fail: 4; not run: 93 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/04 pass: 8,591; fail: 677; error: 19 Build 1: aarch64/2019/jan/07 pass: 8,534; fail: 490; error: 16 Build 2: aarch64/2019/jan/09 pass: 8,545; fail: 483; error: 15 Build 3: aarch64/2019/jan/11 pass: 8,501; fail: 518; error: 25 Build 4: aarch64/2019/jan/16 pass: 8,553; fail: 480; error: 15 Build 5: aarch64/2019/jan/21 pass: 8,521; fail: 511; error: 20 Build 6: aarch64/2019/jan/24 pass: 8,533; fail: 503; error: 18 Build 7: aarch64/2019/jan/25 pass: 8,538; fail: 500; error: 20 Build 8: aarch64/2019/jan/28 pass: 8,543; fail: 496; error: 20 Build 9: aarch64/2019/jan/30 pass: 8,541; fail: 503; error: 19 Build 10: aarch64/2019/feb/04 pass: 8,539; fail: 506; error: 18 Build 11: aarch64/2019/feb/06 pass: 8,537; fail: 499; error: 27 Build 12: aarch64/2019/feb/08 pass: 8,530; fail: 515; error: 23 Build 13: aarch64/2019/feb/11 pass: 8,559; fail: 490; error: 15 Build 14: aarch64/2019/feb/13 pass: 8,534; fail: 512; error: 18 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/04 pass: 3,996; fail: 4 Build 1: aarch64/2019/jan/07 pass: 3,993 Build 2: aarch64/2019/jan/09 pass: 3,993 Build 3: aarch64/2019/jan/11 pass: 3,991 Build 4: aarch64/2019/jan/16 pass: 3,993 Build 5: aarch64/2019/jan/21 pass: 3,993; fail: 1 Build 6: aarch64/2019/jan/24 pass: 3,993; fail: 1 Build 7: aarch64/2019/jan/25 pass: 3,993; fail: 1 Build 8: aarch64/2019/jan/28 pass: 3,994; fail: 1 Build 9: aarch64/2019/jan/30 pass: 3,994; fail: 1 Build 10: aarch64/2019/feb/04 pass: 3,994; fail: 1 Build 11: aarch64/2019/feb/06 pass: 3,994; fail: 1 Build 12: aarch64/2019/feb/08 pass: 3,994; fail: 1 Build 13: aarch64/2019/feb/11 pass: 3,994; fail: 1 Build 14: aarch64/2019/feb/13 pass: 3,994; fail: 1 ------------------------------------------------------------------------------- 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.71x 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: 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-05 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/004/results/ 2019-01-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/007/results/ 2019-01-10 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/009/results/ 2019-01-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/011/results/ 2019-01-16 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/016/results/ 2019-01-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/021/results/ 2019-01-24 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/024/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/028/results/ 2019-01-31 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/030/results/ 2019-02-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/035/results/ 2019-02-07 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/037/results/ 2019-02-09 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/039/results/ 2019-02-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/042/results/ 2019-02-14 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/044/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 Feb 14 01:16:51 2019 From: Nick.Gasson at arm.com (Nick Gasson (Arm Technology China)) Date: Thu, 14 Feb 2019 01:16:51 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: <976b890a-79e6-e8d1-e516-97e15bdb6658@redhat.com> References: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com> <1fd9aa7f-c5f5-80ef-dd47-73756a318d31@redhat.com> <068399ec-fbb8-b881-7ea2-1b684a42652a@redhat.com> <976b890a-79e6-e8d1-e516-97e15bdb6658@redhat.com> Message-ID: On 12/02/2019 23:32, Andrew Haley wrote: > What's the status of this? Are you still looking at it? > Apologies, I was on holiday until today so haven't done anything on it. I'll send an updated patch shortly... Nick From ci_notify at linaro.org Thu Feb 14 14:33:53 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Thu, 14 Feb 2019 14:33:53 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <556894532.1526.1550154833963.JavaMail.jenkins@dc828b94788c> 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/045/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 792; fail: 16; error: 3 Build 1: aarch64/2019/feb/03 pass: 800; fail: 9; error: 2 Build 2: aarch64/2019/feb/14 pass: 799; fail: 9; error: 3 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 5,778; fail: 236; error: 28 Build 1: aarch64/2019/feb/03 pass: 5,756; fail: 261; error: 25 Build 2: aarch64/2019/feb/14 pass: 5,761; fail: 257; error: 24 ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 3,114; fail: 2 Build 1: aarch64/2019/feb/03 pass: 3,114; fail: 2 Build 2: aarch64/2019/feb/14 pass: 3,114; fail: 2 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.81x Relative performance: Server critical-jOPS (nc): 8.99x 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-04 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/034/results/ 2019-02-14 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/045/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From stuart.monteith at linaro.org Thu Feb 14 17:52:00 2019 From: stuart.monteith at linaro.org (Stuart Monteith) Date: Thu, 14 Feb 2019 17:52:00 +0000 Subject: [aarch64-port-dev ] RFC: 64 bit literal oops In-Reply-To: References: <3a606763-b49f-b902-f4d3-180c386bed96@arm.com> Message-ID: Thanks for taking a look. I've updated it here: http://cr.openjdk.java.net/~smonteith/oop64/webrev-20190214/ The stub code size needs to be increased to 14 instructions because of the construction of 64-bit constants in the main code. BR, Stuart On Tue, 12 Feb 2019 at 18:49, Andrew Haley wrote: > > On 2/11/19 1:27 PM, Stuart Monteith wrote: > > Thanks for your comments Nick. > > > > I've updated the code with your comments: > > http://cr.openjdk.java.net/~smonteith/oop64/webrev-20190211/ > > It's pretty close. > > Two things: > > I don't think you really have to calculate things like > NativeGeneralJump::instruction_size every time. They don't have to be > compile-time constants, they can be fields that you initialize > immediately after you've set Use64BitLiteralAddresses. If you do that > then you won't need to change so much code. > > +// SRDM: Use64BitLiteralAddresses isn't initialized for the static _patch_info_offset to be used. > > ? > > -- > Andrew Haley > Java Platform Lead Engineer > Red Hat UK Ltd. > EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From mbalao at redhat.com Thu Feb 14 19:49:52 2019 From: mbalao at redhat.com (Martin Balao) Date: Thu, 14 Feb 2019 16:49:52 -0300 Subject: [aarch64-port-dev ] [aarch64-port-dev] RFR 8219011: Implement MacroAssembler::warn method on AArch64 Message-ID: <09fc866c-0d4c-622c-238d-6920d74b2360@redhat.com> Hi, I'd like to propose a patch for JDK-8219011 [0]: * http://cr.openjdk.java.net/~mbalao/webrevs/8219011/8219011.webrev.00/ * http://cr.openjdk.java.net/~mbalao/webrevs/8219011/8219011.webrev.00.zip Thanks, Martin.- -- [0] - https://bugs.openjdk.java.net/browse/JDK-8219011 From adinn at redhat.com Fri Feb 15 09:08:20 2019 From: adinn at redhat.com (Andrew Dinn) Date: Fri, 15 Feb 2019 09:08:20 +0000 Subject: [aarch64-port-dev ] [aarch64-port-dev] RFR 8219011: Implement MacroAssembler::warn method on AArch64 In-Reply-To: <09fc866c-0d4c-622c-238d-6920d74b2360@redhat.com> References: <09fc866c-0d4c-622c-238d-6920d74b2360@redhat.com> Message-ID: Hi Martin, On 14/02/2019 19:49, Martin Balao wrote: > I'd like to propose a patch for JDK-8219011 [0]: > > * http://cr.openjdk.java.net/~mbalao/webrevs/8219011/8219011.webrev.00/ > * http://cr.openjdk.java.net/~mbalao/webrevs/8219011/8219011.webrev.00.zip > > Thanks, > Martin.- > > -- > [0] - https://bugs.openjdk.java.net/browse/JDK-8219011 Yes, that patch looks good (and very useful). Reviewed. 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 mbalao at redhat.com Fri Feb 15 22:23:55 2019 From: mbalao at redhat.com (Martin Balao) Date: Fri, 15 Feb 2019 19:23:55 -0300 Subject: [aarch64-port-dev ] [aarch64-port-dev] RFR 8219011: Implement MacroAssembler::warn method on AArch64 In-Reply-To: References: <09fc866c-0d4c-622c-238d-6920d74b2360@redhat.com> Message-ID: <573d08b1-c0b8-436f-78b9-b3913ac07992@redhat.com> On 2/15/19 6:08 AM, Andrew Dinn wrote: > > Reviewed. > Thanks http://hg.openjdk.java.net/jdk/jdk/rev/72709e703abd From ci_notify at linaro.org Fri Feb 15 23:52:22 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 15 Feb 2019 23:52:22 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <1789725788.1810.1550274742759.JavaMail.jenkins@dc828b94788c> 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/046/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/jan/07 pass: 5,563; fail: 19; error: 1; not run: 93 Build 1: aarch64/2019/jan/09 pass: 5,564; fail: 20; error: 1; not run: 93 Build 2: aarch64/2019/jan/11 pass: 5,504; fail: 5; error: 1; not run: 93 Build 3: aarch64/2019/jan/16 pass: 5,511; fail: 6; error: 2; not run: 93 Build 4: aarch64/2019/jan/21 pass: 5,514; fail: 8; error: 1; not run: 93 Build 5: aarch64/2019/jan/24 pass: 5,520; fail: 5; error: 1; not run: 93 Build 6: aarch64/2019/jan/25 pass: 5,533; fail: 6; error: 1; not run: 93 Build 7: aarch64/2019/jan/28 pass: 5,533; fail: 6; error: 1; not run: 93 Build 8: aarch64/2019/jan/30 pass: 5,527; fail: 5; error: 2; not run: 93 Build 9: aarch64/2019/feb/04 pass: 5,527; fail: 7; error: 2; not run: 93 Build 10: aarch64/2019/feb/06 pass: 5,532; fail: 4; error: 1; not run: 93 Build 11: aarch64/2019/feb/08 pass: 5,519; fail: 19; error: 2; not run: 93 Build 12: aarch64/2019/feb/11 pass: 5,527; fail: 11; error: 2; not run: 93 Build 13: aarch64/2019/feb/13 pass: 5,537; fail: 4; not run: 93 Build 14: aarch64/2019/feb/15 pass: 5,538; fail: 4; not run: 93 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/07 pass: 8,534; fail: 490; error: 16 Build 1: aarch64/2019/jan/09 pass: 8,545; fail: 483; error: 15 Build 2: aarch64/2019/jan/11 pass: 8,501; fail: 518; error: 25 Build 3: aarch64/2019/jan/16 pass: 8,553; fail: 480; error: 15 Build 4: aarch64/2019/jan/21 pass: 8,521; fail: 511; error: 20 Build 5: aarch64/2019/jan/24 pass: 8,533; fail: 503; error: 18 Build 6: aarch64/2019/jan/25 pass: 8,538; fail: 500; error: 20 Build 7: aarch64/2019/jan/28 pass: 8,543; fail: 496; error: 20 Build 8: aarch64/2019/jan/30 pass: 8,541; fail: 503; error: 19 Build 9: aarch64/2019/feb/04 pass: 8,539; fail: 506; error: 18 Build 10: aarch64/2019/feb/06 pass: 8,537; fail: 499; error: 27 Build 11: aarch64/2019/feb/08 pass: 8,530; fail: 515; error: 23 Build 12: aarch64/2019/feb/11 pass: 8,559; fail: 490; error: 15 Build 13: aarch64/2019/feb/13 pass: 8,534; fail: 512; error: 18 Build 14: aarch64/2019/feb/15 pass: 8,556; fail: 492; error: 16 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/07 pass: 3,993 Build 1: aarch64/2019/jan/09 pass: 3,993 Build 2: aarch64/2019/jan/11 pass: 3,991 Build 3: aarch64/2019/jan/16 pass: 3,993 Build 4: aarch64/2019/jan/21 pass: 3,993; fail: 1 Build 5: aarch64/2019/jan/24 pass: 3,993; fail: 1 Build 6: aarch64/2019/jan/25 pass: 3,993; fail: 1 Build 7: aarch64/2019/jan/28 pass: 3,994; fail: 1 Build 8: aarch64/2019/jan/30 pass: 3,994; fail: 1 Build 9: aarch64/2019/feb/04 pass: 3,994; fail: 1 Build 10: aarch64/2019/feb/06 pass: 3,994; fail: 1 Build 11: aarch64/2019/feb/08 pass: 3,994; fail: 1 Build 12: aarch64/2019/feb/11 pass: 3,994; fail: 1 Build 13: aarch64/2019/feb/13 pass: 3,994; fail: 1 Build 14: aarch64/2019/feb/15 pass: 3,995 ------------------------------------------------------------------------------- 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): 8.90x 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-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/007/results/ 2019-01-10 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/009/results/ 2019-01-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/011/results/ 2019-01-16 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/016/results/ 2019-01-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/021/results/ 2019-01-24 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/024/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/028/results/ 2019-01-31 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/030/results/ 2019-02-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/035/results/ 2019-02-07 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/037/results/ 2019-02-09 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/039/results/ 2019-02-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/042/results/ 2019-02-14 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/044/results/ 2019-02-15 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/046/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 Feb 17 03:13:57 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Sun, 17 Feb 2019 03:13:57 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 11u on AArch64 Message-ID: <1303249476.1949.1550373237503.JavaMail.jenkins@dc828b94788c> 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/047/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 5,705; fail: 9; not run: 11,618 Build 1: aarch64/2019/jan/12 pass: 5,705; fail: 9; not run: 11,618 Build 2: aarch64/2019/jan/15 pass: 5,705; fail: 9; not run: 11,618 Build 3: aarch64/2019/jan/17 pass: 5,709; fail: 9; not run: 11,618 Build 4: aarch64/2019/jan/22 pass: 5,709; fail: 9; not run: 11,618 Build 5: aarch64/2019/jan/24 pass: 5,708; fail: 10; not run: 11,618 Build 6: aarch64/2019/jan/29 pass: 5,709; fail: 9; not run: 11,618 Build 7: aarch64/2019/jan/31 pass: 5,707; fail: 11; not run: 11,618 Build 8: aarch64/2019/feb/02 pass: 5,708; fail: 10; not run: 11,618 Build 9: aarch64/2019/feb/07 pass: 5,710; fail: 9; not run: 11,618 Build 10: aarch64/2019/feb/09 pass: 5,710; fail: 9; not run: 11,618 Build 11: aarch64/2019/feb/12 pass: 5,709; fail: 10; not run: 11,618 Build 12: aarch64/2019/feb/16 pass: 5,713; fail: 10; not run: 11,618 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 8,344; fail: 522; error: 29 Build 1: aarch64/2019/jan/12 pass: 8,376; fail: 496; error: 23 Build 2: aarch64/2019/jan/15 pass: 8,353; fail: 510; error: 32 Build 3: aarch64/2019/jan/17 pass: 8,386; fail: 493; error: 19 Build 4: aarch64/2019/jan/22 pass: 8,369; fail: 506; error: 23 Build 5: aarch64/2019/jan/24 pass: 8,366; fail: 507; error: 25 Build 6: aarch64/2019/jan/29 pass: 8,353; fail: 524; error: 22 Build 7: aarch64/2019/jan/31 pass: 8,372; fail: 502; error: 25 Build 8: aarch64/2019/feb/02 pass: 8,378; fail: 501; error: 21 Build 9: aarch64/2019/feb/07 pass: 8,364; fail: 507; error: 29 Build 10: aarch64/2019/feb/09 pass: 8,354; fail: 523; error: 23 Build 11: aarch64/2019/feb/12 pass: 8,358; fail: 519; error: 24 Build 12: aarch64/2019/feb/16 pass: 8,356; fail: 520; error: 25 5 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 3,903 Build 1: aarch64/2019/jan/12 pass: 3,903 Build 2: aarch64/2019/jan/15 pass: 3,903 Build 3: aarch64/2019/jan/17 pass: 3,903 Build 4: aarch64/2019/jan/22 pass: 3,903 Build 5: aarch64/2019/jan/24 pass: 3,903 Build 6: aarch64/2019/jan/29 pass: 3,903 Build 7: aarch64/2019/jan/31 pass: 3,903 Build 8: aarch64/2019/feb/02 pass: 3,903 Build 9: aarch64/2019/feb/07 pass: 3,903 Build 10: aarch64/2019/feb/09 pass: 3,903 Build 11: aarch64/2019/feb/12 pass: 3,903 Build 12: aarch64/2019/feb/16 pass: 3,903 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.38x Relative performance: Server critical-jOPS (nc): 7.17x 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-01-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/010/results/ 2019-01-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/012/results/ 2019-01-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/015/results/ 2019-01-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/017/results/ 2019-01-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/022/results/ 2019-01-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/024/results/ 2019-01-30 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/031/results/ 2019-02-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/033/results/ 2019-02-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/038/results/ 2019-02-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/040/results/ 2019-02-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/043/results/ 2019-02-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/047/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/ From Nick.Gasson at arm.com Mon Feb 18 07:36:20 2019 From: Nick.Gasson at arm.com (Nick Gasson (Arm Technology China)) Date: Mon, 18 Feb 2019 07:36:20 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: <976b890a-79e6-e8d1-e516-97e15bdb6658@redhat.com> References: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com> <1fd9aa7f-c5f5-80ef-dd47-73756a318d31@redhat.com> <068399ec-fbb8-b881-7ea2-1b684a42652a@redhat.com> <976b890a-79e6-e8d1-e516-97e15bdb6658@redhat.com> Message-ID: <6e69e83a-3b9b-2dc0-e769-29d84b99ba13@arm.com> Hi Andrew, Please take a look at this updated patch: http://cr.openjdk.java.net/~ngasson/8209413/webrev.03/ It contains your suggested change below, as well as an extra check in the AARCH64Frame two-argument constructor that the PC from SP[-1] is valid. Also changed SharedRuntime::generate_native_wrapper and TemplateInterpreterGenerator::generate_native_entry to save an accurate return PC in the frame anchor. There's a FIXME in set_last_Java_frame like this: } else { // FIXME: This is almost never correct. We should delete all // cases of set_last_Java_frame with last_java_pc=NULL and use the // correct return address instead. adr(scratch, pc()); } Should we do this now? There's only two places I can see: StubGenerator::generate_throw_exception and the set_last_Java_frame overload that takes a Label. Thanks, Nick On 12/02/2019 23:32, Andrew Haley wrote: > What's the status of this? Are you still looking at it? > > On 2/7/19 3:39 PM, Andrew Haley wrote: >> On 2/7/19 2:36 PM, Nick Gasson (Arm Technology China) wrote: >>> >>> Yeah I tried this method too (see the end of my first email). It >>> works fine except the PC is off by a few instructions. That can be >>> fixed quite easily though if required, and it always points into the >>> right method. >> >> We should fix those few cases. >> >>> I ended up doing the stack scanning thing because as far as I can >>> tell that constructor is only used when we need to find the return >>> PC from a native frame >> >> I don't think that ever happens. In the code I modified we know that >> we have a good PC in the frame anchor. In the cases where we have a >> native frame on the stack and nothing in the frame anchor we give >> up. At least, I can see no counter-cases. >> >>> (I might have been wrong about this), so I couldn't see how it would >>> ever get the right value. If we check vm.isJavaPCDbg() before we use >>> the SP[-1] value that will make the remaining callers a bit safer >>> (and set this.pc to null otherwise). >> >> That would be safe, for sure. >> > > From aph at redhat.com Mon Feb 18 09:22:37 2019 From: aph at redhat.com (Andrew Haley) Date: Mon, 18 Feb 2019 09:22:37 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: <6e69e83a-3b9b-2dc0-e769-29d84b99ba13@arm.com> References: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com> <1fd9aa7f-c5f5-80ef-dd47-73756a318d31@redhat.com> <068399ec-fbb8-b881-7ea2-1b684a42652a@redhat.com> <976b890a-79e6-e8d1-e516-97e15bdb6658@redhat.com> <6e69e83a-3b9b-2dc0-e769-29d84b99ba13@arm.com> Message-ID: On 2/18/19 7:36 AM, Nick Gasson (Arm Technology China) wrote: > http://cr.openjdk.java.net/~ngasson/8209413/webrev.03/ > > It contains your suggested change below, as well as an extra check in > the AARCH64Frame two-argument constructor that the PC from SP[-1] is > valid. Also changed SharedRuntime::generate_native_wrapper and > TemplateInterpreterGenerator::generate_native_entry to save an accurate > return PC in the frame anchor. That looks right, thanks. OK. > There's a FIXME in set_last_Java_frame like this: > > } else { > // FIXME: This is almost never correct. We should delete all > // cases of set_last_Java_frame with last_java_pc=NULL and use the > // correct return address instead. > adr(scratch, pc()); > } > > Should we do this now? There's only two places I can see: > StubGenerator::generate_throw_exception and the set_last_Java_frame > overload that takes a Label. I hate cruft like this, but it's not actually a bug, and any change in this delicate area has a non-zero probability of breaking something. On the other hand, it would be a very low-risk change. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Mon Feb 18 23:36:16 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Mon, 18 Feb 2019 23:36:16 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <1088288599.2206.1550532977358.JavaMail.jenkins@dc828b94788c> 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/049/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/jan/09 pass: 5,564; fail: 20; error: 1; not run: 93 Build 1: aarch64/2019/jan/11 pass: 5,504; fail: 5; error: 1; not run: 93 Build 2: aarch64/2019/jan/16 pass: 5,511; fail: 6; error: 2; not run: 93 Build 3: aarch64/2019/jan/21 pass: 5,514; fail: 8; error: 1; not run: 93 Build 4: aarch64/2019/jan/24 pass: 5,520; fail: 5; error: 1; not run: 93 Build 5: aarch64/2019/jan/25 pass: 5,533; fail: 6; error: 1; not run: 93 Build 6: aarch64/2019/jan/28 pass: 5,533; fail: 6; error: 1; not run: 93 Build 7: aarch64/2019/jan/30 pass: 5,527; fail: 5; error: 2; not run: 93 Build 8: aarch64/2019/feb/04 pass: 5,527; fail: 7; error: 2; not run: 93 Build 9: aarch64/2019/feb/06 pass: 5,532; fail: 4; error: 1; not run: 93 Build 10: aarch64/2019/feb/08 pass: 5,519; fail: 19; error: 2; not run: 93 Build 11: aarch64/2019/feb/11 pass: 5,527; fail: 11; error: 2; not run: 93 Build 12: aarch64/2019/feb/13 pass: 5,537; fail: 4; not run: 93 Build 13: aarch64/2019/feb/15 pass: 5,538; fail: 4; not run: 93 Build 14: aarch64/2019/feb/18 pass: 5,538; fail: 4; not run: 93 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/09 pass: 8,545; fail: 483; error: 15 Build 1: aarch64/2019/jan/11 pass: 8,501; fail: 518; error: 25 Build 2: aarch64/2019/jan/16 pass: 8,553; fail: 480; error: 15 Build 3: aarch64/2019/jan/21 pass: 8,521; fail: 511; error: 20 Build 4: aarch64/2019/jan/24 pass: 8,533; fail: 503; error: 18 Build 5: aarch64/2019/jan/25 pass: 8,538; fail: 500; error: 20 Build 6: aarch64/2019/jan/28 pass: 8,543; fail: 496; error: 20 Build 7: aarch64/2019/jan/30 pass: 8,541; fail: 503; error: 19 Build 8: aarch64/2019/feb/04 pass: 8,539; fail: 506; error: 18 Build 9: aarch64/2019/feb/06 pass: 8,537; fail: 499; error: 27 Build 10: aarch64/2019/feb/08 pass: 8,530; fail: 515; error: 23 Build 11: aarch64/2019/feb/11 pass: 8,559; fail: 490; error: 15 Build 12: aarch64/2019/feb/13 pass: 8,534; fail: 512; error: 18 Build 13: aarch64/2019/feb/15 pass: 8,556; fail: 492; error: 16 Build 14: aarch64/2019/feb/18 pass: 8,530; fail: 514; error: 20 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/09 pass: 3,993 Build 1: aarch64/2019/jan/11 pass: 3,991 Build 2: aarch64/2019/jan/16 pass: 3,993 Build 3: aarch64/2019/jan/21 pass: 3,993; fail: 1 Build 4: aarch64/2019/jan/24 pass: 3,993; fail: 1 Build 5: aarch64/2019/jan/25 pass: 3,993; fail: 1 Build 6: aarch64/2019/jan/28 pass: 3,994; fail: 1 Build 7: aarch64/2019/jan/30 pass: 3,994; fail: 1 Build 8: aarch64/2019/feb/04 pass: 3,994; fail: 1 Build 9: aarch64/2019/feb/06 pass: 3,994; fail: 1 Build 10: aarch64/2019/feb/08 pass: 3,994; fail: 1 Build 11: aarch64/2019/feb/11 pass: 3,994; fail: 1 Build 12: aarch64/2019/feb/13 pass: 3,994; fail: 1 Build 13: aarch64/2019/feb/15 pass: 3,995 Build 14: aarch64/2019/feb/18 pass: 3,996 ------------------------------------------------------------------------------- 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.80x Relative performance: Server critical-jOPS (nc): 9.55x 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: 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/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-10 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/009/results/ 2019-01-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/011/results/ 2019-01-16 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/016/results/ 2019-01-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/021/results/ 2019-01-24 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/024/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/028/results/ 2019-01-31 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/030/results/ 2019-02-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/035/results/ 2019-02-07 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/037/results/ 2019-02-09 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/039/results/ 2019-02-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/042/results/ 2019-02-14 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/044/results/ 2019-02-15 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/046/results/ 2019-02-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/049/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 Tue Feb 19 06:21:49 2019 From: Nick.Gasson at arm.com (Nick Gasson (Arm Technology China)) Date: Tue, 19 Feb 2019 06:21:49 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: References: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com> <1fd9aa7f-c5f5-80ef-dd47-73756a318d31@redhat.com> <068399ec-fbb8-b881-7ea2-1b684a42652a@redhat.com> <976b890a-79e6-e8d1-e516-97e15bdb6658@redhat.com> <6e69e83a-3b9b-2dc0-e769-29d84b99ba13@arm.com> Message-ID: <64be136c-e3a1-27e4-3ca8-c8b1026cea3c@arm.com> On 18/02/2019 17:22, Andrew Haley wrote: >> >> Should we do this now? There's only two places I can see: >> StubGenerator::generate_throw_exception and the set_last_Java_frame >> overload that takes a Label. > > I hate cruft like this, but it's not actually a bug, and any change in this > delicate area has a non-zero probability of breaking something. On the other > hand, it would be a very low-risk change. > How about this: http://cr.openjdk.java.net/~ngasson/8209413/webrev.04/ I changed the two places that currently pass NULL to pass pc() instead and changed the FIXME into an assert. I think the result is much cleaner with no functional change. Ran jtreg with assertions enabled. Thanks, Nick From Nick.Gasson at arm.com Tue Feb 19 07:54:22 2019 From: Nick.Gasson at arm.com (Nick Gasson (Arm Technology China)) Date: Tue, 19 Feb 2019 07:54:22 +0000 Subject: [aarch64-port-dev ] Panama foreign on AArch64? Message-ID: Hi, The panama foreign branch currently only has an implementation for x86. Is anyone working on or planning to work on an AArch64 port? If not, is this something we (Arm) could usefully contribute to now, or would it be better to wait until the architecture-specific interfaces are more finalised? Thanks, Nick From dms at samersoff.net Tue Feb 19 09:25:26 2019 From: dms at samersoff.net (Dmitry Samersoff) Date: Tue, 19 Feb 2019 12:25:26 +0300 Subject: [aarch64-port-dev ] Panama foreign on AArch64? In-Reply-To: References: Message-ID: <16063f5f-4932-94a4-778d-6a1054a166f8@samersoff.net> Nick, We plan to start working on it in the nearest future and any help and advices is much appreciated. -Dmitry On 19.02.2019 10:54, Nick Gasson (Arm Technology China) wrote: > Hi, > > The panama foreign branch currently only has an implementation for x86. > Is anyone working on or planning to work on an AArch64 port? If not, is > this something we (Arm) could usefully contribute to now, or would it be > better to wait until the architecture-specific interfaces are more > finalised? > > Thanks, > Nick > From aph at redhat.com Tue Feb 19 09:43:19 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 19 Feb 2019 09:43:19 +0000 Subject: [aarch64-port-dev ] RFR: 8209413: AArch64: NPE in clhsdb jstack command In-Reply-To: <64be136c-e3a1-27e4-3ca8-c8b1026cea3c@arm.com> References: <48554800-8c44-1756-e372-59e5f1babe5f@redhat.com> <100cc6ef-cab1-4ee1-3ab8-8186f9d898e8@redhat.com> <1fd9aa7f-c5f5-80ef-dd47-73756a318d31@redhat.com> <068399ec-fbb8-b881-7ea2-1b684a42652a@redhat.com> <976b890a-79e6-e8d1-e516-97e15bdb6658@redhat.com> <6e69e83a-3b9b-2dc0-e769-29d84b99ba13@arm.com> <64be136c-e3a1-27e4-3ca8-c8b1026cea3c@arm.com> Message-ID: <8cff43f3-73ee-35b6-8d8d-0549276550da@redhat.com> On 2/19/19 6:21 AM, Nick Gasson (Arm Technology China) wrote: > How about this: > > http://cr.openjdk.java.net/~ngasson/8209413/webrev.04/ > > I changed the two places that currently pass NULL to pass pc() instead > and changed the FIXME into an assert. I think the result is much cleaner > with no functional change. Ran jtreg with assertions enabled. That's fine, thanks. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From bsrbnd at gmail.com Wed Feb 6 11:21:21 2019 From: bsrbnd at gmail.com (B. Blaser) Date: Wed, 6 Feb 2019 12:21:21 +0100 Subject: [aarch64-port-dev ] RFR(M): 8212043: Add floating-point Math.min/max intrinsics In-Reply-To: <6332babc-f2c9-1478-42f4-2e2e0f8ae6a7@redhat.com> References: <1e7af2c4-8610-2ee9-9955-298ffb715fa7@redhat.com> <06048878-effe-7d24-bb87-b140e662aeb8@redhat.com> <7c97719b-e83a-ba40-43a3-8cec8273df1c@redhat.com> <3df16666-a10b-41bb-7439-b967e1d76735@redhat.com> <4a10fa17-197b-2da9-7890-9544a407832f@redhat.com> <02FCFB8477C4EF43A2AD8E0C60F3DA2BB1A579A7@FMSMSX126.amr.corp.intel.com> <6332babc-f2c9-1478-42f4-2e2e0f8ae6a7@redhat.com> Message-ID: Hi Andrew, On Wed, 6 Feb 2019 at 11:47, Andrew Dinn wrote: > > Hi Bernard, > > I prefer to create a separate issue to cover addition this test so that > it does not get wrapped up with the review of the Intel implementation > which is really a separate task. I have created JDK-8218550 for this > purpose. All right, I'll let you push the test case. We are currently discussing about its parameters on the Intel review thread, you might be interested in giving your opinion on this. Regards, Bernard From maurizio.cimadamore at oracle.com Tue Feb 19 11:39:05 2019 From: maurizio.cimadamore at oracle.com (Maurizio Cimadamore) Date: Tue, 19 Feb 2019 11:39:05 +0000 Subject: [aarch64-port-dev ] Panama foreign on AArch64? In-Reply-To: References: Message-ID: <539341e2-9fbe-1e11-309b-c50834dc198e@oracle.com> Hi Nick, overall, the ABI interface is relatively stable: http://hg.openjdk.java.net/panama/dev/file/6b1f1666f5f6/src/java.base/share/classes/jdk/internal/foreign/abi/SystemABI.java This is the interface used by the Panama binder for all system-specific stuff - it is conceptually easy, in that it takes a description of a function (e.g. native layouts, Java carriers) and return a MethodHandle that the client can use to make the call. A similar strategy is used for creating callbacks. Panama supports two ABI implementation for now: * SysVABI (Linux): http://hg.openjdk.java.net/panama/dev/file/6b1f1666f5f6/src/java.base/share/classes/jdk/internal/foreign/abi/x64/sysv/SysVx64ABI.java * Windows ABI: http://hg.openjdk.java.net/panama/dev/file/6b1f1666f5f6/src/java.base/share/classes/jdk/internal/foreign/abi/x64/windows/Windowsx64ABI.java Within each ABI implementation, there is a certain degree of freedom on how the method handles are generated - for instance, Linux supports two MH strategies: universal and direct invoker; Windows has only the universal invoker one. We are also working on an alternate backend, called linkToNative - which will eventually obsolete the Linux direct invoker - and make these optimizations more portable across the board. So, if you are looking to add ARM support, I'd suggest looking at what's been done for Windows: that is port the universal invoker/upcall implementation to ARM - that should be enough to be able to run the binder on ARM. When, in the future, linkToNative will land on the main 'foreign' branch, some tweaks will probably be needed in order to adjust the linkToNative logic to ARM - but looking at the work done for Windows by Jorn [1, 2], these adjustments seem to be rather small. Let me know if you need extra pointers. I think this would be a very valuable experiment, as it might point out areas where we made incorrect, platform-dependent assumptions. Cheers Maurizio [1] - https://mail.openjdk.java.net/pipermail/panama-dev/2019-February/004271.html [2] - https://mail.openjdk.java.net/pipermail/panama-dev/2019-February/004199.html On 19/02/2019 07:54, Nick Gasson (Arm Technology China) wrote: > Hi, > > The panama foreign branch currently only has an implementation for x86. > Is anyone working on or planning to work on an AArch64 port? If not, is > this something we (Arm) could usefully contribute to now, or would it be > better to wait until the architecture-specific interfaces are more > finalised? > > Thanks, > Nick From jbvernee at xs4all.nl Tue Feb 19 12:25:48 2019 From: jbvernee at xs4all.nl (Jorn Vernee) Date: Tue, 19 Feb 2019 13:25:48 +0100 Subject: [aarch64-port-dev ] Panama foreign on AArch64? In-Reply-To: <539341e2-9fbe-1e11-309b-c50834dc198e@oracle.com> References: <539341e2-9fbe-1e11-309b-c50834dc198e@oracle.com> Message-ID: Maurizio Cimadamore schreef op 2019-02-19 12:39: > Hi Nick, > overall, the ABI interface is relatively stable: > > http://hg.openjdk.java.net/panama/dev/file/6b1f1666f5f6/src/java.base/share/classes/jdk/internal/foreign/abi/SystemABI.java > > This is the interface used by the Panama binder for all > system-specific stuff - it is conceptually easy, in that it takes a > description of a function (e.g. native layouts, Java carriers) and > return a MethodHandle that the client can use to make the call. A > similar strategy is used for creating callbacks. > > Panama supports two ABI implementation for now: > > * SysVABI (Linux): > http://hg.openjdk.java.net/panama/dev/file/6b1f1666f5f6/src/java.base/share/classes/jdk/internal/foreign/abi/x64/sysv/SysVx64ABI.java > > * Windows ABI: > http://hg.openjdk.java.net/panama/dev/file/6b1f1666f5f6/src/java.base/share/classes/jdk/internal/foreign/abi/x64/windows/Windowsx64ABI.java > > Within each ABI implementation, there is a certain degree of freedom > on how the method handles are generated - for instance, Linux supports > two MH strategies: universal and direct invoker; Windows has only the > universal invoker one. > > We are also working on an alternate backend, called linkToNative - > which will eventually obsolete the Linux direct invoker - and make > these optimizations more portable across the board. > > So, if you are looking to add ARM support, I'd suggest looking at > what's been done for Windows: that is port the universal > invoker/upcall implementation to ARM - that should be enough to be > able to run the binder on ARM. When, in the future, linkToNative will > land on the main 'foreign' branch, some tweaks will probably be needed > in order to adjust the linkToNative logic to ARM - but looking at the > work done for Windows by Jorn [1, 2], these adjustments seem to be > rather small. The changes were small because everything is mostly the same between the SysV and Windows ABIs, so I only had to insert some compiler switches with code to handle the Windows quirks. I'm not really well-versed in the AArach64 architecture or ABI, but at least the build system keeps x86 and AArach64 separate, so the changes will probably be a little more extensive to make another architecture work. I would suggest starting with the UniversalNativeInoker/UniversalUpcallHandler backend, since that is broadly applicable, and has a little more debug code written for it already. It's also not certain the Direct backend would work for AArach64, since it relies on a SysV ABI trait, that for instance doesn't exist in the Windows ABI. You could start by looking at src/hotspot/share/prims/universalNativeInvoker.cpp and src/hotspot/cpu/x86/universalNativeInvoker_x86.cpp and try to replicate the functionality in the latter for AArach64. On the Java side you'd have to start probably by looking at one of the src/java.base/share/classes/jdk/internal/foreign/abi/x64/ folders, and replicating the functionality for AArach64. Generally, anything in the jdk.internal.foreign.abi package should be interesting to look at for a port. The idea of UniversalNativeInvoker is that we stack all the unboxed arguments into a long[], and then provide a shuffle recipe to put these arguments into registers on the native side. The shuffle recipe is derived from a CallingSequence, which is generated internally by the particular ABI implementations. The idea of UniversalUpcallHandler is that we create a native stub that forwards it's arguments as pointers to a java function, then give the native code a pointer to the generated stub. On the java side arguments are boxed from these pointer, and a target MethodHandle is called. Cheers, Jorn > Let me know if you need extra pointers. I think this would be a very > valuable experiment, as it might point out areas where we made > incorrect, platform-dependent assumptions. > > Cheers > Maurizio > > > [1] - > https://mail.openjdk.java.net/pipermail/panama-dev/2019-February/004271.html > [2] - > https://mail.openjdk.java.net/pipermail/panama-dev/2019-February/004199.html > > > On 19/02/2019 07:54, Nick Gasson (Arm Technology China) wrote: >> Hi, >> >> The panama foreign branch currently only has an implementation for >> x86. >> Is anyone working on or planning to work on an AArch64 port? If not, >> is >> this something we (Arm) could usefully contribute to now, or would it >> be >> better to wait until the architecture-specific interfaces are more >> finalised? >> >> Thanks, >> Nick From ci_notify at linaro.org Wed Feb 20 02:54:21 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Wed, 20 Feb 2019 02:54:21 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 11u on AArch64 Message-ID: <1206884827.2439.1550631262135.JavaMail.jenkins@dc828b94788c> 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/050/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 5,705; fail: 9; not run: 11,618 Build 1: aarch64/2019/jan/12 pass: 5,705; fail: 9; not run: 11,618 Build 2: aarch64/2019/jan/15 pass: 5,705; fail: 9; not run: 11,618 Build 3: aarch64/2019/jan/17 pass: 5,709; fail: 9; not run: 11,618 Build 4: aarch64/2019/jan/22 pass: 5,709; fail: 9; not run: 11,618 Build 5: aarch64/2019/jan/24 pass: 5,708; fail: 10; not run: 11,618 Build 6: aarch64/2019/jan/29 pass: 5,709; fail: 9; not run: 11,618 Build 7: aarch64/2019/jan/31 pass: 5,707; fail: 11; not run: 11,618 Build 8: aarch64/2019/feb/02 pass: 5,708; fail: 10; not run: 11,618 Build 9: aarch64/2019/feb/07 pass: 5,710; fail: 9; not run: 11,618 Build 10: aarch64/2019/feb/09 pass: 5,710; fail: 9; not run: 11,618 Build 11: aarch64/2019/feb/12 pass: 5,709; fail: 10; not run: 11,618 Build 12: aarch64/2019/feb/16 pass: 5,713; fail: 10; not run: 11,618 Build 13: aarch64/2019/feb/19 pass: 5,715; fail: 10; not run: 11,618 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 8,344; fail: 522; error: 29 Build 1: aarch64/2019/jan/12 pass: 8,376; fail: 496; error: 23 Build 2: aarch64/2019/jan/15 pass: 8,353; fail: 510; error: 32 Build 3: aarch64/2019/jan/17 pass: 8,386; fail: 493; error: 19 Build 4: aarch64/2019/jan/22 pass: 8,369; fail: 506; error: 23 Build 5: aarch64/2019/jan/24 pass: 8,366; fail: 507; error: 25 Build 6: aarch64/2019/jan/29 pass: 8,353; fail: 524; error: 22 Build 7: aarch64/2019/jan/31 pass: 8,372; fail: 502; error: 25 Build 8: aarch64/2019/feb/02 pass: 8,378; fail: 501; error: 21 Build 9: aarch64/2019/feb/07 pass: 8,364; fail: 507; error: 29 Build 10: aarch64/2019/feb/09 pass: 8,354; fail: 523; error: 23 Build 11: aarch64/2019/feb/12 pass: 8,358; fail: 519; error: 24 Build 12: aarch64/2019/feb/16 pass: 8,356; fail: 520; error: 25 Build 13: aarch64/2019/feb/19 pass: 8,375; fail: 506; error: 24 4 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 3,903 Build 1: aarch64/2019/jan/12 pass: 3,903 Build 2: aarch64/2019/jan/15 pass: 3,903 Build 3: aarch64/2019/jan/17 pass: 3,903 Build 4: aarch64/2019/jan/22 pass: 3,903 Build 5: aarch64/2019/jan/24 pass: 3,903 Build 6: aarch64/2019/jan/29 pass: 3,903 Build 7: aarch64/2019/jan/31 pass: 3,903 Build 8: aarch64/2019/feb/02 pass: 3,903 Build 9: aarch64/2019/feb/07 pass: 3,903 Build 10: aarch64/2019/feb/09 pass: 3,903 Build 11: aarch64/2019/feb/12 pass: 3,903 Build 12: aarch64/2019/feb/16 pass: 3,903 Build 13: aarch64/2019/feb/19 pass: 3,903 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.29x Relative performance: Server critical-jOPS (nc): 7.53x 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-01-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/010/results/ 2019-01-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/012/results/ 2019-01-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/015/results/ 2019-01-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/017/results/ 2019-01-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/022/results/ 2019-01-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/024/results/ 2019-01-30 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/031/results/ 2019-02-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/033/results/ 2019-02-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/038/results/ 2019-02-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/040/results/ 2019-02-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/043/results/ 2019-02-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/047/results/ 2019-02-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/050/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 Thu Feb 21 00:21:54 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Thu, 21 Feb 2019 00:21:54 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <1826352840.2755.1550708514844.JavaMail.jenkins@dc828b94788c> 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/051/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/jan/11 pass: 5,504; fail: 5; error: 1; not run: 93 Build 1: aarch64/2019/jan/16 pass: 5,511; fail: 6; error: 2; not run: 93 Build 2: aarch64/2019/jan/21 pass: 5,514; fail: 8; error: 1; not run: 93 Build 3: aarch64/2019/jan/24 pass: 5,520; fail: 5; error: 1; not run: 93 Build 4: aarch64/2019/jan/25 pass: 5,533; fail: 6; error: 1; not run: 93 Build 5: aarch64/2019/jan/28 pass: 5,533; fail: 6; error: 1; not run: 93 Build 6: aarch64/2019/jan/30 pass: 5,527; fail: 5; error: 2; not run: 93 Build 7: aarch64/2019/feb/04 pass: 5,527; fail: 7; error: 2; not run: 93 Build 8: aarch64/2019/feb/06 pass: 5,532; fail: 4; error: 1; not run: 93 Build 9: aarch64/2019/feb/08 pass: 5,519; fail: 19; error: 2; not run: 93 Build 10: aarch64/2019/feb/11 pass: 5,527; fail: 11; error: 2; not run: 93 Build 11: aarch64/2019/feb/13 pass: 5,537; fail: 4; not run: 93 Build 12: aarch64/2019/feb/15 pass: 5,538; fail: 4; not run: 93 Build 13: aarch64/2019/feb/18 pass: 5,538; fail: 4; not run: 93 Build 14: aarch64/2019/feb/20 pass: 5,539; fail: 4; not run: 93 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/11 pass: 8,501; fail: 518; error: 25 Build 1: aarch64/2019/jan/16 pass: 8,553; fail: 480; error: 15 Build 2: aarch64/2019/jan/21 pass: 8,521; fail: 511; error: 20 Build 3: aarch64/2019/jan/24 pass: 8,533; fail: 503; error: 18 Build 4: aarch64/2019/jan/25 pass: 8,538; fail: 500; error: 20 Build 5: aarch64/2019/jan/28 pass: 8,543; fail: 496; error: 20 Build 6: aarch64/2019/jan/30 pass: 8,541; fail: 503; error: 19 Build 7: aarch64/2019/feb/04 pass: 8,539; fail: 506; error: 18 Build 8: aarch64/2019/feb/06 pass: 8,537; fail: 499; error: 27 Build 9: aarch64/2019/feb/08 pass: 8,530; fail: 515; error: 23 Build 10: aarch64/2019/feb/11 pass: 8,559; fail: 490; error: 15 Build 11: aarch64/2019/feb/13 pass: 8,534; fail: 512; error: 18 Build 12: aarch64/2019/feb/15 pass: 8,556; fail: 492; error: 16 Build 13: aarch64/2019/feb/18 pass: 8,530; fail: 514; error: 20 Build 14: aarch64/2019/feb/20 pass: 8,550; fail: 498; error: 17 3 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/11 pass: 3,991 Build 1: aarch64/2019/jan/16 pass: 3,993 Build 2: aarch64/2019/jan/21 pass: 3,993; fail: 1 Build 3: aarch64/2019/jan/24 pass: 3,993; fail: 1 Build 4: aarch64/2019/jan/25 pass: 3,993; fail: 1 Build 5: aarch64/2019/jan/28 pass: 3,994; fail: 1 Build 6: aarch64/2019/jan/30 pass: 3,994; fail: 1 Build 7: aarch64/2019/feb/04 pass: 3,994; fail: 1 Build 8: aarch64/2019/feb/06 pass: 3,994; fail: 1 Build 9: aarch64/2019/feb/08 pass: 3,994; fail: 1 Build 10: aarch64/2019/feb/11 pass: 3,994; fail: 1 Build 11: aarch64/2019/feb/13 pass: 3,994; fail: 1 Build 12: aarch64/2019/feb/15 pass: 3,995 Build 13: aarch64/2019/feb/18 pass: 3,996 Build 14: aarch64/2019/feb/20 pass: 3,996 ------------------------------------------------------------------------------- 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.88x Relative performance: Server critical-jOPS (nc): 9.43x 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-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/011/results/ 2019-01-16 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/016/results/ 2019-01-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/021/results/ 2019-01-24 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/024/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/028/results/ 2019-01-31 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/030/results/ 2019-02-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/035/results/ 2019-02-07 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/037/results/ 2019-02-09 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/039/results/ 2019-02-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/042/results/ 2019-02-14 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/044/results/ 2019-02-15 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/046/results/ 2019-02-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/049/results/ 2019-02-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/051/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From dmitrij.pochepko at bell-sw.com Thu Feb 21 15:26:44 2019 From: dmitrij.pochepko at bell-sw.com (Dmitrij Pochepko) Date: Thu, 21 Feb 2019 18:26:44 +0300 Subject: [aarch64-port-dev ] 8218966: AArch64: String.compareTo() can read memory after string Message-ID: Hi all, Please review a fix for "8218966: AArch64: String.compareTo() can read memory after string". bug: https://bugs.openjdk.java.net/browse/JDK-8218966 webrev: http://cr.openjdk.java.net/~dpochepk/8218966/webrev/ Intrinsic implementation returns wrong value in rare cases for strings longer than 72 characters. Changes: - Different encodings case. Small 16-characters loop and post-loop code are re-organized to stop at string end. Post-loop now also uses compare_string_16_x_LU() to avoid code duplication. - Changed calculation of prefetchLoopExitCondition. It might be incorrect in case when SoftwarePrefetchHintDistance was set to non-default small value. - Same encoding case. Moved loop counter update out of prefetch block. It might miss end-of-string check when prefetch is disabled, with memory after string being read. - Added 2 tests. They are quite similar but TestStringCompareToSameLength compares strings of same length, and TestStringCompareToDifferentLength is for different lengths. Tests cover 8218966 case. And also they cover different parts of intrinsic, taking into account conditions in the implementation and possible SoftwarePrefetchHintDistance values. Testing: Existing jtreg and jck tests were not able to detect 8218966 case. But they pass with the fix applied. Newly added jtreg tests can detect the issue and potential problems in case of changes in the implementation. The following testing was performed: - jck with default vm flags - jck with -Xcomp -XX:-TieredCompilation - hotspot jtreg tests (including new tests): compiler/*, runtime/*, gc/* with default vm flags - hotspot jtreg tests (including new tests): compiler/*, runtime/*, gc/* with -Xcomp -XX:-TieredCompilation - jdk jtreg tier1-3 tests with default vm flags - jdk jtreg tier1-3 tests with -Xcomp -XX:-TieredCompilation No regressions were found. I'd like to thank Pengfei Li (Pengfei.Li at arm.com) for pre-review and additional testing. I'm also about to send separate additional webrev with compareTo intrinsic documentation and maintenance-related improvements as separate enhancement. Thanks, Dmitrij From dmitrij.pochepko at bell-sw.com Thu Feb 21 20:28:40 2019 From: dmitrij.pochepko at bell-sw.com (Dmitrij Pochepko) Date: Thu, 21 Feb 2019 23:28:40 +0300 Subject: [aarch64-port-dev ] RFR: 8218748: AARCH64: String::compareTo intrinsic documentation and maintenance improvement Message-ID: Hi all. Please review an enhancement change "8218748: AARCH64: String::compareTo intrinsic documentation and maintenance improvement". RFE: https://bugs.openjdk.java.net/browse/JDK-8218748 webrev: http://cr.openjdk.java.net/~dpochepk/8218748/webrev/ Changes: - Added documentation for compareTo implementation. - Removed duplicated code and using existing code instead. -- compare_string_16_bytes_same is used for tail handling in generate_compare_long_string_same_encoding . -- DIFF block code is reused for DIFF2 block in generate_compare_long_string_same_encoding. - Registers and labels are partially renamed to better reflect code actions. This patch is dependent on JDK-8218966 and should be applied on top of it. Testing: - jck - hotspot jtreg compiler/*, runtime/* and gc/* tests. Including AARCH64-implementation-specific compareTo tests introduced in JDK-8218966 fix - jdk jtreg tier1-3 tests No regressions were found. I'd like to thank Pengfei Li (Pengfei.Li at arm.com) for pre-review and additional testing. Thanks, Dmitrij From patrick at os.amperecomputing.com Fri Feb 22 04:04:39 2019 From: patrick at os.amperecomputing.com (Patrick Zhang) Date: Fri, 22 Feb 2019 04:04:39 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: <1880b8f1-7563-f50e-aef9-5c6032672844@redhat.com> References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> <1880b8f1-7563-f50e-aef9-5c6032672844@redhat.com> Message-ID: Hi Andrew and Yangfei, Perhaps TemplateTable::fast_storefield needs the additional " | MacroAssembler::LoadStore" as well, please double check, thanks. http://hg.openjdk.java.net/jdk/jdk/file/f41793b5b83f/src/hotspot/cpu/aarch64/templateTable_aarch64.cpp#l2984 Regards Patrick -----Original Message----- From: aarch64-port-dev On Behalf Of Andrew Haley Sent: Tuesday, February 12, 2019 5:29 PM To: Yangfei (Felix) ; aarch64-port-dev at openjdk.java.net Cc: Lun Liu Subject: Re: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? On 2/12/19 9:05 AM, Yangfei (Felix) wrote: > This is aarch64-specific and is supposed to be merged into: aarch64-port/jdk8u-shenandoah and aarch64-port/jdk8u repos. > > Do we still need to send this to the 8u list ? If true, should I simply CC to that list? Sorry, of course. No, don't post to 8u. Please forget I said that! :-) Only halfway down my first cup of coffee... -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Fri Feb 22 09:01:17 2019 From: aph at redhat.com (Andrew Haley) Date: Fri, 22 Feb 2019 09:01:17 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> <1880b8f1-7563-f50e-aef9-5c6032672844@redhat.com> Message-ID: On 2/22/19 4:04 AM, Patrick Zhang wrote: > Perhaps TemplateTable::fast_storefield needs the additional " | MacroAssembler::LoadStore" as well, please double check, thanks. > http://hg.openjdk.java.net/jdk/jdk/file/f41793b5b83f/src/hotspot/cpu/aarch64/templateTable_aarch64.cpp#l2984 Yes. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Fri Feb 22 09:01:46 2019 From: aph at redhat.com (Andrew Haley) Date: Fri, 22 Feb 2019 09:01:46 +0000 Subject: [aarch64-port-dev ] RFR: 8218748: AARCH64: String::compareTo intrinsic documentation and maintenance improvement In-Reply-To: References: Message-ID: On 2/21/19 8:28 PM, Dmitrij Pochepko wrote: > Testing: > - jck > - hotspot jtreg compiler/*, runtime/* and gc/* tests. Including > AARCH64-implementation-specific compareTo tests introduced in > JDK-8218966 fix > - jdk jtreg tier1-3 tests > > No regressions were found. I'm investigating, thanks. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From Nick.Gasson at arm.com Fri Feb 22 10:06:43 2019 From: Nick.Gasson at arm.com (Nick Gasson (Arm Technology China)) Date: Fri, 22 Feb 2019 10:06:43 +0000 Subject: [aarch64-port-dev ] Panama foreign on AArch64? In-Reply-To: <16063f5f-4932-94a4-778d-6a1054a166f8@samersoff.net> References: <16063f5f-4932-94a4-778d-6a1054a166f8@samersoff.net> Message-ID: <5439c03a-21a2-7374-877f-0f977e1e1ba3@arm.com> Hi Dmitry, > We plan to start working on it in the nearest future and any help and > advices is much appreciated. I briefly investigated getting the foreign branch to build on aarch64, by stubbing out the new backend interfaces implemented on x86, and copy/pasting the Java ABI classes. Let me know if you want to collaborate on this or would like us to help with testing, etc. Thanks, Nick > -----Original Message----- > From: aarch64-port-dev On > Behalf Of Dmitry Samersoff > Sent: 19 February 2019 17:25 > To: Nick Gasson (Arm Technology China) ; panama- > dev at openjdk.java.net > Cc: nd ; aarch64-port-dev at openjdk.java.net > Subject: Re: [aarch64-port-dev ] Panama foreign on AArch64? > > Nick, > > We plan to start working on it in the nearest future and any help and > advices is much appreciated. > > -Dmitry > > > On 19.02.2019 10:54, Nick Gasson (Arm Technology China) wrote: > > Hi, > > > > The panama foreign branch currently only has an implementation for x86. > > Is anyone working on or planning to work on an AArch64 port? If not, is > > this something we (Arm) could usefully contribute to now, or would it be > > better to wait until the architecture-specific interfaces are more > > finalised? > > > > Thanks, > > Nick > > From Pengfei.Li at arm.com Fri Feb 22 10:31:22 2019 From: Pengfei.Li at arm.com (Pengfei Li (Arm Technology China)) Date: Fri, 22 Feb 2019 10:31:22 +0000 Subject: [aarch64-port-dev ] RFR: 8218748: AARCH64: String::compareTo intrinsic documentation and maintenance improvement In-Reply-To: References: Message-ID: Hi Dmitrij, > Please review an enhancement change "8218748: AARCH64: > String::compareTo intrinsic documentation and maintenance improvement". > > RFE: https://bugs.openjdk.java.net/browse/JDK-8218748 > webrev: http://cr.openjdk.java.net/~dpochepk/8218748/webrev/ I still see inconsistencies between the original code block and the documentation. e.g. 1) In macroAssembler_aarch64.cpp, the SHORT_LOOP_TAIL block before the SHORT_LAST2 is missing. 2) And also in macro assembler code, after the SHORT_LOOP label: +// endReached = cnt2 == 0; +// if (endReached) goto SHORT_LAST_INIT; --> should it be SHORT_LAST ? So personally, I still prefer to inline the comments with the original code block to avoid this kind of inconsistencies. And it makes us easier to review or maintain the code together with the doc, as we don't need to scroll back and force. I don't know the benefit of making the code documentation as a separate part. What's your opinion, Andrew Haley? -- Thanks, Pengfei From patrick at os.amperecomputing.com Fri Feb 22 10:54:35 2019 From: patrick at os.amperecomputing.com (Patrick Zhang) Date: Fri, 22 Feb 2019 10:54:35 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> <1880b8f1-7563-f50e-aef9-5c6032672844@redhat.com> Message-ID: Thanks for reviewed this, Andrew. Hi Felix, Could you please help sponsor this extra patch as well? It is quite similar as your previous one. I found JDK-8218185 has been resolved and the subject was for "putfield_or_static". Probably a new Jira ticket is needed for this "fast_storefield" and two issues are closely corelated. I have no commit permission so appreciate your help very much! (both jdk/jdk and jdk8u) Regarding the tests, I have run jtreg jdk_core and jcstress on my aarch64 platform, no problem found. Please help double check at your side too if possible. Thanks. diff -r 2a78b2963793 src/hotspot/cpu/aarch64/templateTable_aarch64.cpp --- a/src/hotspot/cpu/aarch64/templateTable_aarch64.cpp Wed Feb 13 13:27:17 2019 +0100 +++ b/src/hotspot/cpu/aarch64/templateTable_aarch64.cpp Fri Feb 22 17:18:20 2019 +0800 @@ -2981,7 +2981,7 @@ { Label notVolatile; __ tbz(r3, ConstantPoolCacheEntry::is_volatile_shift, notVolatile); - __ membar(MacroAssembler::StoreStore); + __ membar(MacroAssembler::StoreStore | MacroAssembler::LoadStore); __ bind(notVolatile); } Regards Patrick -----Original Message----- From: Andrew Haley Sent: Friday, February 22, 2019 5:01 PM To: Patrick Zhang ; Yangfei (Felix) Cc: aarch64-port-dev at openjdk.java.net Subject: Re: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? On 2/22/19 4:04 AM, Patrick Zhang wrote: > Perhaps TemplateTable::fast_storefield needs the additional " | MacroAssembler::LoadStore" as well, please double check, thanks. > http://hg.openjdk.java.net/jdk/jdk/file/f41793b5b83f/src/hotspot/cpu/aarch64/templateTable_aarch64.cpp#l2984 Yes. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Fri Feb 22 15:42:19 2019 From: aph at redhat.com (Andrew Haley) Date: Fri, 22 Feb 2019 15:42:19 +0000 Subject: [aarch64-port-dev ] RFR: 8218748: AARCH64: String::compareTo intrinsic documentation and maintenance improvement In-Reply-To: References: Message-ID: <86f91401-b7f6-b634-fef1-b0615b8fcde0@redhat.com> On 2/22/19 10:31 AM, Pengfei Li (Arm Technology China) wrote: > So personally, I still prefer to inline the comments with the > original code block to avoid this kind of inconsistencies. And it > makes us easier to review or maintain the code together with the > doc, as we don't need to scroll back and force. I don't know the > benefit of making the code documentation as a separate part. What's > your opinion, Andrew Haley? I agree with you. There's no harm having both inline and separate. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Fri Feb 22 18:47:30 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 22 Feb 2019 18:47:30 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 12 on AArch64 Message-ID: <2053573145.3145.1550861250662.JavaMail.jenkins@dc828b94788c> 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/jdk12/openjdk-jtreg-nightly-tests/summary/2019/052/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 5,510; fail: 4; error: 1; not run: 93 Build 1: aarch64/2019/jan/25 pass: 5,523; fail: 7; not run: 93 Build 2: aarch64/2019/jan/27 pass: 5,524; fail: 5; error: 1; not run: 93 Build 3: aarch64/2019/jan/29 pass: 5,524; fail: 5; error: 1; not run: 93 Build 4: aarch64/2019/jan/31 pass: 5,518; fail: 5; error: 1; not run: 93 Build 5: aarch64/2019/feb/03 pass: 5,517; fail: 6; error: 1; not run: 93 Build 6: aarch64/2019/feb/05 pass: 5,517; fail: 6; error: 1; not run: 93 Build 7: aarch64/2019/feb/07 pass: 5,518; fail: 6; not run: 93 Build 8: aarch64/2019/feb/09 pass: 5,519; fail: 4; error: 1; not run: 93 Build 9: aarch64/2019/feb/21 pass: 5,518; fail: 5; error: 1; not run: 93 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 8,528; fail: 482; error: 29 Build 1: aarch64/2019/jan/25 pass: 8,522; fail: 491; error: 27 Build 2: aarch64/2019/jan/27 pass: 8,540; fail: 488; error: 12 Build 3: aarch64/2019/jan/29 pass: 8,543; fail: 483; error: 14 Build 4: aarch64/2019/jan/31 pass: 8,530; fail: 491; error: 21 Build 5: aarch64/2019/feb/03 pass: 8,523; fail: 502; error: 17 Build 6: aarch64/2019/feb/05 pass: 8,492; fail: 520; error: 30 Build 7: aarch64/2019/feb/07 pass: 8,499; fail: 521; error: 22 Build 8: aarch64/2019/feb/09 pass: 8,525; fail: 501; error: 16 Build 9: aarch64/2019/feb/21 pass: 8,514; fail: 510; error: 18 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/22 pass: 3,992 Build 1: aarch64/2019/jan/25 pass: 3,992 Build 2: aarch64/2019/jan/27 pass: 3,992 Build 3: aarch64/2019/jan/29 pass: 3,992 Build 4: aarch64/2019/jan/31 pass: 3,992 Build 5: aarch64/2019/feb/03 pass: 3,992 Build 6: aarch64/2019/feb/05 pass: 3,992 Build 7: aarch64/2019/feb/07 pass: 3,992 Build 8: aarch64/2019/feb/09 pass: 3,992 Build 9: aarch64/2019/feb/21 pass: 3,992 Previous results can be found here: http://openjdk.linaro.org/jdk12/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.12x Relative performance: Server critical-jOPS (nc): 8.32x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk12/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/jdk12/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-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/022/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/027/results/ 2019-01-30 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/031/results/ 2019-02-04 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/034/results/ 2019-02-06 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/036/results/ 2019-02-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/038/results/ 2019-02-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/040/results/ 2019-02-22 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/2019/052/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk12/jcstress-nightly-runs/ From ci_notify at linaro.org Fri Feb 22 18:52:29 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Fri, 22 Feb 2019 18:52:29 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 11u on AArch64 Message-ID: <2067775921.3147.1550861549838.JavaMail.jenkins@dc828b94788c> 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/052/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 5,705; fail: 9; not run: 11,618 Build 1: aarch64/2019/jan/12 pass: 5,705; fail: 9; not run: 11,618 Build 2: aarch64/2019/jan/15 pass: 5,705; fail: 9; not run: 11,618 Build 3: aarch64/2019/jan/17 pass: 5,709; fail: 9; not run: 11,618 Build 4: aarch64/2019/jan/22 pass: 5,709; fail: 9; not run: 11,618 Build 5: aarch64/2019/jan/24 pass: 5,708; fail: 10; not run: 11,618 Build 6: aarch64/2019/jan/29 pass: 5,709; fail: 9; not run: 11,618 Build 7: aarch64/2019/jan/31 pass: 5,707; fail: 11; not run: 11,618 Build 8: aarch64/2019/feb/02 pass: 5,708; fail: 10; not run: 11,618 Build 9: aarch64/2019/feb/07 pass: 5,710; fail: 9; not run: 11,618 Build 10: aarch64/2019/feb/09 pass: 5,710; fail: 9; not run: 11,618 Build 11: aarch64/2019/feb/12 pass: 5,709; fail: 10; not run: 11,618 Build 12: aarch64/2019/feb/16 pass: 5,713; fail: 10; not run: 11,618 Build 13: aarch64/2019/feb/19 pass: 5,715; fail: 10; not run: 11,618 Build 14: aarch64/2019/feb/21 pass: 5,714; fail: 11; not run: 11,618 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 8,344; fail: 522; error: 29 Build 1: aarch64/2019/jan/12 pass: 8,376; fail: 496; error: 23 Build 2: aarch64/2019/jan/15 pass: 8,353; fail: 510; error: 32 Build 3: aarch64/2019/jan/17 pass: 8,386; fail: 493; error: 19 Build 4: aarch64/2019/jan/22 pass: 8,369; fail: 506; error: 23 Build 5: aarch64/2019/jan/24 pass: 8,366; fail: 507; error: 25 Build 6: aarch64/2019/jan/29 pass: 8,353; fail: 524; error: 22 Build 7: aarch64/2019/jan/31 pass: 8,372; fail: 502; error: 25 Build 8: aarch64/2019/feb/02 pass: 8,378; fail: 501; error: 21 Build 9: aarch64/2019/feb/07 pass: 8,364; fail: 507; error: 29 Build 10: aarch64/2019/feb/09 pass: 8,354; fail: 523; error: 23 Build 11: aarch64/2019/feb/12 pass: 8,358; fail: 519; error: 24 Build 12: aarch64/2019/feb/16 pass: 8,356; fail: 520; error: 25 Build 13: aarch64/2019/feb/19 pass: 8,375; fail: 506; error: 24 Build 14: aarch64/2019/feb/21 pass: 8,377; fail: 513; error: 22 4 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/10 pass: 3,903 Build 1: aarch64/2019/jan/12 pass: 3,903 Build 2: aarch64/2019/jan/15 pass: 3,903 Build 3: aarch64/2019/jan/17 pass: 3,903 Build 4: aarch64/2019/jan/22 pass: 3,903 Build 5: aarch64/2019/jan/24 pass: 3,903 Build 6: aarch64/2019/jan/29 pass: 3,903 Build 7: aarch64/2019/jan/31 pass: 3,903 Build 8: aarch64/2019/feb/02 pass: 3,903 Build 9: aarch64/2019/feb/07 pass: 3,903 Build 10: aarch64/2019/feb/09 pass: 3,903 Build 11: aarch64/2019/feb/12 pass: 3,903 Build 12: aarch64/2019/feb/16 pass: 3,903 Build 13: aarch64/2019/feb/19 pass: 3,903 Build 14: aarch64/2019/feb/21 pass: 3,904 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.04x Relative performance: Server critical-jOPS (nc): 7.38x 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-01-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/010/results/ 2019-01-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/012/results/ 2019-01-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/015/results/ 2019-01-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/017/results/ 2019-01-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/022/results/ 2019-01-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/024/results/ 2019-01-30 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/031/results/ 2019-02-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/033/results/ 2019-02-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/038/results/ 2019-02-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/040/results/ 2019-02-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/043/results/ 2019-02-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/047/results/ 2019-02-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/050/results/ 2019-02-22 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/052/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/ From fujie at loongson.cn Mon Feb 25 06:28:48 2019 From: fujie at loongson.cn (Jie Fu) Date: Mon, 25 Feb 2019 14:28:48 +0800 Subject: [aarch64-port-dev ] Fwd: RFR (trivial): 8219519: Remove linux_sparc.ad and linux_aarch64.ad In-Reply-To: <900ea372-d9fd-e1fd-051d-3d96e1ec2c66@loongson.cn> References: <900ea372-d9fd-e1fd-051d-3d96e1ec2c66@loongson.cn> Message-ID: <2091db69-de38-37ef-d91e-ec051c1106db@loongson.cn> Forward this mail to aarch64-port-dev. Could you please review it? Thanks a lot. Best regards, Jie -------- Forwarded Message -------- Subject: RFR (trivial): 8219519: Remove linux_sparc.ad and linux_aarch64.ad Date: Thu, 21 Feb 2019 17:35:12 +0800 From: Jie Fu To: hotspot-compiler-dev at openjdk.java.net compiler Hi all, The following two source files are useless for the generation of C2 and should be removed. ?1) ./src/hotspot/os_cpu/linux_sparc/linux_sparc.ad ?2) ./src/hotspot/os_cpu/linux_aarch64/linux_aarch64.ad Bug:??? https://bugs.openjdk.java.net/browse/JDK-8219519 Webrev: http://cr.openjdk.java.net/~jiefu/8219519/webrev.00/ Could you please review it? Thanks a lot. Best regards, Jie From felix.yang at huawei.com Mon Feb 25 07:53:05 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Mon, 25 Feb 2019 07:53:05 +0000 Subject: [aarch64-port-dev ] Fix aarch64-8u jcstress test failure on ARMv8.1 platform Message-ID: Hi, I find that the support for ARMv8.1 LSE atomic operations is different in implementation for aarch64-8u and jdk9+. The corresponding issue is: https://bugs.openjdk.java.net/browse/JDK-8151775 Previously, there were two patches for this issue: v1: http://cr.openjdk.java.net/~enevill/8151775/webrev/ v2: http://cr.openjdk.java.net/~enevill/8151775/webrev.2/ The v1 patch was once rejected by aph in: http://mail.openjdk.java.net/pipermail/hotspot-compiler-dev/2016-March/022001.html So for jdk9+, we are using the v2 patch: http://hg.openjdk.java.net/jdk9/jdk9/hotspot/rev/03fb00b96355 But for aarch64-8u branches, we are still using the v1 patch. Except for the issues mentioned by aph about the v1 patch, this patch is also causing the jcstress test failures with the latest aarch64-8u jdk, which is easy to reproduce. One failed case is : o.o.j.t.memeffects.basic.atomic.AtomicInteger.atomic_get_getAndSet_boolean under JVM args: [-client, -XX:TieredStopAtLevel=1, -Xcomp]. The reason is that the v1 patch uses a LSE "swp" instruction for the" lir_xchg" case in LIR_Assembler::atomic_op, which is lacking the necessary acquire & release semantics. The v2 patch is uses a LSE "swpal" instruction instead, . This issue can be fixed by reverting the v1 patch and backporting the v2 patch from jdk9+, which also makes the support for ARMv8.1 LSE atomic operations consistent. Webrev: http://cr.openjdk.java.net/~fyang/lse-8u-backports/webrev.00/ This webrev also incorporates one trivial fix for the v2 patch: https://bugs.openjdk.java.net/browse/JDK-8153172 http://hg.openjdk.java.net/jdk9/jdk9/hotspot/rev/8911d94e888b JCstress tested on both ARMv8 and ARMv8.1 platforms. Also ran JTreg test on both platforms. OK to backport? Thanks, Felix From aph at redhat.com Mon Feb 25 09:28:01 2019 From: aph at redhat.com (Andrew Haley) Date: Mon, 25 Feb 2019 09:28:01 +0000 Subject: [aarch64-port-dev ] Fix aarch64-8u jcstress test failure on ARMv8.1 platform In-Reply-To: References: Message-ID: <63ed2df7-c2d6-d6dd-4766-30586164b8d0@redhat.com> On 2/25/19 7:53 AM, Yangfei (Felix) wrote: > This webrev also incorporates one trivial fix for the v2 patch: > https://bugs.openjdk.java.net/browse/JDK-8153172 > http://hg.openjdk.java.net/jdk9/jdk9/hotspot/rev/8911d94e888b > > JCstress tested on both ARMv8 and ARMv8.1 platforms. Also ran JTreg test on both platforms. > OK to backport? Looks good. Approved. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From felix.yang at huawei.com Mon Feb 25 13:29:17 2019 From: felix.yang at huawei.com (felix.yang at huawei.com) Date: Mon, 25 Feb 2019 13:29:17 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 2 new changesets Message-ID: <201902251329.x1PDTHvi017065@aojmv0008.oracle.com> Changeset: b684f8354d32 Author: fyang Date: 2019-02-23 15:15 +0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/b684f8354d32 8151775: aarch64: add support for 8.1 LSE atomic operations Reviewed-by: aph ! src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp ! src/cpu/aarch64/vm/macroAssembler_aarch64.cpp ! src/cpu/aarch64/vm/macroAssembler_aarch64.hpp ! src/cpu/aarch64/vm/templateInterpreter_aarch64.cpp ! src/os_cpu/linux_aarch64/vm/atomic_linux_aarch64.inline.hpp Changeset: d0bf0d3e0b2e Author: fyang Date: 2019-02-23 16:09 +0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/d0bf0d3e0b2e 8153172: aarch64: hotspot crashes after the 8.1 LSE patch is merged Summary: Fix scratch register usage in C1 atomic_op to avoid unpredictable instruction Reviewed-by: aph Contributed-by: felix.yang at linaro.org ! src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp From felix.yang at huawei.com Mon Feb 25 13:30:05 2019 From: felix.yang at huawei.com (felix.yang at huawei.com) Date: Mon, 25 Feb 2019 13:30:05 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/hotspot: 2 new changesets Message-ID: <201902251330.x1PDU5iq017414@aojmv0008.oracle.com> Changeset: 693eba576dfe Author: fyang Date: 2019-02-23 15:15 +0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/693eba576dfe 8151775: aarch64: add support for 8.1 LSE atomic operations Reviewed-by: aph ! src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp ! src/cpu/aarch64/vm/macroAssembler_aarch64.cpp ! src/cpu/aarch64/vm/macroAssembler_aarch64.hpp ! src/cpu/aarch64/vm/templateInterpreter_aarch64.cpp ! src/os_cpu/linux_aarch64/vm/atomic_linux_aarch64.inline.hpp Changeset: 57cc73ef7f11 Author: fyang Date: 2019-02-23 16:09 +0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/57cc73ef7f11 8153172: aarch64: hotspot crashes after the 8.1 LSE patch is merged Summary: Fix scratch register usage in C1 atomic_op to avoid unpredictable instruction Reviewed-by: aph Contributed-by: felix.yang at linaro.org ! src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp From dmitrij.pochepko at bell-sw.com Mon Feb 25 16:52:33 2019 From: dmitrij.pochepko at bell-sw.com (Dmitrij Pochepko) Date: Mon, 25 Feb 2019 19:52:33 +0300 Subject: [aarch64-port-dev ] RFR: 8218748: AARCH64: String::compareTo intrinsic documentation and maintenance improvement In-Reply-To: <86f91401-b7f6-b634-fef1-b0615b8fcde0@redhat.com> References: <86f91401-b7f6-b634-fef1-b0615b8fcde0@redhat.com> Message-ID: Hi Andrew, Pengfei, I created webrev.02 with all your suggestions implemented: webrev: http://cr.openjdk.java.net/~dpochepk/8218748/webrev.02/ - comments are now both in separate section and inlined into code. - documentation mismatch mentioned by Pengfei is fixed: -- SHORT_LAST_INIT label name misprint changed to correct SHORT_LAST -- SHORT_LOOP_TAIL block now merged with last instruction. Documentation is updated respectively - minor other changes to layout and wording Newly developed tests were run as sanity and they passed. Thanks, Dmitrij On 22/02/2019 6:42 PM, Andrew Haley wrote: > On 2/22/19 10:31 AM, Pengfei Li (Arm Technology China) wrote: > >> So personally, I still prefer to inline the comments with the >> original code block to avoid this kind of inconsistencies. And it >> makes us easier to review or maintain the code together with the >> doc, as we don't need to scroll back and force. I don't know the >> benefit of making the code documentation as a separate part. What's >> your opinion, Andrew Haley? > I agree with you. There's no harm having both inline and separate. > From ci_notify at linaro.org Mon Feb 25 22:45:01 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Mon, 25 Feb 2019 22:45:01 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <722250302.535.1551134702027.JavaMail.jenkins@a6c5c67cda76> 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/056/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/jan/16 pass: 5,511; fail: 6; error: 2; not run: 93 Build 1: aarch64/2019/jan/21 pass: 5,514; fail: 8; error: 1; not run: 93 Build 2: aarch64/2019/jan/24 pass: 5,520; fail: 5; error: 1; not run: 93 Build 3: aarch64/2019/jan/25 pass: 5,533; fail: 6; error: 1; not run: 93 Build 4: aarch64/2019/jan/28 pass: 5,533; fail: 6; error: 1; not run: 93 Build 5: aarch64/2019/jan/30 pass: 5,527; fail: 5; error: 2; not run: 93 Build 6: aarch64/2019/feb/04 pass: 5,527; fail: 7; error: 2; not run: 93 Build 7: aarch64/2019/feb/06 pass: 5,532; fail: 4; error: 1; not run: 93 Build 8: aarch64/2019/feb/08 pass: 5,519; fail: 19; error: 2; not run: 93 Build 9: aarch64/2019/feb/11 pass: 5,527; fail: 11; error: 2; not run: 93 Build 10: aarch64/2019/feb/13 pass: 5,537; fail: 4; not run: 93 Build 11: aarch64/2019/feb/15 pass: 5,538; fail: 4; not run: 93 Build 12: aarch64/2019/feb/18 pass: 5,538; fail: 4; not run: 93 Build 13: aarch64/2019/feb/20 pass: 5,539; fail: 4; not run: 93 Build 14: aarch64/2019/feb/25 pass: 5,540; fail: 4; not run: 93 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/16 pass: 8,553; fail: 480; error: 15 Build 1: aarch64/2019/jan/21 pass: 8,521; fail: 511; error: 20 Build 2: aarch64/2019/jan/24 pass: 8,533; fail: 503; error: 18 Build 3: aarch64/2019/jan/25 pass: 8,538; fail: 500; error: 20 Build 4: aarch64/2019/jan/28 pass: 8,543; fail: 496; error: 20 Build 5: aarch64/2019/jan/30 pass: 8,541; fail: 503; error: 19 Build 6: aarch64/2019/feb/04 pass: 8,539; fail: 506; error: 18 Build 7: aarch64/2019/feb/06 pass: 8,537; fail: 499; error: 27 Build 8: aarch64/2019/feb/08 pass: 8,530; fail: 515; error: 23 Build 9: aarch64/2019/feb/11 pass: 8,559; fail: 490; error: 15 Build 10: aarch64/2019/feb/13 pass: 8,534; fail: 512; error: 18 Build 11: aarch64/2019/feb/15 pass: 8,556; fail: 492; error: 16 Build 12: aarch64/2019/feb/18 pass: 8,530; fail: 514; error: 20 Build 13: aarch64/2019/feb/20 pass: 8,550; fail: 498; error: 17 Build 14: aarch64/2019/feb/25 pass: 8,535; fail: 510; error: 23 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/16 pass: 3,993 Build 1: aarch64/2019/jan/21 pass: 3,993; fail: 1 Build 2: aarch64/2019/jan/24 pass: 3,993; fail: 1 Build 3: aarch64/2019/jan/25 pass: 3,993; fail: 1 Build 4: aarch64/2019/jan/28 pass: 3,994; fail: 1 Build 5: aarch64/2019/jan/30 pass: 3,994; fail: 1 Build 6: aarch64/2019/feb/04 pass: 3,994; fail: 1 Build 7: aarch64/2019/feb/06 pass: 3,994; fail: 1 Build 8: aarch64/2019/feb/08 pass: 3,994; fail: 1 Build 9: aarch64/2019/feb/11 pass: 3,994; fail: 1 Build 10: aarch64/2019/feb/13 pass: 3,994; fail: 1 Build 11: aarch64/2019/feb/15 pass: 3,995 Build 12: aarch64/2019/feb/18 pass: 3,996 Build 13: aarch64/2019/feb/20 pass: 3,996 Build 14: aarch64/2019/feb/25 pass: 3,931 ------------------------------------------------------------------------------- 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.71x Relative performance: Server critical-jOPS (nc): 9.94x 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-16 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/016/results/ 2019-01-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/021/results/ 2019-01-24 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/024/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/028/results/ 2019-01-31 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/030/results/ 2019-02-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/035/results/ 2019-02-07 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/037/results/ 2019-02-09 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/039/results/ 2019-02-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/042/results/ 2019-02-14 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/044/results/ 2019-02-15 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/046/results/ 2019-02-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/049/results/ 2019-02-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/051/results/ 2019-02-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/056/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 Feb 26 01:33:40 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Tue, 26 Feb 2019 01:33:40 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> <1880b8f1-7563-f50e-aef9-5c6032672844@redhat.com> Message-ID: Bug: https://bugs.openjdk.java.net/browse/JDK-8219635 Webrev: http://cr.openjdk.java.net/~fyang/8219635/webrev.00/ AArch64 8u-backport: http://cr.openjdk.java.net/~fyang/8219635-backport/webrev.00/ Both JCstress tested. OK to push? Thanks, Felix > > Thanks for reviewed this, Andrew. > > Hi Felix, > Could you please help sponsor this extra patch as well? It is quite similar as your > previous one. > I found JDK-8218185 has been resolved and the subject was for > "putfield_or_static". Probably a new Jira ticket is needed for this > "fast_storefield" and two issues are closely corelated. I have no commit > permission so appreciate your help very much! (both jdk/jdk and jdk8u) > > Regarding the tests, I have run jtreg jdk_core and jcstress on my aarch64 > platform, no problem found. Please help double check at your side too if possible. > Thanks. > > diff -r 2a78b2963793 src/hotspot/cpu/aarch64/templateTable_aarch64.cpp > --- a/src/hotspot/cpu/aarch64/templateTable_aarch64.cpp Wed Feb 13 13:27:17 > 2019 +0100 > +++ b/src/hotspot/cpu/aarch64/templateTable_aarch64.cpp Fri Feb 22 17:18:20 > 2019 +0800 > @@ -2981,7 +2981,7 @@ > { > Label notVolatile; > __ tbz(r3, ConstantPoolCacheEntry::is_volatile_shift, notVolatile); > - __ membar(MacroAssembler::StoreStore); > + __ membar(MacroAssembler::StoreStore | MacroAssembler::LoadStore); > __ bind(notVolatile); > } From gnu.andrew at redhat.com Tue Feb 26 01:46:41 2019 From: gnu.andrew at redhat.com (Andrew Hughes) Date: Tue, 26 Feb 2019 01:46:41 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/hotspot: 2 new changesets In-Reply-To: <201902251330.x1PDU5iq017414@aojmv0008.oracle.com> References: <201902251330.x1PDU5iq017414@aojmv0008.oracle.com> Message-ID: On Mon, 25 Feb 2019 at 13:31, wrote: > > Changeset: 693eba576dfe > Author: fyang > Date: 2019-02-23 15:15 +0800 > URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/693eba576dfe > > 8151775: aarch64: add support for 8.1 LSE atomic operations > Reviewed-by: aph > > ! src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp > ! src/cpu/aarch64/vm/macroAssembler_aarch64.cpp > ! src/cpu/aarch64/vm/macroAssembler_aarch64.hpp > ! src/cpu/aarch64/vm/templateInterpreter_aarch64.cpp > ! src/os_cpu/linux_aarch64/vm/atomic_linux_aarch64.inline.hpp > > Changeset: 57cc73ef7f11 > Author: fyang > Date: 2019-02-23 16:09 +0800 > URL: http://hg.openjdk.java.net/aarch64-port/jdk8u/hotspot/rev/57cc73ef7f11 > > 8153172: aarch64: hotspot crashes after the 8.1 LSE patch is merged > Summary: Fix scratch register usage in C1 atomic_op to avoid unpredictable instruction > Reviewed-by: aph > Contributed-by: felix.yang at linaro.org > > ! src/cpu/aarch64/vm/c1_LIRAssembler_aarch64.cpp > Is there a reason you're pushing to aarch64-port/jdk8u, given it's no longer maintained? -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) Web Site: http://fuseyism.com Twitter: https://twitter.com/gnu_andrew_java PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 From felix.yang at huawei.com Tue Feb 26 02:20:07 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Tue, 26 Feb 2019 02:20:07 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/hotspot: 2 new changesets In-Reply-To: References: <201902251330.x1PDU5iq017414@aojmv0008.oracle.com> Message-ID: > > Is there a reason you're pushing to aarch64-port/jdk8u, given it's no > longer maintained? > -- No specific reasons for that. I noticed backport patches were pushed to both branches about three months ago: https://mail.openjdk.java.net/pipermail/aarch64-port-dev/2018-November/006515.html https://mail.openjdk.java.net/pipermail/aarch64-port-dev/2018-November/006514.html So I am doing the same way. I can leave aside aarch64-port/jdk8u. Thanks, Felix From shade at redhat.com Tue Feb 26 08:23:52 2019 From: shade at redhat.com (Aleksey Shipilev) Date: Tue, 26 Feb 2019 09:23:52 +0100 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/hotspot: 2 new changesets In-Reply-To: References: <201902251330.x1PDU5iq017414@aojmv0008.oracle.com> Message-ID: <09d002b5-df8a-945e-80b4-f365a737d88d@redhat.com> On 2/26/19 3:20 AM, Yangfei (Felix) wrote: >> >> Is there a reason you're pushing to aarch64-port/jdk8u, given it's no >> longer maintained? >> -- > > No specific reasons for that. > > I noticed backport patches were pushed to both branches about three months ago: > https://mail.openjdk.java.net/pipermail/aarch64-port-dev/2018-November/006515.html > https://mail.openjdk.java.net/pipermail/aarch64-port-dev/2018-November/006514.html > > So I am doing the same way. I can leave aside aarch64-port/jdk8u. Request the ops@ to turn one of the repositories read-only, Andrew? -Aleksey From aph at redhat.com Tue Feb 26 08:36:52 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 26 Feb 2019 08:36:52 +0000 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> <1880b8f1-7563-f50e-aef9-5c6032672844@redhat.com> Message-ID: On 2/26/19 1:33 AM, Yangfei (Felix) wrote: > Bug: https://bugs.openjdk.java.net/browse/JDK-8219635 > Webrev: http://cr.openjdk.java.net/~fyang/8219635/webrev.00/ > AArch64 8u-backport: http://cr.openjdk.java.net/~fyang/8219635-backport/webrev.00/ > > Both JCstress tested. OK to push? OK. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Tue Feb 26 09:09:08 2019 From: aph at redhat.com (Andrew Haley) Date: Tue, 26 Feb 2019 09:09:08 +0000 Subject: [aarch64-port-dev ] [RFR] [8u] 8u192 Upstream Sync In-Reply-To: References: Message-ID: <24d24dfd-089a-b98c-9a91-4f2f3532e08b@redhat.com> On 1/18/19 3:36 AM, Andrew Hughes wrote: > That's fine from my point of view. I have two more to immediately > follow this: the two AArch64 fixes I mentioned to get this working > on AArch64 again, and then 8u201. > > There would then be an 8u201 sync with upstream, and finally 8u202 > merge from upstream. Those I still need to complete and test out on > our RPMs before submission. OK, please go ahead. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From felix.yang at huawei.com Tue Feb 26 13:21:40 2019 From: felix.yang at huawei.com (felix.yang at huawei.com) Date: Tue, 26 Feb 2019 13:21:40 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 8219635: aarch64: missing LoadStore barrier in TemplateTable::fast_storefield Message-ID: <201902261321.x1QDLe5U010617@aojmv0008.oracle.com> Changeset: 7b7da2a4e83c Author: fyang Date: 2019-02-25 19:09 +0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/7b7da2a4e83c 8219635: aarch64: missing LoadStore barrier in TemplateTable::fast_storefield Reviewed-by: aph Contributed-by: patrick at os.amperecomputing.com ! src/cpu/aarch64/vm/templateTable_aarch64.cpp From gnu.andrew at redhat.com Tue Feb 26 17:20:46 2019 From: gnu.andrew at redhat.com (Andrew Hughes) Date: Tue, 26 Feb 2019 17:20:46 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u/hotspot: 2 new changesets In-Reply-To: References: <201902251330.x1PDU5iq017414@aojmv0008.oracle.com> Message-ID: On Tue, 26 Feb 2019 at 02:20, Yangfei (Felix) wrote: > > > > > Is there a reason you're pushing to aarch64-port/jdk8u, given it's no > > longer maintained? > > -- > > No specific reasons for that. > > I noticed backport patches were pushed to both branches about three months ago: > https://mail.openjdk.java.net/pipermail/aarch64-port-dev/2018-November/006515.html > https://mail.openjdk.java.net/pipermail/aarch64-port-dev/2018-November/006514.html > > So I am doing the same way. I can leave aside aarch64-port/jdk8u. > > Thanks, > Felix Ok, I was wondering if you were using it for something and so was going to warn you that it doesn't have the latest security fixes from 8u191 & 8u201. It doesn't really cause any problems, but we should probably make it read only to avoid this confusion. -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) Web Site: http://fuseyism.com Twitter: https://twitter.com/gnu_andrew_java PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 From gnu.andrew at redhat.com Tue Feb 26 21:54:40 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 26 Feb 2019 21:54:40 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah: 45 new changesets Message-ID: <201902262154.x1QLseCU007439@aojmv0008.oracle.com> Changeset: 58d9f4132496 Author: andrew Date: 2019-02-25 05:09 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/58d9f4132496 Added tag aarch64-shenandoah-jdk8u201-b11 for changeset d6a89862f1cc ! .hgtags Changeset: e131417abf59 Author: diazhou Date: 2018-10-06 05:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/e131417abf59 Added tag jdk8u192-b12 for changeset 4d3fefdd2f98 ! .hgtags Changeset: b425c4315c20 Author: diazhou Date: 2018-10-08 10:54 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/b425c4315c20 Added tag jdk8u192-b26 for changeset e131417abf59 ! .hgtags Changeset: 3322b7fdc03f Author: diazhou Date: 2018-10-06 04:39 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/3322b7fdc03f Added tag jdk8u191-b12 for changeset 6432b2dd408c ! .hgtags Changeset: 706bc7b97694 Author: diazhou Date: 2018-10-08 10:19 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/706bc7b97694 Added tag jdk8u191-b26 for changeset 3322b7fdc03f ! .hgtags Changeset: 363f5cb2a9ed Author: aefimov Date: 2018-10-08 20:42 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/363f5cb2a9ed Merge ! .hgtags Changeset: 1935c4d42613 Author: aefimov Date: 2018-07-11 15:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/1935c4d42613 Added tag jdk8u201-b00 for changeset d6007fa4ffae ! .hgtags Changeset: d6a70178d360 Author: aefimov Date: 2018-07-27 11:46 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/d6a70178d360 Merge ! .hgtags Changeset: ecf6f15f5d5d Author: aefimov Date: 2018-08-04 12:52 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/ecf6f15f5d5d Merge ! .hgtags Changeset: 49178e2b8f4d Author: aefimov Date: 2018-08-10 12:27 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/49178e2b8f4d Merge ! .hgtags Changeset: 3c7ce574bd75 Author: aefimov Date: 2018-08-18 12:58 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/3c7ce574bd75 Merge ! .hgtags Changeset: 39cd012b6aa4 Author: alitvinov Date: 2018-08-24 19:22 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/39cd012b6aa4 Merge ! .hgtags Changeset: 33dd16e44595 Author: alitvinov Date: 2018-09-03 16:52 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/33dd16e44595 Merge ! .hgtags Changeset: 54ee1ff3842b Author: dmarkov Date: 2018-09-07 10:18 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/54ee1ff3842b 8210431: Complete backport of libpng 1.6.35 TPRM Reviewed-by: jeff, prr ! THIRD_PARTY_README Changeset: 1a10633a3a1d Author: alitvinov Date: 2018-09-10 16:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/1a10633a3a1d Merge ! .hgtags Changeset: 0cfb160ceb80 Author: aefimov Date: 2018-09-17 15:04 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/0cfb160ceb80 Merge ! .hgtags Changeset: fbe47c49e7ee Author: aefimov Date: 2018-07-02 16:27 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/fbe47c49e7ee Merge ! .hgtags ! common/autoconf/generated-configure.sh Changeset: e2463fc19255 Author: diazhou Date: 2018-07-04 02:06 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/e2463fc19255 Added tag jdk8u181-b31 for changeset fbe47c49e7ee ! .hgtags Changeset: 0296aef8d561 Author: aefimov Date: 2018-07-11 00:20 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/0296aef8d561 Merge ! .hgtags Changeset: f15cbd32f132 Author: diazhou Date: 2018-07-11 22:53 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/f15cbd32f132 Added tag jdk8u181-b32 for changeset 0296aef8d561 ! .hgtags Changeset: 2d56732bb1b8 Author: diazhou Date: 2018-07-24 13:16 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/2d56732bb1b8 Added tag jdk8u181-b33 for changeset f15cbd32f132 ! .hgtags Changeset: 56562c6fe999 Author: diazhou Date: 2018-08-27 01:50 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/56562c6fe999 Added tag jdk8u181-b34 for changeset 2d56732bb1b8 ! .hgtags Changeset: f5e8607118ba Author: diazhou Date: 2018-09-10 14:05 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/f5e8607118ba Added tag jdk8u181-b35 for changeset 56562c6fe999 ! .hgtags Changeset: 6be7467c0f3b Author: diazhou Date: 2018-09-24 19:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/6be7467c0f3b Added tag jdk8u181-b36 for changeset f5e8607118ba ! .hgtags Changeset: 48a34b5e4655 Author: aefimov Date: 2018-09-26 15:23 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/48a34b5e4655 Merge ! .hgtags Changeset: d5254c14e1ea Author: aefimov Date: 2018-09-30 19:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/d5254c14e1ea Merge ! .hgtags Changeset: 7baa4ad9c98f Author: diazhou Date: 2018-10-04 02:46 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/7baa4ad9c98f Added tag jdk8u181-b37 for changeset 6be7467c0f3b ! .hgtags Changeset: 2a2ddb83b8e0 Author: aefimov Date: 2018-10-05 16:51 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/2a2ddb83b8e0 Merge ! .hgtags Changeset: 6b45574a5596 Author: aefimov Date: 2018-10-08 21:51 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/6b45574a5596 Merge ! .hgtags Changeset: df6617cb2038 Author: diazhou Date: 2018-10-17 04:41 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/df6617cb2038 Added tag jdk8u201-b01 for changeset 6b45574a5596 ! .hgtags Changeset: 09dcb0ab23d0 Author: diazhou Date: 2018-11-01 16:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/09dcb0ab23d0 Added tag jdk8u201-b02 for changeset df6617cb2038 ! .hgtags Changeset: 0506fb60784e Author: diazhou Date: 2018-11-07 04:25 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/0506fb60784e Added tag jdk8u201-b03 for changeset 09dcb0ab23d0 ! .hgtags Changeset: 93019419c535 Author: diazhou Date: 2018-11-14 10:17 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/93019419c535 Added tag jdk8u201-b04 for changeset 0506fb60784e ! .hgtags Changeset: d5f2a8d71e50 Author: diazhou Date: 2018-11-14 11:11 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/d5f2a8d71e50 Added tag jdk8u201-b74 for changeset 93019419c535 ! .hgtags Changeset: 3ce64f831a36 Author: diazhou Date: 2018-11-19 03:06 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/3ce64f831a36 Added tag jdk8u201-b05 for changeset d5f2a8d71e50 ! .hgtags Changeset: 6815d9894b30 Author: diazhou Date: 2018-11-22 09:32 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/6815d9894b30 Added tag jdk8u201-b75 for changeset 3ce64f831a36 ! .hgtags Changeset: 065b4b9247bd Author: diazhou Date: 2018-11-27 09:15 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/065b4b9247bd Added tag jdk8u201-b06 for changeset 6815d9894b30 ! .hgtags Changeset: 8cd738678469 Author: diazhou Date: 2018-11-27 10:22 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/8cd738678469 Added tag jdk8u201-b76 for changeset 065b4b9247bd ! .hgtags Changeset: 2c9ec0970599 Author: kevinw Date: 2018-11-19 14:52 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/2c9ec0970599 8199552: Update to build scripts Reviewed-by: jwilhelm ! common/autoconf/flags.m4 ! common/autoconf/generated-configure.sh Changeset: fb2d87afd9f8 Author: alitvinov Date: 2018-11-28 13:53 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/fb2d87afd9f8 8213792: Update THIRTD_PARTY_README for LCMS to 2.9 Reviewed-by: prr ! THIRD_PARTY_README Changeset: 97ecc454983b Author: diazhou Date: 2018-12-05 19:23 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/97ecc454983b Added tag jdk8u201-b07 for changeset fb2d87afd9f8 ! .hgtags Changeset: 4b734c44eee9 Author: diazhou Date: 2018-12-05 19:44 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/4b734c44eee9 Added tag jdk8u201-b77 for changeset 97ecc454983b ! .hgtags Changeset: 9250f6917113 Author: diazhou Date: 2018-12-11 23:59 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/9250f6917113 Added tag jdk8u201-b08 for changeset 4b734c44eee9 ! .hgtags Changeset: 44b0de312e79 Author: andrew Date: 2019-02-26 00:54 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/44b0de312e79 Merge jdk8u201-ga ! .hgtags ! THIRD_PARTY_README ! common/autoconf/flags.m4 ! common/autoconf/generated-configure.sh Changeset: 8c813b474805 Author: andrew Date: 2019-02-26 00:56 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/rev/8c813b474805 Added tag aarch64-shenandoah-jdk8u201-b12 for changeset 44b0de312e79 ! .hgtags From gnu.andrew at redhat.com Tue Feb 26 21:54:49 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 26 Feb 2019 21:54:49 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/corba: 44 new changesets Message-ID: <201902262154.x1QLsn8U007540@aojmv0008.oracle.com> Changeset: 44ee35451fd3 Author: andrew Date: 2019-02-25 05:09 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/44ee35451fd3 Added tag aarch64-shenandoah-jdk8u201-b11 for changeset 52ad646e8553 ! .hgtags Changeset: a86c7b3fc440 Author: diazhou Date: 2018-10-06 05:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/a86c7b3fc440 Added tag jdk8u192-b12 for changeset d70620db70e3 ! .hgtags Changeset: 43b5bbfe2a35 Author: diazhou Date: 2018-10-08 10:54 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/43b5bbfe2a35 Added tag jdk8u192-b26 for changeset a86c7b3fc440 ! .hgtags Changeset: 314a4e05e420 Author: diazhou Date: 2018-10-06 04:39 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/314a4e05e420 Added tag jdk8u191-b12 for changeset 298df76047a5 ! .hgtags Changeset: 8ee1d729abb0 Author: diazhou Date: 2018-10-08 10:19 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/8ee1d729abb0 Added tag jdk8u191-b26 for changeset 314a4e05e420 ! .hgtags Changeset: a349bf5a9de7 Author: aefimov Date: 2018-10-08 20:41 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/a349bf5a9de7 Merge ! .hgtags Changeset: eef71b4198f2 Author: aefimov Date: 2018-07-11 15:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/eef71b4198f2 Added tag jdk8u201-b00 for changeset ce3b35fca864 ! .hgtags Changeset: 712b19a7da9f Author: aefimov Date: 2018-07-27 11:45 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/712b19a7da9f Merge ! .hgtags Changeset: 6c0b61eac246 Author: aefimov Date: 2018-08-04 12:51 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/6c0b61eac246 Merge ! .hgtags Changeset: b2e5ccf7b07c Author: aefimov Date: 2018-08-10 12:27 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/b2e5ccf7b07c Merge ! .hgtags Changeset: ab96a038970e Author: aefimov Date: 2018-08-18 12:58 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/ab96a038970e Merge ! .hgtags Changeset: eab375ccfd9d Author: alitvinov Date: 2018-08-24 19:22 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/eab375ccfd9d Merge ! .hgtags Changeset: 980b965bc39e Author: alitvinov Date: 2018-09-03 16:52 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/980b965bc39e Merge ! .hgtags Changeset: 0b38d96aec1c Author: dmarkov Date: 2018-09-07 10:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/0b38d96aec1c 8210431: Complete backport of libpng 1.6.35 TPRM Reviewed-by: jeff, prr ! THIRD_PARTY_README Changeset: 0bb8fea48637 Author: alitvinov Date: 2018-09-10 16:17 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/0bb8fea48637 Merge ! .hgtags Changeset: 9388799c8566 Author: aefimov Date: 2018-09-17 15:00 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/9388799c8566 Merge ! .hgtags Changeset: d6e70a820e6b Author: aefimov Date: 2018-07-02 16:24 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/d6e70a820e6b Merge ! .hgtags Changeset: cb5ee8562d99 Author: diazhou Date: 2018-07-04 02:06 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/cb5ee8562d99 Added tag jdk8u181-b31 for changeset d6e70a820e6b ! .hgtags Changeset: 0fba5f3cce1f Author: aefimov Date: 2018-07-11 00:18 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/0fba5f3cce1f Merge ! .hgtags Changeset: 99f73e3d73f1 Author: diazhou Date: 2018-07-11 22:53 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/99f73e3d73f1 Added tag jdk8u181-b32 for changeset 0fba5f3cce1f ! .hgtags Changeset: 5b648b564d19 Author: diazhou Date: 2018-07-24 13:16 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/5b648b564d19 Added tag jdk8u181-b33 for changeset 99f73e3d73f1 ! .hgtags Changeset: 9e341ecdf741 Author: diazhou Date: 2018-08-27 01:50 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/9e341ecdf741 Added tag jdk8u181-b34 for changeset 5b648b564d19 ! .hgtags Changeset: fdb4bff55790 Author: diazhou Date: 2018-09-10 14:06 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/fdb4bff55790 Added tag jdk8u181-b35 for changeset 9e341ecdf741 ! .hgtags Changeset: 4a42d89f7ba2 Author: diazhou Date: 2018-09-24 19:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/4a42d89f7ba2 Added tag jdk8u181-b36 for changeset fdb4bff55790 ! .hgtags Changeset: 2bde3d3cbff9 Author: aefimov Date: 2018-09-26 15:20 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/2bde3d3cbff9 Merge ! .hgtags Changeset: cb14afdf55df Author: aefimov Date: 2018-09-30 19:57 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/cb14afdf55df Merge ! .hgtags Changeset: 9b30025f3ac3 Author: diazhou Date: 2018-10-04 02:46 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/9b30025f3ac3 Added tag jdk8u181-b37 for changeset 4a42d89f7ba2 ! .hgtags Changeset: e93186b1e62f Author: aefimov Date: 2018-10-05 16:51 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/e93186b1e62f Merge ! .hgtags Changeset: 291e5023b0c5 Author: aefimov Date: 2018-10-08 21:46 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/291e5023b0c5 Merge ! .hgtags Changeset: 8dc9ee9494c9 Author: diazhou Date: 2018-10-17 04:41 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/8dc9ee9494c9 Added tag jdk8u201-b01 for changeset 291e5023b0c5 ! .hgtags Changeset: 637785bfd832 Author: diazhou Date: 2018-11-01 16:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/637785bfd832 Added tag jdk8u201-b02 for changeset 8dc9ee9494c9 ! .hgtags Changeset: efa05252e6d4 Author: diazhou Date: 2018-11-07 04:25 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/efa05252e6d4 Added tag jdk8u201-b03 for changeset 637785bfd832 ! .hgtags Changeset: 0b1ad394520c Author: diazhou Date: 2018-11-14 10:17 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/0b1ad394520c Added tag jdk8u201-b04 for changeset efa05252e6d4 ! .hgtags Changeset: face39da0a93 Author: diazhou Date: 2018-11-14 11:11 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/face39da0a93 Added tag jdk8u201-b74 for changeset 0b1ad394520c ! .hgtags Changeset: 34fa3c008e22 Author: diazhou Date: 2018-11-19 03:06 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/34fa3c008e22 Added tag jdk8u201-b05 for changeset face39da0a93 ! .hgtags Changeset: 7ed32e9e0596 Author: diazhou Date: 2018-11-22 09:32 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/7ed32e9e0596 Added tag jdk8u201-b75 for changeset 34fa3c008e22 ! .hgtags Changeset: 0303a8dc5824 Author: diazhou Date: 2018-11-27 09:15 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/0303a8dc5824 Added tag jdk8u201-b06 for changeset 7ed32e9e0596 ! .hgtags Changeset: 77dd701c96fe Author: diazhou Date: 2018-11-27 10:22 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/77dd701c96fe Added tag jdk8u201-b76 for changeset 0303a8dc5824 ! .hgtags Changeset: 52738cffda5b Author: alitvinov Date: 2018-11-28 13:48 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/52738cffda5b 8213792: Update THIRTD_PARTY_README for LCMS to 2.9 Reviewed-by: prr ! THIRD_PARTY_README Changeset: c4dc8ca88a3f Author: diazhou Date: 2018-12-05 19:23 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/c4dc8ca88a3f Added tag jdk8u201-b07 for changeset 52738cffda5b ! .hgtags Changeset: a775a126005d Author: diazhou Date: 2018-12-05 19:44 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/a775a126005d Added tag jdk8u201-b77 for changeset c4dc8ca88a3f ! .hgtags Changeset: 69ab1163c4bb Author: diazhou Date: 2018-12-11 23:59 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/69ab1163c4bb Added tag jdk8u201-b08 for changeset a775a126005d ! .hgtags Changeset: ae5eca166291 Author: andrew Date: 2019-02-26 00:54 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/ae5eca166291 Merge jdk8u201-ga ! .hgtags ! THIRD_PARTY_README Changeset: 3f143f309fe9 Author: andrew Date: 2019-02-26 00:56 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/corba/rev/3f143f309fe9 Added tag aarch64-shenandoah-jdk8u201-b12 for changeset ae5eca166291 ! .hgtags From gnu.andrew at redhat.com Tue Feb 26 21:54:57 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 26 Feb 2019 21:54:57 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxp: 45 new changesets Message-ID: <201902262154.x1QLswpS007659@aojmv0008.oracle.com> Changeset: b48f23c61cfb Author: andrew Date: 2019-02-25 05:09 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/b48f23c61cfb Added tag aarch64-shenandoah-jdk8u201-b11 for changeset 550545de620d ! .hgtags Changeset: fce0c0377cbd Author: diazhou Date: 2018-10-06 05:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/fce0c0377cbd Added tag jdk8u192-b12 for changeset 6465f54b4b63 ! .hgtags Changeset: 3649eacfbb43 Author: diazhou Date: 2018-10-08 10:54 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/3649eacfbb43 Added tag jdk8u192-b26 for changeset fce0c0377cbd ! .hgtags Changeset: a873d847260c Author: diazhou Date: 2018-10-06 04:40 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/a873d847260c Added tag jdk8u191-b12 for changeset 6da26fc7da9a ! .hgtags Changeset: 2a5cddf27b48 Author: diazhou Date: 2018-10-08 10:19 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/2a5cddf27b48 Added tag jdk8u191-b26 for changeset a873d847260c ! .hgtags Changeset: 09a3cb8c45a1 Author: aefimov Date: 2018-10-08 20:44 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/09a3cb8c45a1 Merge ! .hgtags Changeset: ba1b15a15e5a Author: aefimov Date: 2018-07-11 15:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/ba1b15a15e5a Added tag jdk8u201-b00 for changeset ecdbe3bf911c ! .hgtags Changeset: 332eaf7ad0ee Author: aefimov Date: 2018-07-27 11:48 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/332eaf7ad0ee Merge ! .hgtags Changeset: 237b80356459 Author: aefimov Date: 2018-08-04 12:54 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/237b80356459 Merge ! .hgtags Changeset: f6128edbaab2 Author: aefimov Date: 2018-08-10 13:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/f6128edbaab2 Merge ! .hgtags Changeset: 5901be6849e4 Author: aefimov Date: 2018-08-18 13:03 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/5901be6849e4 Merge ! .hgtags Changeset: 5daf61775b30 Author: alitvinov Date: 2018-08-24 19:32 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/5daf61775b30 Merge ! .hgtags Changeset: e0c837a76587 Author: alitvinov Date: 2018-09-03 16:55 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/e0c837a76587 Merge ! .hgtags Changeset: 741c713900f9 Author: dmarkov Date: 2018-09-07 10:24 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/741c713900f9 8210431: Complete backport of libpng 1.6.35 TPRM Reviewed-by: jeff, prr ! THIRD_PARTY_README Changeset: cbb05e621e3b Author: alitvinov Date: 2018-09-10 19:37 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/cbb05e621e3b Merge ! .hgtags Changeset: 32250914d8fb Author: aefimov Date: 2018-09-17 15:05 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/32250914d8fb Merge ! .hgtags Changeset: 382c9313d23f Author: aefimov Date: 2018-07-02 16:33 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/382c9313d23f Merge ! .hgtags Changeset: 7789ea92ce7d Author: diazhou Date: 2018-07-04 02:06 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/7789ea92ce7d Added tag jdk8u181-b31 for changeset 382c9313d23f ! .hgtags Changeset: 019bb0c95d8e Author: aefimov Date: 2018-07-11 00:26 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/019bb0c95d8e Merge ! .hgtags Changeset: 84e3a5220fdc Author: diazhou Date: 2018-07-11 22:53 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/84e3a5220fdc Added tag jdk8u181-b32 for changeset 019bb0c95d8e ! .hgtags Changeset: dd700ba0a891 Author: diazhou Date: 2018-07-24 13:17 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/dd700ba0a891 Added tag jdk8u181-b33 for changeset 84e3a5220fdc ! .hgtags Changeset: ed73be44ba93 Author: diazhou Date: 2018-08-27 01:51 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/ed73be44ba93 Added tag jdk8u181-b34 for changeset dd700ba0a891 ! .hgtags Changeset: f6e56479aedc Author: diazhou Date: 2018-09-10 14:06 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/f6e56479aedc Added tag jdk8u181-b35 for changeset ed73be44ba93 ! .hgtags Changeset: 0179f90264fa Author: diazhou Date: 2018-09-24 19:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/0179f90264fa Added tag jdk8u181-b36 for changeset f6e56479aedc ! .hgtags Changeset: 6d22a021a908 Author: aefimov Date: 2018-09-26 15:30 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/6d22a021a908 Merge ! .hgtags Changeset: 184e0f49b351 Author: aefimov Date: 2018-09-30 20:02 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/184e0f49b351 Merge ! .hgtags Changeset: c9db0b4d1be1 Author: diazhou Date: 2018-10-04 02:47 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/c9db0b4d1be1 Added tag jdk8u181-b37 for changeset 0179f90264fa ! .hgtags Changeset: 12305fb87863 Author: aefimov Date: 2018-10-05 16:53 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/12305fb87863 Merge ! .hgtags Changeset: fc3557ce51e4 Author: aefimov Date: 2018-10-08 21:54 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/fc3557ce51e4 Merge ! .hgtags Changeset: 477375759c38 Author: diazhou Date: 2018-10-17 04:42 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/477375759c38 Added tag jdk8u201-b01 for changeset fc3557ce51e4 ! .hgtags Changeset: bd61e1494e36 Author: diazhou Date: 2018-11-01 16:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/bd61e1494e36 Added tag jdk8u201-b02 for changeset 477375759c38 ! .hgtags Changeset: b54f96e9e357 Author: diazhou Date: 2018-11-07 04:26 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/b54f96e9e357 Added tag jdk8u201-b03 for changeset bd61e1494e36 ! .hgtags Changeset: f00858e3cb66 Author: ljiang Date: 2018-11-07 19:00 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/f00858e3cb66 8213368: JDK 8u201 l10n resource file update Reviewed-by: coffeys ! src/com/sun/org/apache/xalan/internal/xsltc/runtime/ErrorMessages_it.java ! src/com/sun/org/apache/xerces/internal/impl/msg/XMLMessages_sv.properties Changeset: 9c371081f017 Author: diazhou Date: 2018-11-14 10:17 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/9c371081f017 Added tag jdk8u201-b04 for changeset f00858e3cb66 ! .hgtags Changeset: fadb12a859bc Author: diazhou Date: 2018-11-14 11:12 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/fadb12a859bc Added tag jdk8u201-b74 for changeset 9c371081f017 ! .hgtags Changeset: 8b544083d841 Author: diazhou Date: 2018-11-19 03:07 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/8b544083d841 Added tag jdk8u201-b05 for changeset fadb12a859bc ! .hgtags Changeset: 0efa6d733578 Author: diazhou Date: 2018-11-22 09:33 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/0efa6d733578 Added tag jdk8u201-b75 for changeset 8b544083d841 ! .hgtags Changeset: f728390b15a5 Author: diazhou Date: 2018-11-27 09:16 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/f728390b15a5 Added tag jdk8u201-b06 for changeset 0efa6d733578 ! .hgtags Changeset: 3629282ec52e Author: diazhou Date: 2018-11-27 10:22 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/3629282ec52e Added tag jdk8u201-b76 for changeset f728390b15a5 ! .hgtags Changeset: 16c76ce6176a Author: alitvinov Date: 2018-11-28 13:49 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/16c76ce6176a 8213792: Update THIRTD_PARTY_README for LCMS to 2.9 Reviewed-by: prr ! THIRD_PARTY_README Changeset: ace766139b0a Author: diazhou Date: 2018-12-05 19:23 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/ace766139b0a Added tag jdk8u201-b07 for changeset 16c76ce6176a ! .hgtags Changeset: 4d0534929ed3 Author: diazhou Date: 2018-12-05 19:45 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/4d0534929ed3 Added tag jdk8u201-b77 for changeset ace766139b0a ! .hgtags Changeset: 0bd4dbc4d66f Author: diazhou Date: 2018-12-12 00:00 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/0bd4dbc4d66f Added tag jdk8u201-b08 for changeset 4d0534929ed3 ! .hgtags Changeset: 8da5b0a2983c Author: andrew Date: 2019-02-26 00:54 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/8da5b0a2983c Merge jdk8u201-ga ! .hgtags ! THIRD_PARTY_README Changeset: badb8fb70a52 Author: andrew Date: 2019-02-26 00:56 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxp/rev/badb8fb70a52 Added tag aarch64-shenandoah-jdk8u201-b12 for changeset 8da5b0a2983c ! .hgtags From gnu.andrew at redhat.com Tue Feb 26 21:55:16 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 26 Feb 2019 21:55:16 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/langtools: 45 new changesets Message-ID: <201902262155.x1QLtG2F007903@aojmv0008.oracle.com> Changeset: e82ec61d2268 Author: andrew Date: 2019-02-25 05:10 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/e82ec61d2268 Added tag aarch64-shenandoah-jdk8u201-b11 for changeset 14db9ad95f20 ! .hgtags Changeset: 4bbe353fcc36 Author: diazhou Date: 2018-10-06 05:12 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/4bbe353fcc36 Added tag jdk8u192-b12 for changeset 3eb4c8be649b ! .hgtags Changeset: b1c4dd6ea80c Author: diazhou Date: 2018-10-08 10:55 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/b1c4dd6ea80c Added tag jdk8u192-b26 for changeset 4bbe353fcc36 ! .hgtags Changeset: 17bb956bc44e Author: diazhou Date: 2018-10-06 04:40 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/17bb956bc44e Added tag jdk8u191-b12 for changeset d035a731ab59 ! .hgtags Changeset: 974270d3963d Author: diazhou Date: 2018-10-08 10:20 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/974270d3963d Added tag jdk8u191-b26 for changeset 17bb956bc44e ! .hgtags Changeset: 3f98d53fe94b Author: aefimov Date: 2018-10-08 20:48 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/3f98d53fe94b Merge ! .hgtags Changeset: 9b749364682d Author: aefimov Date: 2018-07-11 15:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/9b749364682d Added tag jdk8u201-b00 for changeset 1f33e21011aa ! .hgtags Changeset: 554e7579f421 Author: aefimov Date: 2018-07-27 11:50 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/554e7579f421 Merge ! .hgtags Changeset: 7b508cdd33ae Author: aefimov Date: 2018-08-04 12:55 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/7b508cdd33ae Merge ! .hgtags Changeset: d5c506c5e329 Author: aefimov Date: 2018-08-10 13:23 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/d5c506c5e329 Merge ! .hgtags Changeset: ee6eaa71e7db Author: aefimov Date: 2018-08-18 13:04 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/ee6eaa71e7db Merge ! .hgtags Changeset: 30258a15b1fc Author: alitvinov Date: 2018-08-24 19:36 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/30258a15b1fc Merge ! .hgtags Changeset: a9fd0c289f45 Author: alitvinov Date: 2018-09-03 16:57 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/a9fd0c289f45 Merge ! .hgtags Changeset: 0e6536643c51 Author: dmarkov Date: 2018-09-07 10:30 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/0e6536643c51 8210431: Complete backport of libpng 1.6.35 TPRM Reviewed-by: jeff, prr ! THIRD_PARTY_README Changeset: 2760408dc3a1 Author: alitvinov Date: 2018-09-10 19:39 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/2760408dc3a1 Merge ! .hgtags Changeset: defe0db6c1b2 Author: aefimov Date: 2018-09-17 15:07 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/defe0db6c1b2 Merge ! .hgtags Changeset: 107b71b590ec Author: aefimov Date: 2018-07-02 16:42 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/107b71b590ec Merge ! .hgtags Changeset: d480ba6d893b Author: diazhou Date: 2018-07-04 02:07 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/d480ba6d893b Added tag jdk8u181-b31 for changeset 107b71b590ec ! .hgtags Changeset: 46f42ead87aa Author: aefimov Date: 2018-07-11 00:29 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/46f42ead87aa Merge ! .hgtags Changeset: 0ce50eb7c16f Author: diazhou Date: 2018-07-11 22:54 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/0ce50eb7c16f Added tag jdk8u181-b32 for changeset 46f42ead87aa ! .hgtags Changeset: de209b077cbc Author: diazhou Date: 2018-07-24 13:17 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/de209b077cbc Added tag jdk8u181-b33 for changeset 0ce50eb7c16f ! .hgtags Changeset: d0895208bafb Author: diazhou Date: 2018-08-27 01:52 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/d0895208bafb Added tag jdk8u181-b34 for changeset de209b077cbc ! .hgtags Changeset: 22576f8af4bd Author: diazhou Date: 2018-09-10 14:06 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/22576f8af4bd Added tag jdk8u181-b35 for changeset d0895208bafb ! .hgtags Changeset: 8d841e832cc0 Author: diazhou Date: 2018-09-24 19:12 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/8d841e832cc0 Added tag jdk8u181-b36 for changeset 22576f8af4bd ! .hgtags Changeset: e41807918d27 Author: aefimov Date: 2018-09-26 15:36 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/e41807918d27 Merge ! .hgtags Changeset: 74bfa5dee571 Author: aefimov Date: 2018-09-30 20:05 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/74bfa5dee571 Merge ! .hgtags Changeset: 807ccbe26b23 Author: diazhou Date: 2018-10-04 02:47 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/807ccbe26b23 Added tag jdk8u181-b37 for changeset 8d841e832cc0 ! .hgtags Changeset: 303f5c5af01a Author: aefimov Date: 2018-10-05 16:54 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/303f5c5af01a Merge ! .hgtags Changeset: 30d61da05c3b Author: aefimov Date: 2018-10-08 21:57 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/30d61da05c3b Merge ! .hgtags Changeset: 8c18711ab932 Author: diazhou Date: 2018-10-17 04:42 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/8c18711ab932 Added tag jdk8u201-b01 for changeset 30d61da05c3b ! .hgtags Changeset: 4a4ded3965b6 Author: diazhou Date: 2018-11-01 16:12 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/4a4ded3965b6 Added tag jdk8u201-b02 for changeset 8c18711ab932 ! .hgtags Changeset: a7f48b9dfb82 Author: diazhou Date: 2018-11-07 04:26 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/a7f48b9dfb82 Added tag jdk8u201-b03 for changeset 4a4ded3965b6 ! .hgtags Changeset: 7909abb85562 Author: diazhou Date: 2018-11-14 10:18 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/7909abb85562 Added tag jdk8u201-b04 for changeset a7f48b9dfb82 ! .hgtags Changeset: 14d6465af4ec Author: diazhou Date: 2018-11-14 11:12 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/14d6465af4ec Added tag jdk8u201-b74 for changeset 7909abb85562 ! .hgtags Changeset: 5129e794a75f Author: diazhou Date: 2018-11-19 03:07 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/5129e794a75f Added tag jdk8u201-b05 for changeset 14d6465af4ec ! .hgtags Changeset: 772887000640 Author: diazhou Date: 2018-11-22 09:33 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/772887000640 Added tag jdk8u201-b75 for changeset 5129e794a75f ! .hgtags Changeset: a7a52249333b Author: diazhou Date: 2018-11-27 09:16 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/a7a52249333b Added tag jdk8u201-b06 for changeset 772887000640 ! .hgtags Changeset: b51338ca783a Author: diazhou Date: 2018-11-27 10:23 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/b51338ca783a Added tag jdk8u201-b76 for changeset a7a52249333b ! .hgtags Changeset: 4d330e212539 Author: ljiang Date: 2018-11-28 05:34 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/4d330e212539 8214357: JDK 8u201 l10n resource file update md20 Reviewed-by: coffeys ! src/share/classes/com/sun/tools/doclets/internal/toolkit/resources/doclets_ja.properties ! src/share/classes/com/sun/tools/javac/resources/compiler_ja.properties Changeset: 4fbee4ebd4d3 Author: alitvinov Date: 2018-11-28 13:52 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/4fbee4ebd4d3 8213792: Update THIRTD_PARTY_README for LCMS to 2.9 Reviewed-by: prr ! THIRD_PARTY_README Changeset: dd3348cbc2d0 Author: diazhou Date: 2018-12-05 19:24 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/dd3348cbc2d0 Added tag jdk8u201-b07 for changeset 4fbee4ebd4d3 ! .hgtags Changeset: 8c8f74830128 Author: diazhou Date: 2018-12-05 19:45 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/8c8f74830128 Added tag jdk8u201-b77 for changeset dd3348cbc2d0 ! .hgtags Changeset: 689d7755e8c1 Author: diazhou Date: 2018-12-12 00:00 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/689d7755e8c1 Added tag jdk8u201-b08 for changeset 8c8f74830128 ! .hgtags Changeset: 97f878ec8630 Author: andrew Date: 2019-02-26 00:54 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/97f878ec8630 Merge jdk8u201-ga ! .hgtags ! THIRD_PARTY_README Changeset: 71cfe243f425 Author: andrew Date: 2019-02-26 00:56 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/langtools/rev/71cfe243f425 Added tag aarch64-shenandoah-jdk8u201-b12 for changeset 97f878ec8630 ! .hgtags From gnu.andrew at redhat.com Tue Feb 26 21:55:35 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 26 Feb 2019 21:55:35 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jdk: 88 new changesets Message-ID: <201902262155.x1QLte8b008083@aojmv0008.oracle.com> Changeset: 1d5c7c3dd473 Author: andrew Date: 2019-02-25 05:10 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/1d5c7c3dd473 Added tag aarch64-shenandoah-jdk8u201-b11 for changeset 9d0c89fb5149 ! .hgtags Changeset: 996dd3ce1ec5 Author: diazhou Date: 2018-10-06 05:12 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/996dd3ce1ec5 Added tag jdk8u192-b12 for changeset f877dad22786 ! .hgtags Changeset: e54628116071 Author: diazhou Date: 2018-10-08 10:54 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/e54628116071 Added tag jdk8u192-b26 for changeset 996dd3ce1ec5 ! .hgtags Changeset: 574e92cf225b Author: diazhou Date: 2018-10-06 04:40 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/574e92cf225b Added tag jdk8u191-b12 for changeset 5ca18caa6a57 ! .hgtags Changeset: a59b76037144 Author: diazhou Date: 2018-10-08 10:20 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/a59b76037144 Added tag jdk8u191-b26 for changeset 574e92cf225b ! .hgtags Changeset: efd8398ea738 Author: aefimov Date: 2018-10-08 20:46 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/efd8398ea738 Merge ! .hgtags Changeset: 39f2b8e0403f Author: aefimov Date: 2018-07-11 15:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/39f2b8e0403f Added tag jdk8u201-b00 for changeset 2db6890a9567 ! .hgtags Changeset: 74fcc2fed0b3 Author: kaddepalli Date: 2018-07-13 11:22 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/74fcc2fed0b3 8194546: Choosier FileManagers Reviewed-by: prr, serb, skoivu, rhalade ! src/windows/classes/sun/awt/shell/Win32ShellFolder2.java ! src/windows/classes/sun/awt/shell/Win32ShellFolderManager2.java Changeset: b20936547ff0 Author: kaddepalli Date: 2018-07-16 13:10 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/b20936547ff0 8207336: Build failure in JDK8u on Windows after fix 8207260 Reviewed-by: prr ! src/windows/classes/sun/awt/shell/Win32ShellFolder2.java Changeset: 0f1788a16d65 Author: robm Date: 2018-07-18 16:37 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/0f1788a16d65 8196902: Better HTTP redirection support Reviewed-by: michaelm ! src/share/classes/sun/net/www/protocol/http/HttpURLConnection.java + test/lib/testlibrary/jdk/testlibrary/testkeys Changeset: ee20d1e68661 Author: igerasim Date: 2018-07-23 21:34 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/ee20d1e68661 8206295: More reliable p11 transactions Reviewed-by: valeriep, mschoene, rhalade ! src/windows/native/sun/security/pkcs11/wrapper/p11_md.c Changeset: 6a83c2f66345 Author: dtitov Date: 2018-07-25 13:39 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/6a83c2f66345 8205709: Proper allocation handling Reviewed-by: sspitsyn ! src/solaris/instrument/FileSystemSupport_md.c ! src/windows/instrument/FileSystemSupport_md.c Changeset: 243d316d676e Author: igerasim Date: 2018-07-26 04:36 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/243d316d676e 8206301: Improve NIO stability Reviewed-by: alanb, mschoene, rhalade ! src/windows/native/sun/nio/ch/DatagramDispatcher.c ! src/windows/native/sun/nio/ch/WindowsSelectorImpl.c Changeset: 873a1ee5d832 Author: aefimov Date: 2018-07-27 11:49 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/873a1ee5d832 Merge ! .hgtags Changeset: f17e14ea697a Author: prr Date: 2018-08-01 11:16 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f17e14ea697a 8208353: Upgrade JDK 8u to libpng 1.6.35 Reviewed-by: serb, jdv ! src/share/native/sun/awt/libpng/CHANGES ! src/share/native/sun/awt/libpng/LICENSE ! src/share/native/sun/awt/libpng/README ! src/share/native/sun/awt/libpng/png.c ! src/share/native/sun/awt/libpng/png.h ! src/share/native/sun/awt/libpng/pngconf.h ! src/share/native/sun/awt/libpng/pngerror.c ! src/share/native/sun/awt/libpng/pngget.c ! src/share/native/sun/awt/libpng/pnginfo.h ! src/share/native/sun/awt/libpng/pnglibconf.h ! src/share/native/sun/awt/libpng/pngpread.c ! src/share/native/sun/awt/libpng/pngpriv.h ! src/share/native/sun/awt/libpng/pngread.c ! src/share/native/sun/awt/libpng/pngrio.c ! src/share/native/sun/awt/libpng/pngrtran.c ! src/share/native/sun/awt/libpng/pngrutil.c ! src/share/native/sun/awt/libpng/pngset.c ! src/share/native/sun/awt/libpng/pngstruct.h ! src/share/native/sun/awt/libpng/pngtrans.c Changeset: e222c45022e7 Author: aefimov Date: 2018-08-04 12:38 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/e222c45022e7 Merge ! .hgtags Changeset: d42dc38b9397 Author: igerasim Date: 2018-08-08 00:32 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/d42dc38b9397 8208754: The fix for JDK-8194534 needs updates Reviewed-by: alanb, igerasim, rhalade, mullan ! src/share/classes/java/util/jar/JarFile.java ! src/share/classes/java/util/jar/JavaUtilJarAccessImpl.java ! src/share/classes/java/util/jar/Manifest.java ! src/share/classes/sun/misc/JavaUtilJarAccess.java ! src/share/classes/sun/misc/URLClassPath.java Changeset: 068a57a8bd8c Author: ljiang Date: 2018-08-08 01:46 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/068a57a8bd8c 8208660: JDK 8u191 l10n resource file update Reviewed-by: coffeys ! src/share/classes/com/sun/rowset/RowSetResourceBundle_de.properties ! src/share/classes/sun/rmi/registry/resources/rmiregistry_it.properties ! src/share/classes/sun/rmi/server/resources/rmid_it.properties ! src/share/classes/sun/security/tools/jarsigner/Resources_ja.java ! src/share/classes/sun/security/tools/jarsigner/Resources_zh_CN.java Changeset: d3a211e0cced Author: aefimov Date: 2018-08-10 13:23 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/d3a211e0cced Merge ! .hgtags Changeset: b965edac64ad Author: igerasim Date: 2018-08-15 12:12 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/b965edac64ad 8199156: Better route routing Reviewed-by: igerasim, mschoene, michaelm, rhalade ! src/solaris/native/java/net/net_util_md.c Changeset: f1f6a6508eb1 Author: igerasim Date: 2018-08-15 12:13 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f1f6a6508eb1 8199161: Better interface enumeration Reviewed-by: igerasim, mschoene, michaelm, rhalade ! src/windows/native/java/net/NetworkInterface.c Changeset: 776a933c85ea Author: aefimov Date: 2018-08-18 13:03 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/776a933c85ea Merge ! .hgtags Changeset: 5ba4548478b8 Author: psadhukhan Date: 2018-08-21 11:43 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/5ba4548478b8 8205356: Choose printer defaults Reviewed-by: prr, mschoene, rhalade ! src/windows/native/sun/windows/WPrinterJob.cpp Changeset: f8279bb6639f Author: serb Date: 2018-08-21 17:18 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f8279bb6639f 8203955: Improve robot support Reviewed-by: prr, psadhukhan, rhalade, skoivu ! src/share/classes/java/awt/Robot.java Changeset: b63702f5cc12 Author: pkoppula Date: 2018-08-23 13:23 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/b63702f5cc12 8208350: Disable all DES cipher suites Reviewed-by: mullan, jnimeh, coffeys ! src/share/lib/security/java.security-aix ! src/share/lib/security/java.security-linux ! src/share/lib/security/java.security-macosx ! src/share/lib/security/java.security-solaris ! src/share/lib/security/java.security-windows ! test/sun/security/krb5/auto/UnboundSSL.java ! test/sun/security/krb5/auto/UnboundSSLMultipleKeys.java ! test/sun/security/krb5/auto/UnboundSSLPrincipalProperty.java ! test/sun/security/krb5/auto/unbound.ssl.policy + test/sun/security/ssl/CipherSuite/NoDesRC4CiphSuite.java ! test/sun/security/ssl/SSLContextImpl/CustomizedCipherSuites.java Changeset: 8796258816cd Author: coffeys Date: 2018-08-27 11:29 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/8796258816cd 8208585: Make crypto code more robust Reviewed-by: ascarpino, mschoene ! src/share/classes/com/sun/crypto/provider/RSACipher.java ! src/share/classes/sun/security/pkcs11/P11Signature.java ! src/share/classes/sun/security/provider/DSA.java ! src/windows/classes/sun/security/mscapi/RSASignature.java Changeset: 5efb6688cd9e Author: alitvinov Date: 2018-08-27 19:35 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/5efb6688cd9e Merge ! .hgtags Changeset: 891ef8bac57a Author: chegar Date: 2018-08-10 14:35 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/891ef8bac57a 8199166: Better interface lists Reviewed-by: igerasim, mschoene, michaelm, rhalade ! src/windows/native/java/net/NetworkInterface.c Changeset: 423d88f93de7 Author: alitvinov Date: 2018-09-03 16:55 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/423d88f93de7 Merge ! .hgtags Changeset: 3cf807ee638a Author: dmarkov Date: 2018-09-07 10:27 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/3cf807ee638a 8210431: Complete backport of libpng 1.6.35 TPRM Reviewed-by: jeff, prr ! THIRD_PARTY_README Changeset: d8b98efabf57 Author: alitvinov Date: 2018-09-10 19:37 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/d8b98efabf57 Merge ! .hgtags Changeset: c781c1726b62 Author: serb Date: 2018-09-10 19:31 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/c781c1726b62 8204895: Better icon support Reviewed-by: prr, mschoene, aghaisas, rhalade ! src/solaris/native/sun/awt/awt_UNIXToolkit.c Changeset: 2cf0eb69a288 Author: aefimov Date: 2018-09-17 15:06 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/2cf0eb69a288 Merge ! .hgtags Changeset: 01337312ad1e Author: igerasim Date: 2018-09-28 23:04 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/01337312ad1e 8206290: Better FileChannel transfer performance Reviewed-by: alanb, rhalade, mschoene ! src/share/classes/sun/nio/ch/FileChannelImpl.java Changeset: e787bb619c0b Author: serb Date: 2018-09-27 12:54 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/e787bb619c0b 8210598: Strengthen Windows Access Bridge Support Reviewed-by: prr, psadhukhan, rhalade, mschoene ! src/windows/native/sun/bridge/AccessBridgeMessageQueue.cpp Changeset: d1be3b42e6e8 Author: aefimov Date: 2018-07-02 16:39 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/d1be3b42e6e8 Merge ! .hgtags ! src/windows/native/sun/windows/awt_Component.cpp Changeset: 38b4a5b97f38 Author: rpatil Date: 2018-05-01 23:16 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/38b4a5b97f38 8195095: Images are not scaled correctly in JEditorPane Reviewed-by: ssadetsky, psadhukhan, mhalder ! src/share/classes/javax/swing/text/html/ImageView.java + test/javax/swing/JEditorPane/8195095/ImageViewTest.java + test/javax/swing/JEditorPane/8195095/circle.png Changeset: 6401289e4972 Author: diazhou Date: 2018-07-04 02:06 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/6401289e4972 Added tag jdk8u181-b31 for changeset 38b4a5b97f38 ! .hgtags Changeset: d679861a9a1e Author: aefimov Date: 2018-07-11 00:27 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/d679861a9a1e Merge ! .hgtags Changeset: 470cc4680c5e Author: diazhou Date: 2018-07-11 22:54 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/470cc4680c5e Added tag jdk8u181-b32 for changeset d679861a9a1e ! .hgtags Changeset: 078a06936ffe Author: rpatil Date: 2018-07-06 13:45 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/078a06936ffe 8202696: Remove exclusion range for phonetic chars in windows fontconfig.properties Reviewed-by: prr, naoto Contributed-by: dipak.kumar at oracle.com ! src/windows/classes/sun/awt/windows/fontconfig.properties + test/java/awt/font/PhoneticExtensions/PhoneticExtensionsGlyphTest.java Changeset: b4ceaa1adb22 Author: diazhou Date: 2018-07-24 13:17 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/b4ceaa1adb22 Added tag jdk8u181-b33 for changeset 078a06936ffe ! .hgtags Changeset: e5547489e33b Author: coffeys Date: 2018-08-03 14:34 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/e5547489e33b 8208583: Better management of internal KeyStore buffers 8207775: Better management of CipherCore buffers Reviewed-by: weijun, ascarpino ! src/share/classes/com/sun/crypto/provider/CipherCore.java ! src/share/classes/com/sun/crypto/provider/KeyProtector.java ! src/share/classes/com/sun/crypto/provider/PBEKey.java ! src/share/classes/javax/crypto/spec/PBEKeySpec.java ! src/share/classes/sun/security/provider/JavaKeyStore.java ! src/share/classes/sun/security/provider/KeyProtector.java Changeset: ecfdede1e6dd Author: coffeys Date: 2018-08-24 09:50 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/ecfdede1e6dd 8209129: Further improvements to cipher buffer management Reviewed-by: weijun, igerasim ! src/share/classes/com/sun/crypto/provider/HmacPKCS12PBESHA1.java ! src/share/classes/com/sun/crypto/provider/KeyProtector.java ! src/share/classes/com/sun/crypto/provider/PBEKey.java ! src/share/classes/com/sun/crypto/provider/PBES1Core.java ! src/share/classes/com/sun/crypto/provider/PBES2Core.java ! src/share/classes/com/sun/crypto/provider/PBKDF2KeyImpl.java ! src/share/classes/com/sun/crypto/provider/PBMAC1Core.java ! src/share/classes/com/sun/crypto/provider/PKCS12PBECipherCore.java ! src/share/classes/sun/security/provider/DigestBase.java ! src/share/classes/sun/security/provider/MD4.java ! src/share/classes/sun/security/provider/MD5.java ! src/share/classes/sun/security/provider/SHA.java ! src/share/classes/sun/security/provider/SHA2.java ! src/share/classes/sun/security/provider/SHA5.java ! test/com/sun/crypto/provider/Cipher/PBE/PKCS12Cipher.java Changeset: 31bc93543f98 Author: diazhou Date: 2018-08-27 01:51 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/31bc93543f98 Added tag jdk8u181-b34 for changeset ecfdede1e6dd ! .hgtags Changeset: ac943243eaf1 Author: alitvinov Date: 2018-08-30 17:44 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/ac943243eaf1 8201818: [macosx] Printing attributes break page size set via "java.awt.print.Book" object Reviewed-by: prr, psadhukhan ! src/share/classes/sun/print/RasterPrinterJob.java + test/java/awt/print/PageFormat/WrongPaperForBookPrintingTest.java Changeset: 674963395b9f Author: diazhou Date: 2018-09-10 14:06 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/674963395b9f Added tag jdk8u181-b35 for changeset ac943243eaf1 ! .hgtags Changeset: c76b8fd5fa12 Author: diazhou Date: 2018-09-24 19:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/c76b8fd5fa12 Added tag jdk8u181-b36 for changeset 674963395b9f ! .hgtags Changeset: 4d34e8d3d971 Author: aefimov Date: 2018-09-26 15:31 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/4d34e8d3d971 Merge ! .hgtags Changeset: 8f2bdd3d7752 Author: aefimov Date: 2018-09-30 18:26 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/8f2bdd3d7752 Merge Changeset: dad8da6f3cdf Author: aefimov Date: 2018-09-30 20:03 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/dad8da6f3cdf Merge ! .hgtags Changeset: 92587df93360 Author: pkoppula Date: 2018-10-02 21:38 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/92587df93360 8211107: LDAPS communication failure with jdk 1.8.0_181 Reviewed-by: chegar, coffeys, vtewari ! src/share/classes/com/sun/jndi/ldap/Connection.java Changeset: b59df3ee7ad5 Author: diazhou Date: 2018-10-04 02:47 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/b59df3ee7ad5 Added tag jdk8u181-b37 for changeset 92587df93360 ! .hgtags Changeset: 3e9d9329d614 Author: aefimov Date: 2018-10-05 16:53 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/3e9d9329d614 Merge ! .hgtags Changeset: 716ebc3075cc Author: prr Date: 2018-10-05 11:37 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/716ebc3075cc 8210606: Improved data set handling Reviewed-by: serb, psadhukhan, mschoene, rhalade ! src/share/native/sun/java2d/cmm/lcms/cmscgats.c Changeset: 115ffd47a28d Author: igerasim Date: 2018-10-05 17:33 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/115ffd47a28d 8211731: Reconsider default option for ClassPathURLCheck change done in JDK-8195874 Reviewed-by: alanb, mchung ! src/share/classes/sun/misc/URLClassPath.java Changeset: efdd31c24528 Author: igerasim Date: 2018-10-06 12:27 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/efdd31c24528 8210610: Improved LSA authentication Reviewed-by: valeriep, mschoene, rhalade ! src/windows/native/sun/security/krb5/NativeCreds.c Changeset: e2f366716adf Author: aefimov Date: 2018-10-08 21:55 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/e2f366716adf Merge ! .hgtags Changeset: baa7a736796b Author: prr Date: 2018-10-08 15:24 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/baa7a736796b 8210866: Improve JPEG processing Reviewed-by: serb, psadhukhan, rhalade ! src/share/native/sun/awt/image/jpeg/jmemmgr.c Changeset: d0d0b71e3a2a Author: igerasim Date: 2018-10-08 16:51 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/d0d0b71e3a2a 8209094: Improve web server connections Reviewed-by: chegar, dfuchs, mschoene, igerasim ! make/lib/NetworkingLibraries.gmk ! src/share/classes/sun/net/www/protocol/http/ntlm/NTLMAuthenticationCallback.java ! src/share/lib/net.properties ! src/solaris/classes/sun/net/www/protocol/http/ntlm/NTLMAuthentication.java ! src/windows/classes/sun/net/www/protocol/http/ntlm/NTLMAuthentication.java + src/windows/native/sun/net/www/protocol/http/ntlm/NTLMAuthentication.c Changeset: 21e476bfaa0b Author: igerasim Date: 2018-10-09 15:59 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/21e476bfaa0b 8191438: jarsigner should print when a timestamp will expire 8027781: New jarsigner timestamp warning is grammatically incorrect 8159805: sun/security/tools/jarsigner/warnings/NoTimestampTest.java fails after JDK-8027781 Reviewed-by: weijun, coffeys, mullan ! src/share/classes/sun/security/tools/jarsigner/Main.java ! src/share/classes/sun/security/tools/jarsigner/Resources.java ! test/sun/security/tools/jarsigner/TimestampCheck.java ! test/sun/security/tools/jarsigner/warnings/AliasNotInStoreTest.java ! test/sun/security/tools/jarsigner/warnings/BadExtendedKeyUsageTest.java ! test/sun/security/tools/jarsigner/warnings/BadKeyUsageTest.java ! test/sun/security/tools/jarsigner/warnings/BadNetscapeCertTypeTest.java ! test/sun/security/tools/jarsigner/warnings/ChainNotValidatedTest.java ! test/sun/security/tools/jarsigner/warnings/HasExpiredCertTest.java ! test/sun/security/tools/jarsigner/warnings/HasExpiringCertTest.java ! test/sun/security/tools/jarsigner/warnings/HasUnsignedEntryTest.java ! test/sun/security/tools/jarsigner/warnings/MultipleWarningsTest.java ! test/sun/security/tools/jarsigner/warnings/NoTimestampTest.java ! test/sun/security/tools/jarsigner/warnings/NotSignedByAliasTest.java ! test/sun/security/tools/jarsigner/warnings/NotYetValidCertTest.java ! test/sun/security/tools/jarsigner/warnings/Test.java - test/sun/security/tools/jarsigner/warnings/bad_netscape_cert_type.jks.base64 - test/sun/security/tools/jarsigner/warnings/bad_netscape_cert_type.sh Changeset: 2369004fc551 Author: igerasim Date: 2018-10-09 16:01 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/2369004fc551 8210870: Libsunmscapi improved interactions Reviewed-by: valeriep, mschoene, rhalade ! src/windows/classes/sun/security/mscapi/KeyStore.java ! src/windows/native/sun/security/mscapi/security.cpp Changeset: fbc886dd68cc Author: igerasim Date: 2018-10-09 21:31 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/fbc886dd68cc 8200659: Improve BigDecimal support Reviewed-by: darcy, rhalade, mschoene ! src/share/classes/java/math/BigDecimal.java ! src/share/classes/java/math/BigInteger.java ! test/java/math/BigDecimal/AddTests.java ! test/java/math/BigDecimal/Constructor.java + test/java/math/BigInteger/LargeValueExceptions.java Changeset: fbeb9b9cc010 Author: diazhou Date: 2018-10-17 04:42 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/fbeb9b9cc010 Added tag jdk8u201-b01 for changeset fbc886dd68cc ! .hgtags Changeset: 274162fd9a23 Author: diazhou Date: 2018-11-01 16:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/274162fd9a23 Added tag jdk8u201-b02 for changeset fbeb9b9cc010 ! .hgtags Changeset: 02cfe7f5d619 Author: diazhou Date: 2018-11-07 04:26 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/02cfe7f5d619 Added tag jdk8u201-b03 for changeset 274162fd9a23 ! .hgtags Changeset: e146b597c4da Author: pkoppula Date: 2018-10-30 11:06 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/e146b597c4da 8211883: Disable anon and NULL cipher suites Reviewed-by: mullan, coffeys ! src/share/lib/security/java.security-aix ! src/share/lib/security/java.security-linux ! src/share/lib/security/java.security-macosx ! src/share/lib/security/java.security-solaris ! src/share/lib/security/java.security-windows ! test/javax/net/ssl/ciphersuites/DisabledAlgorithms.java ! test/sun/security/ssl/SSLContextImpl/CustomizedCipherSuites.java ! test/sun/security/ssl/javax/net/ssl/NewAPIs/JSSERenegotiate.java Changeset: 4c9887a0167f Author: ljiang Date: 2018-11-07 19:02 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/4c9887a0167f 8213368: JDK 8u201 l10n resource file update Reviewed-by: coffeys ! src/share/classes/sun/security/tools/jarsigner/Resources_ja.java ! src/share/classes/sun/security/tools/jarsigner/Resources_zh_CN.java ! src/share/classes/sun/security/util/Resources_sv.java Changeset: c0b2b82d2478 Author: coffeys Date: 2018-10-15 14:42 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/c0b2b82d2478 8209862: CipherCore performance improvement Reviewed-by: apetcher, ascarpino Contributed-by: sergey.kuksenko at oracle.com, sean.coffey at oracle.com ! src/share/classes/com/sun/crypto/provider/CipherCore.java Changeset: 3d28c8134ca1 Author: diazhou Date: 2018-11-14 10:18 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/3d28c8134ca1 Added tag jdk8u201-b04 for changeset c0b2b82d2478 ! .hgtags Changeset: df3e701ab076 Author: diazhou Date: 2018-11-14 11:12 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/df3e701ab076 Added tag jdk8u201-b74 for changeset 3d28c8134ca1 ! .hgtags Changeset: 9fe667a8402b Author: diazhou Date: 2018-11-19 03:07 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/9fe667a8402b Added tag jdk8u201-b05 for changeset df3e701ab076 ! .hgtags Changeset: 5c2a0076c144 Author: diazhou Date: 2018-11-22 09:33 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/5c2a0076c144 Added tag jdk8u201-b75 for changeset 9fe667a8402b ! .hgtags Changeset: 3cb43f3afe1c Author: rpatil Date: 2018-11-12 14:13 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/3cb43f3afe1c 8171049: Era.getDisplayName doesn't work with non-IsoChronology Reviewed-by: naoto Contributed-by: deepak.kejriwal at oracle.com ! src/share/classes/java/time/chrono/HijrahEra.java ! src/share/classes/java/time/chrono/JapaneseEra.java ! src/share/classes/java/time/chrono/MinguoEra.java ! src/share/classes/java/time/chrono/ThaiBuddhistEra.java + test/java/time/test/java/time/chrono/TestEraDisplayName.java Changeset: dc2aeed27f71 Author: rpatil Date: 2018-11-20 11:25 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/dc2aeed27f71 8213085: (tz) Upgrade time-zone data to tzdata2018g Reviewed-by: martin, naoto ! make/data/tzdata/VERSION ! make/data/tzdata/africa ! make/data/tzdata/antarctica ! make/data/tzdata/asia ! make/data/tzdata/australasia ! make/data/tzdata/backward ! make/data/tzdata/etcetera ! make/data/tzdata/europe ! make/data/tzdata/factory ! make/data/tzdata/leapseconds ! make/data/tzdata/northamerica ! make/data/tzdata/pacificnew ! make/data/tzdata/southamerica ! make/data/tzdata/systemv ! make/data/tzdata/zone.tab ! 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/tzdata/VERSION ! test/sun/util/calendar/zi/tzdata/africa ! test/sun/util/calendar/zi/tzdata/antarctica ! test/sun/util/calendar/zi/tzdata/asia ! test/sun/util/calendar/zi/tzdata/australasia ! test/sun/util/calendar/zi/tzdata/backward ! test/sun/util/calendar/zi/tzdata/etcetera ! test/sun/util/calendar/zi/tzdata/europe ! test/sun/util/calendar/zi/tzdata/factory ! test/sun/util/calendar/zi/tzdata/leapseconds ! test/sun/util/calendar/zi/tzdata/northamerica ! test/sun/util/calendar/zi/tzdata/pacificnew ! test/sun/util/calendar/zi/tzdata/southamerica ! test/sun/util/calendar/zi/tzdata/systemv ! test/sun/util/calendar/zi/tzdata/zone.tab Changeset: a1845b252425 Author: diazhou Date: 2018-11-27 09:16 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/a1845b252425 Added tag jdk8u201-b06 for changeset dc2aeed27f71 ! .hgtags Changeset: f01ae4e6d43b Author: diazhou Date: 2018-11-27 10:22 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f01ae4e6d43b Added tag jdk8u201-b76 for changeset a1845b252425 ! .hgtags Changeset: e1248fad4564 Author: alitvinov Date: 2018-11-28 13:50 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/e1248fad4564 8213792: Update THIRTD_PARTY_README for LCMS to 2.9 Reviewed-by: prr ! THIRD_PARTY_README Changeset: c1ca2d51fbba Author: robm Date: 2018-10-05 14:10 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/c1ca2d51fbba 8205330: InitialDirContext ctor sometimes throws NPE if the server has sent a disconnection Reviewed-by: chegar, dfuchs ! src/share/classes/com/sun/jndi/ldap/LdapClient.java Changeset: fd2d4cb4ff1a Author: robm Date: 2018-10-05 14:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/fd2d4cb4ff1a 8210695: Create test to cover JDK-8205330 InitialDirContext ctor sometimes throws NPE if the server has sent a disconnection Reviewed-by: vtewari, dfuchs, chegar, coffeys + test/com/sun/jndi/ldap/DisconnectNPETest.java Changeset: 0a19f694c42c Author: dbuck Date: 2018-12-03 07:31 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/0a19f694c42c 8141491: Unaligned memory access in Bits.c Summary: Introduce alignment-safe Copy::conjoint_swap and JVM_CopySwapMemory Reviewed-by: mikael, dholmes ! make/mapfiles/libjava/mapfile-vers ! src/share/classes/java/nio/Bits.java ! src/share/javavm/export/jvm.h ! src/share/native/java/nio/Bits.c Changeset: f0611120a4b7 Author: diazhou Date: 2018-12-05 19:23 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/f0611120a4b7 Added tag jdk8u201-b07 for changeset 0a19f694c42c ! .hgtags Changeset: 21ffcdd4d850 Author: diazhou Date: 2018-12-05 19:45 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/21ffcdd4d850 Added tag jdk8u201-b77 for changeset f0611120a4b7 ! .hgtags Changeset: 12f1eb1d224b Author: diazhou Date: 2018-12-12 00:00 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/12f1eb1d224b Added tag jdk8u201-b08 for changeset 21ffcdd4d850 ! .hgtags Changeset: 8aec97b9b658 Author: aivanov Date: 2018-12-14 12:32 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/8aec97b9b658 8213949: OpenJDK 8 CCharToGlyphMapper.m missing the Classpath exception license text Reviewed-by: coffeys ! src/macosx/native/sun/font/CCharToGlyphMapper.m Changeset: 72a1a252527b Author: rpatil Date: 2018-12-14 18:11 +0530 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/72a1a252527b 8215377: JDK-8171049 Breaks JCK signature tests - Era.getDisplayName doesn't work with non-IsoChronology Reviewed-by: coffeys, rpatil Contributed-by: Deepak kejriwal ! src/share/classes/java/time/chrono/HijrahEra.java ! src/share/classes/java/time/chrono/MinguoEra.java ! src/share/classes/java/time/chrono/ThaiBuddhistEra.java ! test/java/time/test/java/time/chrono/TestEraDisplayName.java Changeset: b83b9dd3cef7 Author: andrew Date: 2019-02-26 00:54 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/b83b9dd3cef7 Merge jdk8u201-ga ! .hgtags ! THIRD_PARTY_README ! make/data/tzdata/VERSION ! make/data/tzdata/africa ! make/data/tzdata/antarctica ! make/data/tzdata/asia ! make/data/tzdata/australasia ! make/data/tzdata/backward ! make/data/tzdata/etcetera ! make/data/tzdata/europe ! make/data/tzdata/leapseconds ! make/data/tzdata/northamerica ! make/data/tzdata/southamerica ! make/data/tzdata/zone.tab ! make/lib/NetworkingLibraries.gmk ! make/mapfiles/libjava/mapfile-vers ! src/share/classes/com/sun/crypto/provider/CipherCore.java ! src/share/classes/com/sun/crypto/provider/PBES1Core.java ! src/share/classes/java/math/BigDecimal.java ! src/share/classes/java/math/BigInteger.java ! src/share/classes/java/nio/Bits.java ! src/share/classes/java/time/chrono/MinguoEra.java ! src/share/classes/java/time/chrono/ThaiBuddhistEra.java ! src/share/classes/sun/nio/ch/FileChannelImpl.java ! src/share/classes/sun/print/RasterPrinterJob.java ! src/share/classes/sun/security/provider/DSA.java ! src/share/classes/sun/security/provider/MD4.java ! src/share/classes/sun/security/tools/jarsigner/Main.java ! src/share/classes/sun/security/tools/jarsigner/Resources_ja.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 ! src/share/javavm/export/jvm.h ! src/share/lib/security/java.security-aix ! src/share/lib/security/java.security-linux ! src/share/lib/security/java.security-macosx ! src/share/lib/security/java.security-solaris ! src/share/lib/security/java.security-windows ! src/solaris/native/java/net/net_util_md.c ! src/solaris/native/sun/awt/awt_UNIXToolkit.c ! src/windows/native/java/net/NetworkInterface.c ! src/windows/native/sun/security/krb5/NativeCreds.c ! test/sun/security/tools/jarsigner/TimestampCheck.java ! test/sun/security/tools/jarsigner/warnings/Test.java ! test/sun/util/calendar/zi/tzdata/VERSION ! test/sun/util/calendar/zi/tzdata/africa ! test/sun/util/calendar/zi/tzdata/antarctica ! test/sun/util/calendar/zi/tzdata/asia ! test/sun/util/calendar/zi/tzdata/australasia ! test/sun/util/calendar/zi/tzdata/backward ! test/sun/util/calendar/zi/tzdata/etcetera ! test/sun/util/calendar/zi/tzdata/europe ! test/sun/util/calendar/zi/tzdata/leapseconds ! test/sun/util/calendar/zi/tzdata/northamerica ! test/sun/util/calendar/zi/tzdata/southamerica ! test/sun/util/calendar/zi/tzdata/zone.tab Changeset: cd6d36be7ef6 Author: andrew Date: 2019-02-26 00:56 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jdk/rev/cd6d36be7ef6 Added tag aarch64-shenandoah-jdk8u201-b12 for changeset b83b9dd3cef7 ! .hgtags From gnu.andrew at redhat.com Tue Feb 26 21:55:49 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 26 Feb 2019 21:55:49 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/nashorn: 45 new changesets Message-ID: <201902262155.x1QLtn5a008270@aojmv0008.oracle.com> Changeset: 27ffcec111b3 Author: andrew Date: 2019-02-25 05:10 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/27ffcec111b3 Added tag aarch64-shenandoah-jdk8u201-b11 for changeset d122e4b8d88b ! .hgtags Changeset: 6aeb5e07e2bb Author: diazhou Date: 2018-10-06 05:12 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/6aeb5e07e2bb Added tag jdk8u192-b12 for changeset 854c8339d414 ! .hgtags Changeset: 0433c06d29e2 Author: diazhou Date: 2018-10-08 10:55 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/0433c06d29e2 Added tag jdk8u192-b26 for changeset 6aeb5e07e2bb ! .hgtags Changeset: a53a027482b0 Author: diazhou Date: 2018-10-06 04:40 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/a53a027482b0 Added tag jdk8u191-b12 for changeset 5a2c3b3dd919 ! .hgtags Changeset: d486cd6d71cd Author: diazhou Date: 2018-10-08 10:20 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/d486cd6d71cd Added tag jdk8u191-b26 for changeset a53a027482b0 ! .hgtags Changeset: 2898ce9aa0b0 Author: aefimov Date: 2018-10-08 20:48 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/2898ce9aa0b0 Merge ! .hgtags Changeset: 14e03c335d77 Author: aefimov Date: 2018-07-11 15:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/14e03c335d77 Added tag jdk8u201-b00 for changeset 9bae2c31c00b ! .hgtags Changeset: bba4a022ab02 Author: aefimov Date: 2018-07-27 11:51 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/bba4a022ab02 Merge ! .hgtags Changeset: 0db74627bade Author: aefimov Date: 2018-08-04 12:55 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/0db74627bade Merge ! .hgtags Changeset: bab27d12d61c Author: aefimov Date: 2018-08-10 13:23 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/bab27d12d61c Merge ! .hgtags Changeset: aed3fb12807d Author: aefimov Date: 2018-08-18 13:05 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/aed3fb12807d Merge ! .hgtags Changeset: 22ba2dc03cf2 Author: alitvinov Date: 2018-08-24 19:36 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/22ba2dc03cf2 Merge ! .hgtags Changeset: 513fc74e0d31 Author: alitvinov Date: 2018-09-03 16:57 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/513fc74e0d31 Merge ! .hgtags Changeset: d8eac22ef102 Author: dmarkov Date: 2018-09-07 10:31 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/d8eac22ef102 8210431: Complete backport of libpng 1.6.35 TPRM Reviewed-by: jeff, prr ! THIRD_PARTY_README Changeset: 929981a56ef3 Author: alitvinov Date: 2018-09-10 19:40 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/929981a56ef3 Merge ! .hgtags Changeset: ff52e06bbf56 Author: aefimov Date: 2018-09-17 15:07 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/ff52e06bbf56 Merge ! .hgtags Changeset: 6c92477c026d Author: aefimov Date: 2018-07-02 16:43 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/6c92477c026d Merge ! .hgtags Changeset: 7525dd11e053 Author: diazhou Date: 2018-07-04 02:07 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/7525dd11e053 Added tag jdk8u181-b31 for changeset 6c92477c026d ! .hgtags Changeset: 81cd7926a046 Author: aefimov Date: 2018-07-11 00:30 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/81cd7926a046 Merge ! .hgtags Changeset: bfdef7c90540 Author: diazhou Date: 2018-07-11 22:54 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/bfdef7c90540 Added tag jdk8u181-b32 for changeset 81cd7926a046 ! .hgtags Changeset: 7a321d516a54 Author: diazhou Date: 2018-07-24 13:17 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/7a321d516a54 Added tag jdk8u181-b33 for changeset bfdef7c90540 ! .hgtags Changeset: 49f6984c82a5 Author: diazhou Date: 2018-08-27 01:52 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/49f6984c82a5 Added tag jdk8u181-b34 for changeset 7a321d516a54 ! .hgtags Changeset: 5d35a3a61a5b Author: diazhou Date: 2018-09-10 14:06 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/5d35a3a61a5b Added tag jdk8u181-b35 for changeset 49f6984c82a5 ! .hgtags Changeset: 9a5ee25a4770 Author: diazhou Date: 2018-09-24 19:12 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/9a5ee25a4770 Added tag jdk8u181-b36 for changeset 5d35a3a61a5b ! .hgtags Changeset: c9399828ce4f Author: aefimov Date: 2018-09-26 15:36 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/c9399828ce4f Merge ! .hgtags Changeset: 7cda9da788a7 Author: aefimov Date: 2018-09-30 20:06 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/7cda9da788a7 Merge ! .hgtags Changeset: ae0ce3316919 Author: diazhou Date: 2018-10-04 02:47 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/ae0ce3316919 Added tag jdk8u181-b37 for changeset 9a5ee25a4770 ! .hgtags Changeset: 6b03ea6e622d Author: aefimov Date: 2018-10-05 16:54 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/6b03ea6e622d Merge ! .hgtags Changeset: 9be9b86d06c6 Author: aefimov Date: 2018-10-08 21:57 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/9be9b86d06c6 Merge ! .hgtags Changeset: 43c64cf865d4 Author: diazhou Date: 2018-10-17 04:42 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/43c64cf865d4 Added tag jdk8u201-b01 for changeset 9be9b86d06c6 ! .hgtags Changeset: 6bd999d631dd Author: diazhou Date: 2018-11-01 16:12 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/6bd999d631dd Added tag jdk8u201-b02 for changeset 43c64cf865d4 ! .hgtags Changeset: e81bdfaa81e0 Author: diazhou Date: 2018-11-07 04:26 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/e81bdfaa81e0 Added tag jdk8u201-b03 for changeset 6bd999d631dd ! .hgtags Changeset: 95bf544c9cb6 Author: diazhou Date: 2018-11-14 10:18 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/95bf544c9cb6 Added tag jdk8u201-b04 for changeset e81bdfaa81e0 ! .hgtags Changeset: b27416532dba Author: diazhou Date: 2018-11-14 11:12 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/b27416532dba Added tag jdk8u201-b74 for changeset 95bf544c9cb6 ! .hgtags Changeset: 112dfb97c1e4 Author: diazhou Date: 2018-11-19 03:07 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/112dfb97c1e4 Added tag jdk8u201-b05 for changeset b27416532dba ! .hgtags Changeset: 9e720dd55a3a Author: diazhou Date: 2018-11-22 09:33 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/9e720dd55a3a Added tag jdk8u201-b75 for changeset 112dfb97c1e4 ! .hgtags Changeset: a430c68aabf0 Author: diazhou Date: 2018-11-27 09:16 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/a430c68aabf0 Added tag jdk8u201-b06 for changeset 9e720dd55a3a ! .hgtags Changeset: a66eb9bdafa5 Author: diazhou Date: 2018-11-27 10:23 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/a66eb9bdafa5 Added tag jdk8u201-b76 for changeset a430c68aabf0 ! .hgtags Changeset: 8bf098c9d21b Author: alitvinov Date: 2018-11-28 13:52 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/8bf098c9d21b 8213792: Update THIRTD_PARTY_README for LCMS to 2.9 Reviewed-by: prr ! THIRD_PARTY_README Changeset: 38568172fbdd Author: diazhou Date: 2018-12-05 19:24 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/38568172fbdd Added tag jdk8u201-b07 for changeset 8bf098c9d21b ! .hgtags Changeset: 03dc179691c8 Author: diazhou Date: 2018-12-05 19:45 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/03dc179691c8 Added tag jdk8u201-b77 for changeset 38568172fbdd ! .hgtags Changeset: e9a53cb7ea94 Author: diazhou Date: 2018-12-12 00:00 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/e9a53cb7ea94 Added tag jdk8u201-b08 for changeset 03dc179691c8 ! .hgtags Changeset: bf5c40b0e9d8 Author: rpatil Date: 2018-12-13 21:40 -1200 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/bf5c40b0e9d8 8215257: OpenJDK 8 mozilla_compat.js, parser.js missing the Classpath exception license text Reviewed-by: coffeys ! src/jdk/nashorn/internal/runtime/resources/mozilla_compat.js ! src/jdk/nashorn/internal/runtime/resources/parser.js ! test/script/trusted/classfilter_mozilla_compat.js.EXPECTED Changeset: 7f1809872362 Author: andrew Date: 2019-02-26 00:54 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/7f1809872362 Merge jdk8u201-ga ! .hgtags ! THIRD_PARTY_README Changeset: 03685f680d24 Author: andrew Date: 2019-02-26 00:56 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/nashorn/rev/03685f680d24 Added tag aarch64-shenandoah-jdk8u201-b12 for changeset 7f1809872362 ! .hgtags From gnu.andrew at redhat.com Tue Feb 26 21:55:06 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 26 Feb 2019 21:55:06 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/jaxws: 44 new changesets Message-ID: <201902262155.x1QLt7iO007793@aojmv0008.oracle.com> Changeset: 0996a641daac Author: andrew Date: 2019-02-25 05:10 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/0996a641daac Added tag aarch64-shenandoah-jdk8u201-b11 for changeset 3e946ddece16 ! .hgtags Changeset: b08cb2197601 Author: diazhou Date: 2018-10-06 05:12 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/b08cb2197601 Added tag jdk8u192-b12 for changeset 4b335cfde8d8 ! .hgtags Changeset: e6837b5db85b Author: diazhou Date: 2018-10-08 10:54 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/e6837b5db85b Added tag jdk8u192-b26 for changeset b08cb2197601 ! .hgtags Changeset: b0d7d6afebac Author: diazhou Date: 2018-10-06 04:40 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/b0d7d6afebac Added tag jdk8u191-b12 for changeset b32d94155990 ! .hgtags Changeset: 095255bc3038 Author: diazhou Date: 2018-10-08 10:19 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/095255bc3038 Added tag jdk8u191-b26 for changeset b0d7d6afebac ! .hgtags Changeset: 3bd0d58f0fcb Author: aefimov Date: 2018-10-08 20:45 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/3bd0d58f0fcb Merge ! .hgtags Changeset: 5335893e0e3d Author: aefimov Date: 2018-07-11 15:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/5335893e0e3d Added tag jdk8u201-b00 for changeset d25514e95cfb ! .hgtags Changeset: 7a02f53b06d7 Author: aefimov Date: 2018-07-27 11:49 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/7a02f53b06d7 Merge ! .hgtags Changeset: ebae66c44cf6 Author: aefimov Date: 2018-08-04 12:54 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/ebae66c44cf6 Merge ! .hgtags Changeset: 54cc897bdf03 Author: aefimov Date: 2018-08-10 13:21 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/54cc897bdf03 Merge ! .hgtags Changeset: 00ca0594e6ca Author: aefimov Date: 2018-08-18 13:03 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/00ca0594e6ca Merge ! .hgtags Changeset: abfb2192b65e Author: alitvinov Date: 2018-08-24 19:32 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/abfb2192b65e Merge ! .hgtags Changeset: 56876fc733b0 Author: alitvinov Date: 2018-09-03 16:55 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/56876fc733b0 Merge ! .hgtags Changeset: b6b359607584 Author: dmarkov Date: 2018-09-07 10:26 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/b6b359607584 8210431: Complete backport of libpng 1.6.35 TPRM Reviewed-by: jeff, prr ! THIRD_PARTY_README Changeset: c7a110937511 Author: alitvinov Date: 2018-09-10 19:37 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/c7a110937511 Merge ! .hgtags Changeset: 2bf993b7d898 Author: aefimov Date: 2018-09-17 15:06 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/2bf993b7d898 Merge ! .hgtags Changeset: 5e461ff70eb5 Author: aefimov Date: 2018-07-02 16:36 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/5e461ff70eb5 Merge ! .hgtags Changeset: 4f7dc7544468 Author: diazhou Date: 2018-07-04 02:06 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/4f7dc7544468 Added tag jdk8u181-b31 for changeset 5e461ff70eb5 ! .hgtags Changeset: 0863510c03b3 Author: aefimov Date: 2018-07-11 00:26 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/0863510c03b3 Merge ! .hgtags Changeset: 334e595ce7f8 Author: diazhou Date: 2018-07-11 22:53 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/334e595ce7f8 Added tag jdk8u181-b32 for changeset 0863510c03b3 ! .hgtags Changeset: fae6db55e87d Author: diazhou Date: 2018-07-24 13:17 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/fae6db55e87d Added tag jdk8u181-b33 for changeset 334e595ce7f8 ! .hgtags Changeset: b902d38c0248 Author: diazhou Date: 2018-08-27 01:51 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/b902d38c0248 Added tag jdk8u181-b34 for changeset fae6db55e87d ! .hgtags Changeset: cca9c1360a2b Author: diazhou Date: 2018-09-10 14:06 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/cca9c1360a2b Added tag jdk8u181-b35 for changeset b902d38c0248 ! .hgtags Changeset: 33917cdb4dda Author: diazhou Date: 2018-09-24 19:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/33917cdb4dda Added tag jdk8u181-b36 for changeset cca9c1360a2b ! .hgtags Changeset: 74c6adabf6d1 Author: aefimov Date: 2018-09-26 15:30 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/74c6adabf6d1 Merge ! .hgtags Changeset: ba84c4a29cd1 Author: aefimov Date: 2018-09-30 20:03 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/ba84c4a29cd1 Merge ! .hgtags Changeset: eacf0b8013a7 Author: diazhou Date: 2018-10-04 02:47 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/eacf0b8013a7 Added tag jdk8u181-b37 for changeset 33917cdb4dda ! .hgtags Changeset: 5467feec8914 Author: aefimov Date: 2018-10-05 16:53 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/5467feec8914 Merge ! .hgtags Changeset: 1ec054bb0782 Author: aefimov Date: 2018-10-08 21:54 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/1ec054bb0782 Merge ! .hgtags Changeset: aef7385318ae Author: diazhou Date: 2018-10-17 04:42 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/aef7385318ae Added tag jdk8u201-b01 for changeset 1ec054bb0782 ! .hgtags Changeset: db3500b8fe16 Author: diazhou Date: 2018-11-01 16:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/db3500b8fe16 Added tag jdk8u201-b02 for changeset aef7385318ae ! .hgtags Changeset: 830a687a30bf Author: diazhou Date: 2018-11-07 04:26 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/830a687a30bf Added tag jdk8u201-b03 for changeset db3500b8fe16 ! .hgtags Changeset: a65d21aa3c55 Author: diazhou Date: 2018-11-14 10:18 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/a65d21aa3c55 Added tag jdk8u201-b04 for changeset 830a687a30bf ! .hgtags Changeset: d1b19f1d6713 Author: diazhou Date: 2018-11-14 11:12 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/d1b19f1d6713 Added tag jdk8u201-b74 for changeset a65d21aa3c55 ! .hgtags Changeset: c8f4a6774b2b Author: diazhou Date: 2018-11-19 03:07 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/c8f4a6774b2b Added tag jdk8u201-b05 for changeset d1b19f1d6713 ! .hgtags Changeset: bf2d0accffad Author: diazhou Date: 2018-11-22 09:33 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/bf2d0accffad Added tag jdk8u201-b75 for changeset c8f4a6774b2b ! .hgtags Changeset: bb7ce3a38afb Author: diazhou Date: 2018-11-27 09:16 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/bb7ce3a38afb Added tag jdk8u201-b06 for changeset bf2d0accffad ! .hgtags Changeset: 0efffa86601e Author: diazhou Date: 2018-11-27 10:22 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/0efffa86601e Added tag jdk8u201-b76 for changeset bb7ce3a38afb ! .hgtags Changeset: 50f48f1d242d Author: alitvinov Date: 2018-11-28 13:50 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/50f48f1d242d 8213792: Update THIRTD_PARTY_README for LCMS to 2.9 Reviewed-by: prr ! THIRD_PARTY_README Changeset: 8396aa331353 Author: diazhou Date: 2018-12-05 19:23 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/8396aa331353 Added tag jdk8u201-b07 for changeset 50f48f1d242d ! .hgtags Changeset: 8485292c4700 Author: diazhou Date: 2018-12-05 19:45 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/8485292c4700 Added tag jdk8u201-b77 for changeset 8396aa331353 ! .hgtags Changeset: 05542ff5d183 Author: diazhou Date: 2018-12-12 00:00 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/05542ff5d183 Added tag jdk8u201-b08 for changeset 8485292c4700 ! .hgtags Changeset: 46cb5f89e0f8 Author: andrew Date: 2019-02-26 00:54 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/46cb5f89e0f8 Merge jdk8u201-ga ! .hgtags ! THIRD_PARTY_README Changeset: a2ebbab5648a Author: andrew Date: 2019-02-26 00:56 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/jaxws/rev/a2ebbab5648a Added tag aarch64-shenandoah-jdk8u201-b12 for changeset 46cb5f89e0f8 ! .hgtags From gnu.andrew at redhat.com Tue Feb 26 22:28:35 2019 From: gnu.andrew at redhat.com (gnu.andrew at redhat.com) Date: Tue, 26 Feb 2019 22:28:35 +0000 Subject: [aarch64-port-dev ] hg: aarch64-port/jdk8u-shenandoah/hotspot: 50 new changesets Message-ID: <201902262228.x1QMSZei020367@aojmv0008.oracle.com> Changeset: 24fe2c50cdb9 Author: andrew Date: 2019-02-25 05:10 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/24fe2c50cdb9 Added tag aarch64-shenandoah-jdk8u201-b11 for changeset f98005f3f634 ! .hgtags Changeset: e0e4c3a86ef0 Author: diazhou Date: 2018-10-06 05:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/e0e4c3a86ef0 Added tag jdk8u192-b12 for changeset 1f822ff877d1 ! .hgtags Changeset: 2d516bf3a0a9 Author: diazhou Date: 2018-10-08 10:54 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/2d516bf3a0a9 Added tag jdk8u192-b26 for changeset e0e4c3a86ef0 ! .hgtags Changeset: ab9258f7206e Author: diazhou Date: 2018-10-06 04:39 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/ab9258f7206e Added tag jdk8u191-b12 for changeset 4fc288749a23 ! .hgtags Changeset: b6bff4edabf1 Author: diazhou Date: 2018-10-08 10:19 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/b6bff4edabf1 Added tag jdk8u191-b26 for changeset ab9258f7206e ! .hgtags Changeset: 77ab23a189a4 Author: aefimov Date: 2018-10-08 20:42 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/77ab23a189a4 Merge ! .hgtags Changeset: aec3b5f4ae34 Author: aefimov Date: 2018-07-11 15:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/aec3b5f4ae34 Added tag jdk8u201-b00 for changeset 2bf8498a25ec ! .hgtags Changeset: 1b03cb76a59e Author: aefimov Date: 2018-07-27 11:47 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/1b03cb76a59e Merge ! .hgtags Changeset: 09e0cda9f53d Author: aefimov Date: 2018-08-04 12:53 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/09e0cda9f53d Merge ! .hgtags Changeset: 36292661185e Author: aefimov Date: 2018-08-10 12:27 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/36292661185e Merge ! .hgtags Changeset: 3a4af1679351 Author: aefimov Date: 2018-08-18 12:58 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/3a4af1679351 Merge ! .hgtags Changeset: 2b0ebd23e2c4 Author: alitvinov Date: 2018-08-24 19:25 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/2b0ebd23e2c4 Merge ! .hgtags Changeset: 085a67d76e62 Author: alitvinov Date: 2018-09-03 16:53 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/085a67d76e62 Merge ! .hgtags Changeset: 067031705068 Author: dmarkov Date: 2018-09-07 10:23 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/067031705068 8210431: Complete backport of libpng 1.6.35 TPRM Reviewed-by: jeff, prr ! THIRD_PARTY_README Changeset: c2807622fbbd Author: alitvinov Date: 2018-09-10 16:19 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/c2807622fbbd Merge ! .hgtags Changeset: 9fce84e6f51a Author: coleenp Date: 2018-09-12 10:11 -0400 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/9fce84e6f51a 8210094: Better loading of classloader classes Reviewed-by: acorn, hseigel, ahgross, rhalade ! src/share/vm/classfile/classFileParser.cpp ! src/share/vm/classfile/dictionary.cpp ! src/share/vm/classfile/systemDictionary.cpp ! src/share/vm/classfile/verificationType.cpp ! src/share/vm/classfile/verifier.cpp ! src/share/vm/oops/constantPool.cpp ! src/share/vm/prims/jvm.cpp + test/runtime/ClassUnload/ConstantPoolDependsTest.java + test/runtime/ClassUnload/DictionaryDependsTest.java + test/runtime/ClassUnload/MyDiffClassLoader.java + test/runtime/ClassUnload/SuperDependsTest.java + test/runtime/ClassUnload/p2/c2.java Changeset: 0ff99c48884b Author: aefimov Date: 2018-09-17 15:04 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/0ff99c48884b Merge ! .hgtags Changeset: da06fcb19387 Author: dholmes Date: 2018-09-29 03:37 -0400 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/da06fcb19387 8205714: Initial class initialization Reviewed-by: acorn, coleenp, kvn, vlivanov ! src/share/vm/oops/cpCache.cpp ! src/share/vm/runtime/sharedRuntime.cpp Changeset: f7bd3ef62b03 Author: aefimov Date: 2018-07-02 16:27 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/f7bd3ef62b03 Merge ! .hgtags ! src/share/vm/oops/klass.cpp Changeset: 837064324200 Author: diazhou Date: 2018-07-04 02:06 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/837064324200 Added tag jdk8u181-b31 for changeset f7bd3ef62b03 ! .hgtags Changeset: a2be8e761961 Author: aefimov Date: 2018-07-11 00:20 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/a2be8e761961 Merge ! .hgtags Changeset: 9d9f4c81eb3d Author: diazhou Date: 2018-07-11 22:53 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/9d9f4c81eb3d Added tag jdk8u181-b32 for changeset a2be8e761961 ! .hgtags Changeset: 2ac6a4ff7b3c Author: diazhou Date: 2018-07-24 13:17 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/2ac6a4ff7b3c Added tag jdk8u181-b33 for changeset 9d9f4c81eb3d ! .hgtags Changeset: f3eb9719e696 Author: diazhou Date: 2018-08-27 01:51 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/f3eb9719e696 Added tag jdk8u181-b34 for changeset 2ac6a4ff7b3c ! .hgtags Changeset: 5418d85b93ea Author: diazhou Date: 2018-09-10 14:06 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/5418d85b93ea Added tag jdk8u181-b35 for changeset f3eb9719e696 ! .hgtags Changeset: 310a8a03be93 Author: diazhou Date: 2018-09-24 19:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/310a8a03be93 Added tag jdk8u181-b36 for changeset 5418d85b93ea ! .hgtags Changeset: 995101adba8e Author: aefimov Date: 2018-09-26 15:24 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/995101adba8e Merge ! .hgtags Changeset: 9de790afd8f4 Author: aefimov Date: 2018-09-30 18:26 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/9de790afd8f4 Merge Changeset: 24c8c9e41fcd Author: aefimov Date: 2018-09-30 19:59 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/24c8c9e41fcd Merge ! .hgtags Changeset: ebb74f9e6995 Author: diazhou Date: 2018-10-04 02:46 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/ebb74f9e6995 Added tag jdk8u181-b37 for changeset 310a8a03be93 ! .hgtags Changeset: 062107a28369 Author: aefimov Date: 2018-10-05 16:52 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/062107a28369 Merge ! .hgtags Changeset: cec91c1510a4 Author: aefimov Date: 2018-10-08 21:51 +0100 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/cec91c1510a4 Merge ! .hgtags Changeset: 242132d67800 Author: diazhou Date: 2018-10-17 04:41 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/242132d67800 Added tag jdk8u201-b01 for changeset cec91c1510a4 ! .hgtags Changeset: 68ee3b18354d Author: diazhou Date: 2018-11-01 16:11 -0700 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/68ee3b18354d Added tag jdk8u201-b02 for changeset 242132d67800 ! .hgtags Changeset: f85cae50e040 Author: diazhou Date: 2018-11-07 04:26 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/f85cae50e040 Added tag jdk8u201-b03 for changeset 68ee3b18354d ! .hgtags Changeset: 2b490d8df357 Author: diazhou Date: 2018-11-14 10:17 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/2b490d8df357 Added tag jdk8u201-b04 for changeset f85cae50e040 ! .hgtags Changeset: 4b17023e0a3a Author: diazhou Date: 2018-11-14 11:12 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/4b17023e0a3a Added tag jdk8u201-b74 for changeset 2b490d8df357 ! .hgtags Changeset: 3f6c3bf8f0b1 Author: diazhou Date: 2018-11-19 03:06 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/3f6c3bf8f0b1 Added tag jdk8u201-b05 for changeset 4b17023e0a3a ! .hgtags Changeset: 6ee551349735 Author: diazhou Date: 2018-11-22 09:33 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/6ee551349735 Added tag jdk8u201-b75 for changeset 3f6c3bf8f0b1 ! .hgtags Changeset: f53cabbd1a91 Author: diazhou Date: 2018-11-27 09:16 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/f53cabbd1a91 Added tag jdk8u201-b06 for changeset 6ee551349735 ! .hgtags Changeset: d1bee08dba02 Author: diazhou Date: 2018-11-27 10:22 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/d1bee08dba02 Added tag jdk8u201-b76 for changeset f53cabbd1a91 ! .hgtags Changeset: 5b36a9b6bbb5 Author: alitvinov Date: 2018-11-28 13:49 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/5b36a9b6bbb5 8213792: Update THIRTD_PARTY_README for LCMS to 2.9 Reviewed-by: prr ! THIRD_PARTY_README Changeset: dee6a1ce4a0c Author: dbuck Date: 2018-12-03 07:29 -0500 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/dee6a1ce4a0c 8141491: Unaligned memory access in Bits.c Summary: Introduce alignment-safe Copy::conjoint_swap and JVM_CopySwapMemory Reviewed-by: mikael, dholmes ! make/aix/makefiles/mapfile-vers-debug ! make/aix/makefiles/mapfile-vers-product ! make/bsd/makefiles/mapfile-vers-debug ! make/bsd/makefiles/mapfile-vers-product ! make/linux/makefiles/mapfile-vers-debug ! make/linux/makefiles/mapfile-vers-product ! make/solaris/makefiles/mapfile-vers ! src/share/vm/prims/jvm.cpp ! src/share/vm/prims/jvm.h ! src/share/vm/runtime/interfaceSupport.hpp ! src/share/vm/utilities/copy.cpp ! src/share/vm/utilities/copy.hpp Changeset: e4daab85ac15 Author: diazhou Date: 2018-12-05 19:23 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/e4daab85ac15 Added tag jdk8u201-b07 for changeset dee6a1ce4a0c ! .hgtags Changeset: e2c2448a1ca7 Author: diazhou Date: 2018-12-05 19:45 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/e2c2448a1ca7 Added tag jdk8u201-b77 for changeset e4daab85ac15 ! .hgtags Changeset: 48947e4db9f3 Author: diazhou Date: 2018-12-11 23:59 -0800 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/48947e4db9f3 Added tag jdk8u201-b08 for changeset e2c2448a1ca7 ! .hgtags Changeset: 1e8639cc8075 Author: andrew Date: 2019-02-26 00:54 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/1e8639cc8075 Merge jdk8u201-ga ! .hgtags ! THIRD_PARTY_README ! make/linux/makefiles/mapfile-vers-debug ! src/share/vm/classfile/classFileParser.cpp ! src/share/vm/classfile/dictionary.cpp ! src/share/vm/classfile/systemDictionary.cpp ! src/share/vm/classfile/verifier.cpp ! src/share/vm/oops/constantPool.cpp ! src/share/vm/oops/cpCache.cpp ! src/share/vm/prims/jvm.cpp ! src/share/vm/prims/jvm.h ! src/share/vm/runtime/sharedRuntime.cpp ! src/share/vm/utilities/copy.hpp Changeset: 890a060ab59f Author: andrew Date: 2019-02-26 00:56 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/890a060ab59f Added tag aarch64-shenandoah-jdk8u201-b12 for changeset 1e8639cc8075 ! .hgtags Changeset: 538dce56255a Author: andrew Date: 2019-02-26 02:01 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/538dce56255a Merge Changeset: 488ad5f23093 Author: andrew Date: 2019-02-26 22:28 +0000 URL: http://hg.openjdk.java.net/aarch64-port/jdk8u-shenandoah/hotspot/rev/488ad5f23093 Merge From felix.yang at huawei.com Wed Feb 27 00:46:17 2019 From: felix.yang at huawei.com (Yangfei (Felix)) Date: Wed, 27 Feb 2019 00:46:17 +0000 Subject: [aarch64-port-dev ] RFR (trivial): 8219698: aarch64: SIGILL triggered when specifying unsupported hardware features Message-ID: Hi, Please review this trivial patch. Bug: https://bugs.openjdk.java.net/browse/JDK-8219698 Webrev: http://cr.openjdk.java.net/~fyang/8219698/webrev.00/ Verified the SIGILL will not trigger with this fix. OK to push? Thanks, Felix From Pengfei.Li at arm.com Wed Feb 27 04:15:42 2019 From: Pengfei.Li at arm.com (Pengfei Li (Arm Technology China)) Date: Wed, 27 Feb 2019 04:15:42 +0000 Subject: [aarch64-port-dev ] RFR (trivial): 8219519: Remove linux_sparc.ad and linux_aarch64.ad In-Reply-To: <44494f4f-26ef-3b9e-b38e-eca8178aba89@loongson.cn> References: <900ea372-d9fd-e1fd-051d-3d96e1ec2c66@loongson.cn> <9c080917-84eb-ba84-5951-f159b103e6ed@oracle.com> <44494f4f-26ef-3b9e-b38e-eca8178aba89@loongson.cn> Message-ID: Hi Jie, Tobias, I (Not-A-Reviewer) tested this change on AArch64. Test result shows "make images" is successful and there's no new jtreg failures after linux_aarch64.ad is removed. But I don't have confidence to say this change has no other side effect. -- Thanks, Pengfei > -----Original Message----- > From: hotspot-compiler-dev bounces at openjdk.java.net> On Behalf Of Jie Fu > Sent: Wednesday, February 27, 2019 10:25 > To: Tobias Hartmann ; hotspot-compiler- > dev at openjdk.java.net compiler > Subject: Re: RFR (trivial): 8219519: Remove linux_sparc.ad and > linux_aarch64.ad > > Hi Tobias, > > Thanks a lot for your review. > > It's a bit difficult for me to test this patch since I don't have a sparc or arm > machine. > I've analyzed the adlc processing logic in > make/hotspot/gensrc/GensrcAdlc.gmk finding that ad-files under > ./src/hotspot/os_cpu/$(HOTSPOT_TARGET_OS)_$(HOTSPOT_TARGET_CPU_ > ARCH) are optional. > Since both linux_sparc.ad and linux_aarch64.ad are useless for the > generation of C2, it would be better to remove them. > > I'll try my best to test it. > > By the way, I really appreciate If someone with sparc or aarch64 > development environment could help to verify this change. > Thanks in advance. > > Best regards, > Jie > > > On 2019/2/27 ??12:51, Tobias Hartmann wrote: > > Hi Jie, > > > > this looks good to me assuming that you have tested the change on these > platforms. > > > > Best regards, > > Tobias > > > > On 21.02.19 10:35, Jie Fu wrote: > >> Hi all, > >> > >> The following two source files are useless for the generation of C2 and > should be removed. > >> ?1) ./src/hotspot/os_cpu/linux_sparc/linux_sparc.ad > >> ?2) ./src/hotspot/os_cpu/linux_aarch64/linux_aarch64.ad > >> > >> Bug:??? https://bugs.openjdk.java.net/browse/JDK-8219519 > >> Webrev: http://cr.openjdk.java.net/~jiefu/8219519/webrev.00/ > >> > >> Could you please review it? > >> Thanks a lot. > >> > >> Best regards, > >> Jie > >> > >> From patrick at os.amperecomputing.com Wed Feb 27 05:26:18 2019 From: patrick at os.amperecomputing.com (Patrick Zhang OS) Date: Wed, 27 Feb 2019 05:26:18 +0000 Subject: [aarch64-port-dev ] Request to port a patch to aarch64-port/jdk8u-shenandoah, fix gmtime_r declaration conflicts in zip.cpp with linux header files Message-ID: Hi Can I ask for porting this (simple) patch from jdk8u-dev to aarch64-port/jdk8u-shenandoah? I supposed it would be in via 'bulk merge' but haven't found so in the latest merge. Please kindly approve this, thanks in advance. http://hg.openjdk.java.net/jdk8u/jdk8u-dev/jdk/rev/db7a698be165 JBS: https://bugs.openjdk.java.net/browse/JDK-8217901 (Btw, I found "Fix Version/s: openjdk8u211", when will this accutally happen? April release? or already done? I am confused here...) Regards Patrick -----Original Message----- From: Patrick Zhang Sent: Tuesday, January 29, 2019 11:29 AM To: 'Andrew Hughes' ; Andrew Haley Cc: aarch64-port-dev at openjdk.java.net Subject: RE: [aarch64-port-dev ] Request to cherry-pick JDK-8215976, fix gmtime_r declaration conflicts in zip.cpp with linux header files Many thanks for the help. I saw it is in jdk8u now and suppose will be in aarch64-port/jdk8u-shenandoah soon. Regards Patrick -----Original Message----- From: Andrew Hughes Sent: Wednesday, January 23, 2019 11:40 PM To: Andrew Haley Cc: Patrick Zhang ; aarch64-port-dev at openjdk.java.net Subject: Re: [aarch64-port-dev ] Request to cherry-pick JDK-8215976, fix gmtime_r declaration conflicts in zip.cpp with linux header files On Wed, 23 Jan 2019 at 09:37, Andrew Haley wrote: > > On 1/23/19 3:18 AM, Patrick Zhang wrote: > > Would there be any proper process to follow, please let me know. Appreciate your help. > > I'm fine with this being put into the aarch64-port/jdk8u-shenandoah > port, but it should be sent to jdk8u-dev. > > -- > Andrew Haley > Java Platform Lead Engineer > Red Hat UK Ltd. > EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 Please get the fix into upstream jdk8u, via the 8u-dev list, and we will then pick it up in aarch64-port/jdk8u-shenandoah when we merge. Thanks, -- Andrew :) Senior Free Java Software Engineer Red Hat, Inc. (http://www.redhat.com) Web Site: http://fuseyism.com Twitter: https://twitter.com/gnu_andrew_java PGP Key: ed25519/0xCFDA0F9B35964222 (hkp://keys.gnupg.net) Fingerprint = 5132 579D D154 0ED2 3E04 C5A0 CFDA 0F9B 3596 4222 From fujie at loongson.cn Wed Feb 27 05:46:59 2019 From: fujie at loongson.cn (Jie Fu) Date: Wed, 27 Feb 2019 13:46:59 +0800 Subject: [aarch64-port-dev ] RFR (trivial): 8219519: Remove linux_sparc.ad and linux_aarch64.ad In-Reply-To: References: <900ea372-d9fd-e1fd-051d-3d96e1ec2c66@loongson.cn> <9c080917-84eb-ba84-5951-f159b103e6ed@oracle.com> <44494f4f-26ef-3b9e-b38e-eca8178aba89@loongson.cn> Message-ID: <09b240dd-377b-16c2-9ff6-bff47e557ae9@loongson.cn> Hi Pengfei and Tobias, Thank you so much, Pengfei. The linux_aarch64.ad only defines an enc_class called "Java_To_Runtime" which is not used in the generation of aarch64's C2 at all. I think there is no side effect to remove it. As for the linux_sparc.ad, it is actually empty for the adlc compiler. It should be safe too. Tobias, is it still required to test it on the sparc platform? Thanks. Best regards, Jie On 2019/2/27 ??12:15, Pengfei Li (Arm Technology China) wrote: > Hi Jie, Tobias, > > I (Not-A-Reviewer) tested this change on AArch64. Test result shows "make images" is successful and there's no new jtreg failures after linux_aarch64.ad is removed. But I don't have confidence to say this change has no other side effect. > > -- > Thanks, > Pengfei > >> -----Original Message----- >> From: hotspot-compiler-dev > bounces at openjdk.java.net> On Behalf Of Jie Fu >> Sent: Wednesday, February 27, 2019 10:25 >> To: Tobias Hartmann ; hotspot-compiler- >> dev at openjdk.java.net compiler >> Subject: Re: RFR (trivial): 8219519: Remove linux_sparc.ad and >> linux_aarch64.ad >> >> Hi Tobias, >> >> Thanks a lot for your review. >> >> It's a bit difficult for me to test this patch since I don't have a sparc or arm >> machine. >> I've analyzed the adlc processing logic in >> make/hotspot/gensrc/GensrcAdlc.gmk finding that ad-files under >> ./src/hotspot/os_cpu/$(HOTSPOT_TARGET_OS)_$(HOTSPOT_TARGET_CPU_ >> ARCH) are optional. >> Since both linux_sparc.ad and linux_aarch64.ad are useless for the >> generation of C2, it would be better to remove them. >> >> I'll try my best to test it. >> >> By the way, I really appreciate If someone with sparc or aarch64 >> development environment could help to verify this change. >> Thanks in advance. >> >> Best regards, >> Jie >> >> >> On 2019/2/27 ??12:51, Tobias Hartmann wrote: >>> Hi Jie, >>> >>> this looks good to me assuming that you have tested the change on these >> platforms. >>> Best regards, >>> Tobias >>> >>> On 21.02.19 10:35, Jie Fu wrote: >>>> Hi all, >>>> >>>> The following two source files are useless for the generation of C2 and >> should be removed. >>>> ?1) ./src/hotspot/os_cpu/linux_sparc/linux_sparc.ad >>>> ?2) ./src/hotspot/os_cpu/linux_aarch64/linux_aarch64.ad >>>> >>>> Bug:??? https://bugs.openjdk.java.net/browse/JDK-8219519 >>>> Webrev: http://cr.openjdk.java.net/~jiefu/8219519/webrev.00/ >>>> >>>> Could you please review it? >>>> Thanks a lot. >>>> >>>> Best regards, >>>> Jie >>>> >>>> From fujie at loongson.cn Wed Feb 27 05:31:26 2019 From: fujie at loongson.cn (Jie Fu) Date: Wed, 27 Feb 2019 13:31:26 +0800 Subject: [aarch64-port-dev ] RFR (trivial): 8219519: Remove linux_sparc.ad and linux_aarch64.ad In-Reply-To: References: <900ea372-d9fd-e1fd-051d-3d96e1ec2c66@loongson.cn> <9c080917-84eb-ba84-5951-f159b103e6ed@oracle.com> <44494f4f-26ef-3b9e-b38e-eca8178aba89@loongson.cn> Message-ID: Hi Pengfei and Tobias, Thank you so much, Pengfei. The linux_aarch64.ad only defines an enc_class called "Java_To_Runtime" which is not used in the generation of aarch64's C2 at all. I think there is no side effect to remove it. As for the linux_sparc.ad, it is actually empty for the adlc compiler. It should be safe too. Tobias, is it still required to test it on the sparc platform? Thanks. Best regards, Jie On 2019/2/27 ??12:15, Pengfei Li (Arm Technology China) wrote: > Hi Jie, Tobias, > > I (Not-A-Reviewer) tested this change on AArch64. Test result shows "make images" is successful and there's no new jtreg failures after linux_aarch64.ad is removed. But I don't have confidence to say this change has no other side effect. > > -- > Thanks, > Pengfei > >> -----Original Message----- >> From: hotspot-compiler-dev > bounces at openjdk.java.net> On Behalf Of Jie Fu >> Sent: Wednesday, February 27, 2019 10:25 >> To: Tobias Hartmann ; hotspot-compiler- >> dev at openjdk.java.net compiler >> Subject: Re: RFR (trivial): 8219519: Remove linux_sparc.ad and >> linux_aarch64.ad >> >> Hi Tobias, >> >> Thanks a lot for your review. >> >> It's a bit difficult for me to test this patch since I don't have a sparc or arm >> machine. >> I've analyzed the adlc processing logic in >> make/hotspot/gensrc/GensrcAdlc.gmk finding that ad-files under >> ./src/hotspot/os_cpu/$(HOTSPOT_TARGET_OS)_$(HOTSPOT_TARGET_CPU_ >> ARCH) are optional. >> Since both linux_sparc.ad and linux_aarch64.ad are useless for the >> generation of C2, it would be better to remove them. >> >> I'll try my best to test it. >> >> By the way, I really appreciate If someone with sparc or aarch64 >> development environment could help to verify this change. >> Thanks in advance. >> >> Best regards, >> Jie >> >> >> On 2019/2/27 ??12:51, Tobias Hartmann wrote: >>> Hi Jie, >>> >>> this looks good to me assuming that you have tested the change on these >> platforms. >>> Best regards, >>> Tobias >>> >>> On 21.02.19 10:35, Jie Fu wrote: >>>> Hi all, >>>> >>>> The following two source files are useless for the generation of C2 and >> should be removed. >>>> ?1) ./src/hotspot/os_cpu/linux_sparc/linux_sparc.ad >>>> ?2) ./src/hotspot/os_cpu/linux_aarch64/linux_aarch64.ad >>>> >>>> Bug:??? https://bugs.openjdk.java.net/browse/JDK-8219519 >>>> Webrev: http://cr.openjdk.java.net/~jiefu/8219519/webrev.00/ >>>> >>>> Could you please review it? >>>> Thanks a lot. >>>> >>>> Best regards, >>>> Jie >>>> >>>> From ci_notify at linaro.org Wed Feb 27 08:20:15 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Wed, 27 Feb 2019 08:20:15 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 11u on AArch64 Message-ID: <142556894.757.1551255616404.JavaMail.jenkins@a6c5c67cda76> 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/057/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/12 pass: 5,705; fail: 9; not run: 11,618 Build 1: aarch64/2019/jan/15 pass: 5,705; fail: 9; not run: 11,618 Build 2: aarch64/2019/jan/17 pass: 5,709; fail: 9; not run: 11,618 Build 3: aarch64/2019/jan/22 pass: 5,709; fail: 9; not run: 11,618 Build 4: aarch64/2019/jan/24 pass: 5,708; fail: 10; not run: 11,618 Build 5: aarch64/2019/jan/29 pass: 5,709; fail: 9; not run: 11,618 Build 6: aarch64/2019/jan/31 pass: 5,707; fail: 11; not run: 11,618 Build 7: aarch64/2019/feb/02 pass: 5,708; fail: 10; not run: 11,618 Build 8: aarch64/2019/feb/07 pass: 5,710; fail: 9; not run: 11,618 Build 9: aarch64/2019/feb/09 pass: 5,710; fail: 9; not run: 11,618 Build 10: aarch64/2019/feb/12 pass: 5,709; fail: 10; not run: 11,618 Build 11: aarch64/2019/feb/16 pass: 5,713; fail: 10; not run: 11,618 Build 12: aarch64/2019/feb/19 pass: 5,715; fail: 10; not run: 11,618 Build 13: aarch64/2019/feb/21 pass: 5,714; fail: 11; not run: 11,618 Build 14: aarch64/2019/feb/26 pass: 5,717; fail: 9; not run: 11,618 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/12 pass: 8,376; fail: 496; error: 23 Build 1: aarch64/2019/jan/15 pass: 8,353; fail: 510; error: 32 Build 2: aarch64/2019/jan/17 pass: 8,386; fail: 493; error: 19 Build 3: aarch64/2019/jan/22 pass: 8,369; fail: 506; error: 23 Build 4: aarch64/2019/jan/24 pass: 8,366; fail: 507; error: 25 Build 5: aarch64/2019/jan/29 pass: 8,353; fail: 524; error: 22 Build 6: aarch64/2019/jan/31 pass: 8,372; fail: 502; error: 25 Build 7: aarch64/2019/feb/02 pass: 8,378; fail: 501; error: 21 Build 8: aarch64/2019/feb/07 pass: 8,364; fail: 507; error: 29 Build 9: aarch64/2019/feb/09 pass: 8,354; fail: 523; error: 23 Build 10: aarch64/2019/feb/12 pass: 8,358; fail: 519; error: 24 Build 11: aarch64/2019/feb/16 pass: 8,356; fail: 520; error: 25 Build 12: aarch64/2019/feb/19 pass: 8,375; fail: 506; error: 24 Build 13: aarch64/2019/feb/21 pass: 8,377; fail: 513; error: 22 Build 14: aarch64/2019/feb/26 pass: 8,387; fail: 501; error: 26 4 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/12 pass: 3,903 Build 1: aarch64/2019/jan/15 pass: 3,903 Build 2: aarch64/2019/jan/17 pass: 3,903 Build 3: aarch64/2019/jan/22 pass: 3,903 Build 4: aarch64/2019/jan/24 pass: 3,903 Build 5: aarch64/2019/jan/29 pass: 3,903 Build 6: aarch64/2019/jan/31 pass: 3,903 Build 7: aarch64/2019/feb/02 pass: 3,903 Build 8: aarch64/2019/feb/07 pass: 3,903 Build 9: aarch64/2019/feb/09 pass: 3,903 Build 10: aarch64/2019/feb/12 pass: 3,903 Build 11: aarch64/2019/feb/16 pass: 3,903 Build 12: aarch64/2019/feb/19 pass: 3,903 Build 13: aarch64/2019/feb/21 pass: 3,904 Build 14: aarch64/2019/feb/26 pass: 3,904 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.04x Relative performance: Server critical-jOPS (nc): 7.77x 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-01-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/012/results/ 2019-01-16 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/015/results/ 2019-01-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/017/results/ 2019-01-23 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/022/results/ 2019-01-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/024/results/ 2019-01-30 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/029/results/ 2019-02-02 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/031/results/ 2019-02-03 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/033/results/ 2019-02-08 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/038/results/ 2019-02-11 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/040/results/ 2019-02-13 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/043/results/ 2019-02-17 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/047/results/ 2019-02-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/050/results/ 2019-02-22 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/052/results/ 2019-02-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdk11u/jcstress-nightly-runs/2019/057/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 Wed Feb 27 08:21:18 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Wed, 27 Feb 2019 08:21:18 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <1911905730.759.1551255679341.JavaMail.jenkins@a6c5c67cda76> 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/057/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 792; fail: 16; error: 3 Build 1: aarch64/2019/feb/03 pass: 800; fail: 9; error: 2 Build 2: aarch64/2019/feb/14 pass: 799; fail: 9; error: 3 Build 3: aarch64/2019/feb/26 pass: 799; fail: 9; error: 3 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 5,778; fail: 236; error: 28 Build 1: aarch64/2019/feb/03 pass: 5,756; fail: 261; error: 25 Build 2: aarch64/2019/feb/14 pass: 5,761; fail: 257; error: 24 Build 3: aarch64/2019/feb/26 pass: 5,756; fail: 259; error: 27 1 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 3,114; fail: 2 Build 1: aarch64/2019/feb/03 pass: 3,114; fail: 2 Build 2: aarch64/2019/feb/14 pass: 3,114; fail: 2 Build 3: aarch64/2019/feb/26 pass: 3,114; fail: 2 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.65x Relative performance: Server critical-jOPS (nc): 8.71x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/SPECjbb2015-results/ [1] http://www.spec.org/fairuse.html#Academic Regression test Hadoop-Terasort completed ========================================= This test measures the performance of the server and client compilers running Hadoop sorting a 1GB file using Terasort and compares the performance against the baseline performance of the Zero interpreter and against the baseline performance of the server compiler on 2014-04-01. Relative performance: Zero: 1.0, Server: 176.44 Server 176.44 / Server 2014-04-01 (71.00): 2.49x Details of the test setup and historical results may be found here: http://openjdk.linaro.org/jdk8u/hadoop-terasort-benchmark-results/ This is a summary of the jcstress test results ============================================== The build and test results are cycled every 15 days. 2019-02-04 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/034/results/ 2019-02-14 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/045/results/ 2019-02-27 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/057/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From aph at redhat.com Wed Feb 27 08:56:55 2019 From: aph at redhat.com (Andrew Haley) Date: Wed, 27 Feb 2019 08:56:55 +0000 Subject: [aarch64-port-dev ] RFR (trivial): 8219698: aarch64: SIGILL triggered when specifying unsupported hardware features In-Reply-To: References: Message-ID: <60320bd0-4243-2751-2bd0-1a259e8ef3b7@redhat.com> On 2/27/19 12:46 AM, Yangfei (Felix) wrote: > Bug: https://bugs.openjdk.java.net/browse/JDK-8219698 > Webrev: http://cr.openjdk.java.net/~fyang/8219698/webrev.00/ > > Verified the SIGILL will not trigger with this fix. OK to push? OK. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From adinn at redhat.com Wed Feb 27 10:01:45 2019 From: adinn at redhat.com (Andrew Dinn) Date: Wed, 27 Feb 2019 10:01:45 +0000 Subject: [aarch64-port-dev ] RFR (trivial): 8219519: Remove linux_sparc.ad and linux_aarch64.ad In-Reply-To: References: <900ea372-d9fd-e1fd-051d-3d96e1ec2c66@loongson.cn> <9c080917-84eb-ba84-5951-f159b103e6ed@oracle.com> <44494f4f-26ef-3b9e-b38e-eca8178aba89@loongson.cn> Message-ID: On 27/02/2019 04:15, Pengfei Li (Arm Technology China) wrote: > I (Not-A-Reviewer) tested this change on AArch64. Test result shows > "make images" is successful and there's no new jtreg failures after > linux_aarch64.ad is removed. But I don't have confidence to say this > change has no other side effect. In that case, consider it reviewed by me as regards AArch64. I am sure it will have no other side effect. regards, Andrew Dinn ----------- From tobias.hartmann at oracle.com Wed Feb 27 10:03:48 2019 From: tobias.hartmann at oracle.com (Tobias Hartmann) Date: Wed, 27 Feb 2019 11:03:48 +0100 Subject: [aarch64-port-dev ] RFR (trivial): 8219519: Remove linux_sparc.ad and linux_aarch64.ad In-Reply-To: References: <900ea372-d9fd-e1fd-051d-3d96e1ec2c66@loongson.cn> <9c080917-84eb-ba84-5951-f159b103e6ed@oracle.com> <44494f4f-26ef-3b9e-b38e-eca8178aba89@loongson.cn> Message-ID: <3134c5a6-0a16-5091-6e09-b6c3c347c84c@oracle.com> On 27.02.19 06:31, Jie Fu wrote: > As for the linux_sparc.ad, it is actually empty for the adlc compiler. > It should be safe too. > > Tobias, is it still required to test it on the sparc platform? > Thanks. No, I think it's good to go. Best regards, Tobias From fujie at loongson.cn Wed Feb 27 12:57:03 2019 From: fujie at loongson.cn (Jie Fu) Date: Wed, 27 Feb 2019 20:57:03 +0800 Subject: [aarch64-port-dev ] RFR (trivial): 8219519: Remove linux_sparc.ad and linux_aarch64.ad In-Reply-To: References: <900ea372-d9fd-e1fd-051d-3d96e1ec2c66@loongson.cn> <9c080917-84eb-ba84-5951-f159b103e6ed@oracle.com> <44494f4f-26ef-3b9e-b38e-eca8178aba89@loongson.cn> Message-ID: Thanks Andrew for your review. On 2019?02?27? 18:01, Andrew Dinn wrote: > On 27/02/2019 04:15, Pengfei Li (Arm Technology China) wrote: >> I (Not-A-Reviewer) tested this change on AArch64. Test result shows >> "make images" is successful and there's no new jtreg failures after >> linux_aarch64.ad is removed. But I don't have confidence to say this >> change has no other side effect. > In that case, consider it reviewed by me as regards AArch64. I am sure > it will have no other side effect. > > regards, > > > Andrew Dinn > ----------- From fujie at loongson.cn Wed Feb 27 13:05:37 2019 From: fujie at loongson.cn (Jie Fu) Date: Wed, 27 Feb 2019 21:05:37 +0800 Subject: [aarch64-port-dev ] RFR (trivial): 8219519: Remove linux_sparc.ad and linux_aarch64.ad In-Reply-To: <3134c5a6-0a16-5091-6e09-b6c3c347c84c@oracle.com> References: <900ea372-d9fd-e1fd-051d-3d96e1ec2c66@loongson.cn> <9c080917-84eb-ba84-5951-f159b103e6ed@oracle.com> <44494f4f-26ef-3b9e-b38e-eca8178aba89@loongson.cn> <3134c5a6-0a16-5091-6e09-b6c3c347c84c@oracle.com> Message-ID: Hi Tobias, Thanks for your review. Could you please sponsor it or find a sponsor for me? Thanks a lot. Best regards, Jie On 2019?02?27? 18:03, Tobias Hartmann wrote: > On 27.02.19 06:31, Jie Fu wrote: >> As for the linux_sparc.ad, it is actually empty for the adlc compiler. >> It should be safe too. >> >> Tobias, is it still required to test it on the sparc platform? >> Thanks. > No, I think it's good to go. > > Best regards, > Tobias From vladimir.kozlov at oracle.com Wed Feb 27 20:21:32 2019 From: vladimir.kozlov at oracle.com (Vladimir Kozlov) Date: Wed, 27 Feb 2019 12:21:32 -0800 Subject: [aarch64-port-dev ] [PATCH] 8217561 : X86: Add floating-point Math.min/max intrinsics, approval request In-Reply-To: References: <02FCFB8477C4EF43A2AD8E0C60F3DA2BB1A70A33@FMSMSX126.amr.corp.intel.com> <45438f90-dcac-7941-1cf5-366555821e2e@redhat.com> <3eb77fb3-db71-8e57-a9f3-ebf635a0291c@redhat.com> <1341b8ab-1ab1-0270-86c4-5a4ac4945d03@oracle.com> <35c1db6b-a238-1e1e-9986-3d1a31b00bc2@redhat.com> <3a850f71-0c13-135b-5150-4bdf46654a74@oracle.com> <806a3da6-7125-0ce3-4ec5-d352d7bdcf50@oracle.com> Message-ID: <0ebdb182-2b44-207d-81b7-e1dc1d19150e@oracle.com> Hi Jatin, I am fine with your additional changes but it rises the issue of platform dependency. New code to check probability and your check seems important only for x86. So I have question for aarch64 developers. Are aarch64 fmin/fmax instructions are always faster than code generated by default? If this is true new conditions should be x86 specific. To have a separate function to do these checks. We have precedent - clear_upper_avx(). May be later we have to add other conditions for other platforms too. Thanks, Vladimir On 2/27/19 9:22 AM, Bhateja, Jatin wrote: > Hi Bernard, > I have few queries, please find them embedded in below mail. > > Best Regards, > Jatin > >> -----Original Message----- >> From: B. Blaser [mailto:bsrbnd at gmail.com] >> Sent: Wednesday, February 27, 2019 10:13 PM >> To: Vladimir Kozlov >> Cc: Andrew Haley ; Andrew Dinn ; >> hotspot-compiler-dev at openjdk.java.net; Bhateja, Jatin >> ; Viswanathan, Sandhya >> >> Subject: Re: [PATCH] 8217561 : X86: Add floating-point Math.min/max >> intrinsics, approval request >> >> On Tue, 26 Feb 2019 at 22:34, Vladimir Kozlov >> wrote: >>> >>> On 2/26/19 1:14 PM, B. Blaser wrote: >>>> Hi Vladimir, >>>> >>>> On Tue, 26 Feb 2019 at 21:50, Vladimir Kozlov >>>> wrote: >>>>> >>>>> Hi Bernard, >>>>> >>>>> Unfortunately HotSpot does not collect profiling information per call >> site. >>>>> Currently calee's data is collected from all call sites. For >>>>> example, you can have 2 calls with same *swapped* arguments and you >> will get your balance == 0. >>>>> I would assume if you have multiply call sites in application the >>>>> profiling data will be "flat" - balance value will be near 0. >>>>> >>>>> We did experiment few years ago to collect data per call site but >>>>> we got negative result - no significant improvement in code quality in >> cost of a lot more memory used for MethodData. >>>>> But your case (and cmove) is special since MDO is small for these >>>>> methods. The only downside is to implement that you will need a lot >> more complex changes in HotSpot. >>>>> >>>>> https://bugs.openjdk.java.net/browse/JDK-8015416 >>>>> >>>>> Note, your code is correct in a sense that it use the same >>>>> profiling data as it currently used for inlining these methods. So I don't >> want to reject changes from the start. >>>>> >>>>> The only simple solution I can think of is to use intrinsic only >>>>> for hottest call site. Compare invocation_count with caller's call site >> count to find if it is most used site which contributed the most profiling data. >>>>> >>>>> Thanks, >>>>> Vladimir >>>> >>>> Thanks for your feedback. >>>> >>>> I pushed webrev.05 to jdk/submit a while ago but once I have the >>>> results I'll update the patch as you suggested; the heuristic will >>>> bail out if the caller didn't contribute enough to the statistics, >>>> let say something like at least 80%? >>> >>> Yes, this sounds good. >>> >>> Vladimir >> >> Done: http://hg.openjdk.java.net/jdk/submit/rev/d164e0b595e6 >> >> Please let me know if you've any more comments or if I can push this to the >> main-line (jdk/jdk) once I've got positive test results? > > Profile based intrinsification will not be able to take care of following:- > > 1) De-optimization scenario : Under what condition will this method de-optimize if future inputs change the initially computed balancing factor. > 2) How will balancing factor change with each invocation of C2 since MDO / profile is not affected by code generated by C2. > 3) Check to de-optimize should be part of generated code, but it would add extra cost, in addition C2 does not alter the profiles as of now. > > Vladimir's mail already cleared some of above concerns. > > Another case which was mentioned over the thread sometime back was about reduction which will show better performance with current implementation(non-intrinsic version). > > for (int I = 0 ; I < ITERS ; I++) > Res = Math.max(Res, arr[i]); > > Cross iteration dependency coupled with inter statement RAW dependency within new monolithic sequence of instructions will degrade the performance in reduction scenario. > > Addition check to prevent creation of intrinsic node (Max/Min[FD]Node) in LibraryCallKit::inline_fp_min_max something on following lines will avoid any degradation in reduction > scenarios. > > --- a/src/hotspot/share/opto/library_call.cpp Tue Feb 26 14:57:23 2019 +0530 > +++ b/src/hotspot/share/opto/library_call.cpp Wed Feb 27 20:13:01 2019 +0530 > @@ -6632,6 +6632,12 @@ > if (a->is_Con() || b->is_Con()) { > return false; > } > +#ifdef X86 > + // Being conservative since all the phi edges may not be set > + // by now. This is done to skip over reduction scenarios. > + if (a->is_Phi() || b->is_Phi()) > + return false; > +#endif > > Regards, > Jatin > > >> >> Thanks, >> Bernard From ci_notify at linaro.org Wed Feb 27 22:52:55 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Wed, 27 Feb 2019 22:52:55 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK JDK on AArch64 Message-ID: <166752216.884.1551307976377.JavaMail.jenkins@a6c5c67cda76> 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/058/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/jan/21 pass: 5,514; fail: 8; error: 1; not run: 93 Build 1: aarch64/2019/jan/24 pass: 5,520; fail: 5; error: 1; not run: 93 Build 2: aarch64/2019/jan/25 pass: 5,533; fail: 6; error: 1; not run: 93 Build 3: aarch64/2019/jan/28 pass: 5,533; fail: 6; error: 1; not run: 93 Build 4: aarch64/2019/jan/30 pass: 5,527; fail: 5; error: 2; not run: 93 Build 5: aarch64/2019/feb/04 pass: 5,527; fail: 7; error: 2; not run: 93 Build 6: aarch64/2019/feb/06 pass: 5,532; fail: 4; error: 1; not run: 93 Build 7: aarch64/2019/feb/08 pass: 5,519; fail: 19; error: 2; not run: 93 Build 8: aarch64/2019/feb/11 pass: 5,527; fail: 11; error: 2; not run: 93 Build 9: aarch64/2019/feb/13 pass: 5,537; fail: 4; not run: 93 Build 10: aarch64/2019/feb/15 pass: 5,538; fail: 4; not run: 93 Build 11: aarch64/2019/feb/18 pass: 5,538; fail: 4; not run: 93 Build 12: aarch64/2019/feb/20 pass: 5,539; fail: 4; not run: 93 Build 13: aarch64/2019/feb/25 pass: 5,540; fail: 4; not run: 93 Build 14: aarch64/2019/feb/27 pass: 5,541; fail: 4; not run: 93 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/21 pass: 8,521; fail: 511; error: 20 Build 1: aarch64/2019/jan/24 pass: 8,533; fail: 503; error: 18 Build 2: aarch64/2019/jan/25 pass: 8,538; fail: 500; error: 20 Build 3: aarch64/2019/jan/28 pass: 8,543; fail: 496; error: 20 Build 4: aarch64/2019/jan/30 pass: 8,541; fail: 503; error: 19 Build 5: aarch64/2019/feb/04 pass: 8,539; fail: 506; error: 18 Build 6: aarch64/2019/feb/06 pass: 8,537; fail: 499; error: 27 Build 7: aarch64/2019/feb/08 pass: 8,530; fail: 515; error: 23 Build 8: aarch64/2019/feb/11 pass: 8,559; fail: 490; error: 15 Build 9: aarch64/2019/feb/13 pass: 8,534; fail: 512; error: 18 Build 10: aarch64/2019/feb/15 pass: 8,556; fail: 492; error: 16 Build 11: aarch64/2019/feb/18 pass: 8,530; fail: 514; error: 20 Build 12: aarch64/2019/feb/20 pass: 8,550; fail: 498; error: 17 Build 13: aarch64/2019/feb/25 pass: 8,535; fail: 510; error: 23 Build 14: aarch64/2019/feb/27 pass: 8,538; fail: 513; error: 20 3 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/21 pass: 3,993; fail: 1 Build 1: aarch64/2019/jan/24 pass: 3,993; fail: 1 Build 2: aarch64/2019/jan/25 pass: 3,993; fail: 1 Build 3: aarch64/2019/jan/28 pass: 3,994; fail: 1 Build 4: aarch64/2019/jan/30 pass: 3,994; fail: 1 Build 5: aarch64/2019/feb/04 pass: 3,994; fail: 1 Build 6: aarch64/2019/feb/06 pass: 3,994; fail: 1 Build 7: aarch64/2019/feb/08 pass: 3,994; fail: 1 Build 8: aarch64/2019/feb/11 pass: 3,994; fail: 1 Build 9: aarch64/2019/feb/13 pass: 3,994; fail: 1 Build 10: aarch64/2019/feb/15 pass: 3,995 Build 11: aarch64/2019/feb/18 pass: 3,996 Build 12: aarch64/2019/feb/20 pass: 3,996 Build 13: aarch64/2019/feb/25 pass: 3,931 Build 14: aarch64/2019/feb/27 pass: 3,931 ------------------------------------------------------------------------------- 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.80x Relative performance: Server critical-jOPS (nc): 9.69x 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-21 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/021/results/ 2019-01-24 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/024/results/ 2019-01-27 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/025/results/ 2019-01-28 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/028/results/ 2019-01-31 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/030/results/ 2019-02-05 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/035/results/ 2019-02-07 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/037/results/ 2019-02-09 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/039/results/ 2019-02-12 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/042/results/ 2019-02-14 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/044/results/ 2019-02-15 pass rate: 11558/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/046/results/ 2019-02-18 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/049/results/ 2019-02-20 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/051/results/ 2019-02-25 pass rate: 11560/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/056/results/ 2019-02-27 pass rate: 11559/11560, results: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/2019/058/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdkX/jcstress-nightly-runs/ From fujie at loongson.cn Thu Feb 28 01:57:39 2019 From: fujie at loongson.cn (Jie Fu) Date: Thu, 28 Feb 2019 09:57:39 +0800 Subject: [aarch64-port-dev ] RFR (trivial): 8219519: Remove linux_sparc.ad and linux_aarch64.ad In-Reply-To: References: <900ea372-d9fd-e1fd-051d-3d96e1ec2c66@loongson.cn> <9c080917-84eb-ba84-5951-f159b103e6ed@oracle.com> <44494f4f-26ef-3b9e-b38e-eca8178aba89@loongson.cn> <3134c5a6-0a16-5091-6e09-b6c3c347c84c@oracle.com> Message-ID: Hi Tobias, I have exported the patch in the attachment. Could you please push it for me? Thanks a lot. Best regards, Jie On 2019/2/27 ??9:05, Jie Fu wrote: > Hi Tobias, > > Thanks for your review. > Could you please sponsor it or find a sponsor for me? > Thanks a lot. > > Best regards, > Jie > > > On 2019?02?27? 18:03, Tobias Hartmann wrote: >> On 27.02.19 06:31, Jie Fu wrote: >>> As for the linux_sparc.ad, it is actually empty for the adlc compiler. >>> It should be safe too. >>> >>> Tobias, is it still required to test it on the sparc platform? >>> Thanks. >> No, I think it's good to go. >> >> Best regards, >> Tobias > -------------- next part -------------- A non-text attachment was scrubbed... Name: JDK-8219519.patch Type: text/x-patch Size: 5185 bytes Desc: not available URL: From Pengfei.Li at arm.com Thu Feb 28 06:45:09 2019 From: Pengfei.Li at arm.com (Pengfei Li (Arm Technology China)) Date: Thu, 28 Feb 2019 06:45:09 +0000 Subject: [aarch64-port-dev ] [PATCH] 8217561 : X86: Add floating-point Math.min/max intrinsics, approval request In-Reply-To: <0ebdb182-2b44-207d-81b7-e1dc1d19150e@oracle.com> References: <02FCFB8477C4EF43A2AD8E0C60F3DA2BB1A70A33@FMSMSX126.amr.corp.intel.com> <45438f90-dcac-7941-1cf5-366555821e2e@redhat.com> <3eb77fb3-db71-8e57-a9f3-ebf635a0291c@redhat.com> <1341b8ab-1ab1-0270-86c4-5a4ac4945d03@oracle.com> <35c1db6b-a238-1e1e-9986-3d1a31b00bc2@redhat.com> <3a850f71-0c13-135b-5150-4bdf46654a74@oracle.com> <806a3da6-7125-0ce3-4ec5-d352d7bdcf50@oracle.com> <0ebdb182-2b44-207d-81b7-e1dc1d19150e@oracle.com> Message-ID: Hi Vladimir, Jatin and All, > So I have question for aarch64 developers. Are aarch64 fmin/fmax > instructions are always faster than code generated by default? If this is true > new conditions should be x86 specific. To have a separate function to do > these checks. We have precedent - clear_upper_avx(). May be later we have > to add other conditions for other platforms too. I am the author of original AArch64 fmin/fmax intrinsics patch[1], but not a reviewer. Both Andrew Haley and I have tested the performance of AArch64 fmin/fmax instructions before. As far as I could remember, the result is similar to what we have seen here on x86. If selecting the min/max values from an array of random numbers, fmin/fmax instructions show better performance. But for an already (almost) sorted array, fmin/fmax instructions do make the performance worse, but not too much. So personally I think, adding heuristic in shared code would benefit AArch64 as well. I didn't quite understand Jatin's additional code below. -- +#ifdef X86 + // Being conservative since all the phi edges may not be set + // by now. This is done to skip over reduction scenarios. + if (a->is_Phi() || b->is_Phi()) + return false; +#endif -- Is it going to black out *all* reduction scenarios? I see the intrinsics benefit the reduction in some cases. And in my opinion, adding this kind of platform-dependent macros in hotspot shared code is not so good. [1] http://hg.openjdk.java.net/jdk/jdk/rev/f15af1e2c683 -- Thanks, Pengfei From nick.gasson at arm.com Thu Feb 28 08:38:58 2019 From: nick.gasson at arm.com (Nick Gasson) Date: Thu, 28 Feb 2019 16:38:58 +0800 Subject: [aarch64-port-dev ] RFC: using gtest to test AArch64 MacroAssembler Message-ID: <420f5ddf-cdd3-3c2d-29ea-a456f6b16cbe@arm.com> Hi AArch64 devs... When I was making some changes to the fast_lock and fast_unlock macros last month, I found it was very difficult to verify I hadn't broken anything using the existing hotspot tests. Also it seems that many of the intrinsics have less-than-perfect coverage from the existing jtreg tests. But I think most of the assembly code in MacroAssembler and the stub routines are quite amenable to unit testing, as it's possible to specify their inputs and outputs in terms of registers and some memory buffers, and they don't access a lot of global state. Below is an example of how we might use the existing hotspot gtest framework to write unit tests for our assembly code. I've included an example of testing fast_lock/unlock (that would fail prior to 8217368 and 8216350) and the string_compare intrinsic. http://cr.openjdk.java.net/~ngasson/gtest/webrev.0/ I'm interested whether you think this is useful or not? IMO the advantages of testing this way over Java tests using jtreg are: * We guarantee that the intrinsic/macro code will actually be run (i.e. we don't have to worry about compiler flags, warmup time, etc.) * We can precisely control the input - e.g. buffer sizes and alignment - which should make it easier to hit corner cases. * It's possible to write assertions about things that are impossible to write functional tests for from Java. E.g. the locking macro failure modes just caused a performance degradation which is hard to detect unless you can look at the value in the flags register. * It's much faster to run than jtreg (each test above takes <1ms, plus a few hundred ms VM setup time). * It's all #ifdef AARCH64 so has zero effect on other platforms. We could also move the assembler smoke test that's currently called from aarch64TestHook into gtest, as I don't see a reason to run that every time we start the VM in debug mode. (Does aarch64TestHook leak a BufferBlob at the moment?) Thanks, Nick From aph at redhat.com Thu Feb 28 09:38:37 2019 From: aph at redhat.com (Andrew Haley) Date: Thu, 28 Feb 2019 09:38:37 +0000 Subject: [aarch64-port-dev ] RFC: using gtest to test AArch64 MacroAssembler In-Reply-To: <420f5ddf-cdd3-3c2d-29ea-a456f6b16cbe@arm.com> References: <420f5ddf-cdd3-3c2d-29ea-a456f6b16cbe@arm.com> Message-ID: <55e8932c-cdfa-f883-5276-e993aa2bfe3f@redhat.com> On 2/28/19 8:38 AM, Nick Gasson wrote: > When I was making some changes to the fast_lock and fast_unlock macros > last month, I found it was very difficult to verify I hadn't broken > anything using the existing hotspot tests. Also it seems that many of > the intrinsics have less-than-perfect coverage from the existing jtreg > tests. I'll address the rest of your post later, but one thing occurs to me: you don't mention jcstress anywhere in this message. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From nick.gasson at arm.com Thu Feb 28 09:49:21 2019 From: nick.gasson at arm.com (Nick Gasson) Date: Thu, 28 Feb 2019 17:49:21 +0800 Subject: [aarch64-port-dev ] RFC: using gtest to test AArch64 MacroAssembler In-Reply-To: <55e8932c-cdfa-f883-5276-e993aa2bfe3f@redhat.com> References: <420f5ddf-cdd3-3c2d-29ea-a456f6b16cbe@arm.com> <55e8932c-cdfa-f883-5276-e993aa2bfe3f@redhat.com> Message-ID: Hi Andrew, On 28/02/2019 17:38, Andrew Haley wrote: > > I'll address the rest of your post later, but one thing occurs to me: you > don't mention jcstress anywhere in this message. > Yes that's true, and I ran jcstress at the time. But jcstress is checking your implementation is correct wrt. the Java memory model, rather than some implementation details. You could replace fast_lock and fast_unlock with something that just set the NE flag and it would still pass jcstress (because it would always fall through to the slow path), but that's probably not what was intended... Nick From aph at redhat.com Thu Feb 28 09:54:49 2019 From: aph at redhat.com (Andrew Haley) Date: Thu, 28 Feb 2019 09:54:49 +0000 Subject: [aarch64-port-dev ] [PATCH] 8217561 : X86: Add floating-point Math.min/max intrinsics, approval request In-Reply-To: <0ebdb182-2b44-207d-81b7-e1dc1d19150e@oracle.com> References: <02FCFB8477C4EF43A2AD8E0C60F3DA2BB1A70A33@FMSMSX126.amr.corp.intel.com> <45438f90-dcac-7941-1cf5-366555821e2e@redhat.com> <3eb77fb3-db71-8e57-a9f3-ebf635a0291c@redhat.com> <1341b8ab-1ab1-0270-86c4-5a4ac4945d03@oracle.com> <35c1db6b-a238-1e1e-9986-3d1a31b00bc2@redhat.com> <3a850f71-0c13-135b-5150-4bdf46654a74@oracle.com> <806a3da6-7125-0ce3-4ec5-d352d7bdcf50@oracle.com> <0ebdb182-2b44-207d-81b7-e1dc1d19150e@oracle.com> Message-ID: <7194e0cc-0f4f-7348-7b50-1347acbf9f92@redhat.com> On 2/27/19 8:21 PM, Vladimir Kozlov wrote: > So I have question for aarch64 developers. Are aarch64 fmin/fmax > instructions are always faster than code generated by default? Be aware that AArch64 is an abstract architecture, so it cannot be said to have performance properties. In real hardware, however, the answer is no. Nothing like. I have seen the fmin/fmax instructions cause a 3x slowdown on a reduction loop. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Thu Feb 28 10:03:54 2019 From: aph at redhat.com (Andrew Haley) Date: Thu, 28 Feb 2019 10:03:54 +0000 Subject: [aarch64-port-dev ] RFC: using gtest to test AArch64 MacroAssembler In-Reply-To: References: <420f5ddf-cdd3-3c2d-29ea-a456f6b16cbe@arm.com> <55e8932c-cdfa-f883-5276-e993aa2bfe3f@redhat.com> Message-ID: <7911db16-f968-00f0-bdd2-6728dd83fa63@redhat.com> On 2/28/19 9:49 AM, Nick Gasson wrote: > Hi Andrew, > > On 28/02/2019 17:38, Andrew Haley wrote: >> >> I'll address the rest of your post later, but one thing occurs to me: you >> don't mention jcstress anywhere in this message. > > Yes that's true, and I ran jcstress at the time. But jcstress is > checking your implementation is correct wrt. the Java memory model, > rather than some implementation details. You could replace fast_lock and > fast_unlock with something that just set the NE flag and it would still > pass jcstress (because it would always fall through to the slow path), > but that's probably not what was intended... I'll pass this one back to you: which classes of bugs in locks would this new test *not* detect? Are they important? What could be done about that? -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From adinn at redhat.com Thu Feb 28 10:05:16 2019 From: adinn at redhat.com (Andrew Dinn) Date: Thu, 28 Feb 2019 10:05:16 +0000 Subject: [aarch64-port-dev ] [PATCH] 8217561 : X86: Add floating-point Math.min/max intrinsics, approval request In-Reply-To: References: <02FCFB8477C4EF43A2AD8E0C60F3DA2BB1A70A33@FMSMSX126.amr.corp.intel.com> <45438f90-dcac-7941-1cf5-366555821e2e@redhat.com> <3eb77fb3-db71-8e57-a9f3-ebf635a0291c@redhat.com> <1341b8ab-1ab1-0270-86c4-5a4ac4945d03@oracle.com> <35c1db6b-a238-1e1e-9986-3d1a31b00bc2@redhat.com> <3a850f71-0c13-135b-5150-4bdf46654a74@oracle.com> <806a3da6-7125-0ce3-4ec5-d352d7bdcf50@oracle.com> <0ebdb182-2b44-207d-81b7-e1dc1d19150e@oracle.com> Message-ID: <55011344-326e-dede-6492-edc8ec1def07@redhat.com> On 28/02/2019 06:45, Pengfei Li (Arm Technology China) wrote: >> So I have question for aarch64 developers. Are aarch64 fmin/fmax >> instructions are always faster than code generated by default? If >> this is true new conditions should be x86 specific. To have a >> separate function to do these checks. We have precedent - >> clear_upper_avx(). May be later we have to add other conditions for >> other platforms too. > > I am the author of original AArch64 fmin/fmax intrinsics patch[1], > but not a reviewer. > > Both Andrew Haley and I have tested the performance of AArch64 > fmin/fmax instructions before. As far as I could remember, the result > is similar to what we have seen here on x86. If selecting the min/max > values from an array of random numbers, fmin/fmax instructions show > better performance. But for an already (almost) sorted array, > fmin/fmax instructions do make the performance worse, but not too > much. So personally I think, adding heuristic in shared code would > benefit AArch64 as well. I also have been looking at this issue on AArch64 and found the same as Pengfei. The fpmin/max intrinsics appear to improve performance significantly when the Java code suffers from unpredictable branches. They also appear to cause a degradation to performance when branching is predictable. On some architectures and for some cases that degradation is small. On others it can be significant. So, a heuristic that selects the intrinsic according to branch statistics would be a very good idea. > I didn't quite understand Jatin's additional code below. . . . Is it > going to black out *all* reduction scenarios? I see the intrinsics > benefit the reduction in some cases. And in my opinion, adding this > kind of platform-dependent macros in hotspot shared code is not so > good. I also am not clear what Jatin's Phi feedback heuristic is doing but it does look like it is deselecting the intrinsic when the value produced is fed back into a loop pipeline. That appears to rule out opportunities for use of vector reduction in combination with the vector intrinsic (obviously, that would only apply in cases where use of the intrinsic was selected as beneficial). If so then Jatin's bypassing of the Phi feedback case is an issue for AArch64. Pengfei found there were significant benefits to using the AArch64 vector reduction instructions (fmaxv/fminv) for 4S (4 x float) vectors. However, his tests were not fully driving the reduction rules. I have since found significant benefits using them for 2D (2 x double) vectors. It is not yet clear to me whether if this is true across the board for all AArch64 architectures. 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 Thu Feb 28 10:36:18 2019 From: nick.gasson at arm.com (Nick Gasson) Date: Thu, 28 Feb 2019 18:36:18 +0800 Subject: [aarch64-port-dev ] RFC: using gtest to test AArch64 MacroAssembler In-Reply-To: <7911db16-f968-00f0-bdd2-6728dd83fa63@redhat.com> References: <420f5ddf-cdd3-3c2d-29ea-a456f6b16cbe@arm.com> <55e8932c-cdfa-f883-5276-e993aa2bfe3f@redhat.com> <7911db16-f968-00f0-bdd2-6728dd83fa63@redhat.com> Message-ID: <4ae23fbf-f2ef-9b85-a657-022fa9891bca@arm.com> On 28/02/2019 18:03, Andrew Haley wrote: > > I'll pass this one back to you: which classes of bugs in locks would > this new test *not* detect? Are they important? What could be done > about that? > It doesn't detect bugs caused by races between threads within fast_lock/unlock, i.e. something that would require us in the test to set up some state, start running the code, and then change that state before a certain instruction is executed. Or bugs caused by using the wrong memory ordering semantics. Yes they are important. It would certainly be possible to create multiple threads inside the gtest test and then run a mini stress test. But that seems to be duplicating a lot of what jcstress already does for us. So I guess the question is, is there some locking behaviour that we can't test with assertions in a single-threaded gtest, and if it was wrong wouldn't cause a jcstress failure? I'm not sure so I'll need to think a bit more about that... Thanks, Nick From aph at redhat.com Thu Feb 28 11:32:54 2019 From: aph at redhat.com (Andrew Haley) Date: Thu, 28 Feb 2019 11:32:54 +0000 Subject: [aarch64-port-dev ] [PATCH] 8217561 : X86: Add floating-point Math.min/max intrinsics, approval request In-Reply-To: References: <02FCFB8477C4EF43A2AD8E0C60F3DA2BB1A70A33@FMSMSX126.amr.corp.intel.com> <45438f90-dcac-7941-1cf5-366555821e2e@redhat.com> <3eb77fb3-db71-8e57-a9f3-ebf635a0291c@redhat.com> <1341b8ab-1ab1-0270-86c4-5a4ac4945d03@oracle.com> <35c1db6b-a238-1e1e-9986-3d1a31b00bc2@redhat.com> <3a850f71-0c13-135b-5150-4bdf46654a74@oracle.com> <806a3da6-7125-0ce3-4ec5-d352d7bdcf50@oracle.com> <0ebdb182-2b44-207d-81b7-e1dc1d19150e@oracle.com> Message-ID: <786e7a3c-ee5f-1a2d-5855-d26ac8244101@redhat.com> On 2/28/19 6:45 AM, Pengfei Li (Arm Technology China) wrote: > But for an already (almost) sorted array, fmin/fmax instructions do make the performance worse, but not too much. I have seen a 3x performance degradation on a min reduction over an array. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Thu Feb 28 12:38:53 2019 From: aph at redhat.com (Andrew Haley) Date: Thu, 28 Feb 2019 12:38:53 +0000 Subject: [aarch64-port-dev ] [PATCH] 8217561 : X86: Add floating-point Math.min/max intrinsics, approval request In-Reply-To: <7194e0cc-0f4f-7348-7b50-1347acbf9f92@redhat.com> References: <02FCFB8477C4EF43A2AD8E0C60F3DA2BB1A70A33@FMSMSX126.amr.corp.intel.com> <45438f90-dcac-7941-1cf5-366555821e2e@redhat.com> <3eb77fb3-db71-8e57-a9f3-ebf635a0291c@redhat.com> <1341b8ab-1ab1-0270-86c4-5a4ac4945d03@oracle.com> <35c1db6b-a238-1e1e-9986-3d1a31b00bc2@redhat.com> <3a850f71-0c13-135b-5150-4bdf46654a74@oracle.com> <806a3da6-7125-0ce3-4ec5-d352d7bdcf50@oracle.com> <0ebdb182-2b44-207d-81b7-e1dc1d19150e@oracle.com> <7194e0cc-0f4f-7348-7b50-1347acbf9f92@redhat.com> Message-ID: <8bf4cc54-6e66-fab4-b3fe-4b026780924d@redhat.com> On 2/28/19 9:54 AM, Andrew Haley wrote: > On 2/27/19 8:21 PM, Vladimir Kozlov wrote: > >> So I have question for aarch64 developers. Are aarch64 fmin/fmax >> instructions are always faster than code generated by default? > Be aware that AArch64 is an abstract architecture, so it cannot be > said to have performance properties. > > In real hardware, however, the answer is no. Nothing like. I have seen > the fmin/fmax instructions cause a 3x slowdown on a reduction loop. So Andrew Dinn asked me what machine, and what test. After some time trying I confess that I cannot reproduce this result. I didn't think much of it at the time, which was why I didn't record that information. My apologies. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From aph at redhat.com Thu Feb 28 14:11:26 2019 From: aph at redhat.com (Andrew Haley) Date: Thu, 28 Feb 2019 14:11:26 +0000 Subject: [aarch64-port-dev ] RFC: using gtest to test AArch64 MacroAssembler In-Reply-To: <4ae23fbf-f2ef-9b85-a657-022fa9891bca@arm.com> References: <420f5ddf-cdd3-3c2d-29ea-a456f6b16cbe@arm.com> <55e8932c-cdfa-f883-5276-e993aa2bfe3f@redhat.com> <7911db16-f968-00f0-bdd2-6728dd83fa63@redhat.com> <4ae23fbf-f2ef-9b85-a657-022fa9891bca@arm.com> Message-ID: <9e1a5703-6dc8-a01c-a083-3ed7469e4f2d@redhat.com> On 2/28/19 10:36 AM, Nick Gasson wrote: > On 28/02/2019 18:03, Andrew Haley wrote: >> >> I'll pass this one back to you: which classes of bugs in locks would >> this new test *not* detect? Are they important? What could be done >> about that? >> > > It doesn't detect bugs caused by races between threads within > fast_lock/unlock, i.e. something that would require us in the test to > set up some state, start running the code, and then change that state > before a certain instruction is executed. Or bugs caused by using the > wrong memory ordering semantics. > > Yes they are important. > > It would certainly be possible to create multiple threads inside the > gtest test and then run a mini stress test. But that seems to be > duplicating a lot of what jcstress already does for us. So I guess the > question is, is there some locking behaviour that we can't test with > assertions in a single-threaded gtest, and if it was wrong wouldn't > cause a jcstress failure? I'm not sure so I'll need to think a bit more > about that... That's fine. It's just that I'm trying not to have to guess which failures this new test will detect, and which ones it won't. I'm not saying that the test isn't useful. So, it helps us detect cases that jcstress doesn't. I guess if we test the slow and the fast paths separately, we can hope that the jcstress test will do the rest. -- Andrew Haley Java Platform Lead Engineer Red Hat UK Ltd. EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 From ci_notify at linaro.org Thu Feb 28 14:10:41 2019 From: ci_notify at linaro.org (ci_notify at linaro.org) Date: Thu, 28 Feb 2019 14:10:41 +0000 (UTC) Subject: [aarch64-port-dev ] JTREG, JCStress, SPECjbb2015 and Hadoop/Terasort results for OpenJDK 8u on AArch64 Message-ID: <1250427301.984.1551363041944.JavaMail.jenkins@a6c5c67cda76> 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/059/summary.html ------------------------------------------------------------------------------- release/hotspot ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 792; fail: 16; error: 3 Build 1: aarch64/2019/feb/03 pass: 800; fail: 9; error: 2 Build 2: aarch64/2019/feb/14 pass: 799; fail: 9; error: 3 Build 3: aarch64/2019/feb/26 pass: 799; fail: 9; error: 3 Build 4: aarch64/2019/feb/28 pass: 803; fail: 9; error: 2 ------------------------------------------------------------------------------- release/jdk ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 5,778; fail: 236; error: 28 Build 1: aarch64/2019/feb/03 pass: 5,756; fail: 261; error: 25 Build 2: aarch64/2019/feb/14 pass: 5,761; fail: 257; error: 24 Build 3: aarch64/2019/feb/26 pass: 5,756; fail: 259; error: 27 Build 4: aarch64/2019/feb/28 pass: 5,749; fail: 268; error: 26 2 fatal errors were detected; please follow the link above for more detail. ------------------------------------------------------------------------------- release/langtools ------------------------------------------------------------------------------- Build 0: aarch64/2019/jan/24 pass: 3,114; fail: 2 Build 1: aarch64/2019/feb/03 pass: 3,114; fail: 2 Build 2: aarch64/2019/feb/14 pass: 3,114; fail: 2 Build 3: aarch64/2019/feb/26 pass: 3,114; fail: 2 Build 4: aarch64/2019/feb/28 pass: 3,114; fail: 2 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.65x 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: 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-04 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/034/results/ 2019-02-14 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/045/results/ 2019-02-27 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/057/results/ 2019-02-28 pass rate: 8491/8491, results: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/2019/059/results/ For detailed information on the test output please refer to: http://openjdk.linaro.org/jdk8u/jcstress-nightly-runs/ From vladimir.kozlov at oracle.com Thu Feb 28 19:26:34 2019 From: vladimir.kozlov at oracle.com (Vladimir Kozlov) Date: Thu, 28 Feb 2019 11:26:34 -0800 Subject: [aarch64-port-dev ] [PATCH] 8217561 : X86: Add floating-point Math.min/max intrinsics, approval request In-Reply-To: References: <02FCFB8477C4EF43A2AD8E0C60F3DA2BB1A70A33@FMSMSX126.amr.corp.intel.com> <45438f90-dcac-7941-1cf5-366555821e2e@redhat.com> <3eb77fb3-db71-8e57-a9f3-ebf635a0291c@redhat.com> <1341b8ab-1ab1-0270-86c4-5a4ac4945d03@oracle.com> <35c1db6b-a238-1e1e-9986-3d1a31b00bc2@redhat.com> <3a850f71-0c13-135b-5150-4bdf46654a74@oracle.com> <806a3da6-7125-0ce3-4ec5-d352d7bdcf50@oracle.com> <0ebdb182-2b44-207d-81b7-e1dc1d19150e@oracle.com> Message-ID: <04476179-590e-9315-667c-cc6885477194@oracle.com> Thank you, Pengfei Then lets keep branch prediction heuristic shared. I take back my previous suggestion to have a function for it. Jatin, can you Pengfei's question about your change? Thanks, Vladimir On 2/27/19 10:45 PM, Pengfei Li (Arm Technology China) wrote: > Hi Vladimir, Jatin and All, > >> So I have question for aarch64 developers. Are aarch64 fmin/fmax >> instructions are always faster than code generated by default? If this is true >> new conditions should be x86 specific. To have a separate function to do >> these checks. We have precedent - clear_upper_avx(). May be later we have >> to add other conditions for other platforms too. > > I am the author of original AArch64 fmin/fmax intrinsics patch[1], but not a reviewer. > > Both Andrew Haley and I have tested the performance of AArch64 fmin/fmax instructions before. As far as I could remember, the result is similar to what we have seen here on x86. If selecting the min/max values from an array of random numbers, fmin/fmax instructions show better performance. But for an already (almost) sorted array, fmin/fmax instructions do make the performance worse, but not too much. So personally I think, adding heuristic in shared code would benefit AArch64 as well. > > I didn't quite understand Jatin's additional code below. > -- > +#ifdef X86 > + // Being conservative since all the phi edges may not be set > + // by now. This is done to skip over reduction scenarios. > + if (a->is_Phi() || b->is_Phi()) > + return false; > +#endif > -- > Is it going to black out *all* reduction scenarios? I see the intrinsics benefit the reduction in some cases. And in my opinion, adding this kind of platform-dependent macros in hotspot shared code is not so good. > > [1] http://hg.openjdk.java.net/jdk/jdk/rev/f15af1e2c683 > > -- > Thanks, > Pengfei > From lunliu93 at gmail.com Fri Feb 22 11:14:57 2019 From: lunliu93 at gmail.com (Lun Liu) Date: Fri, 22 Feb 2019 03:14:57 -0800 Subject: [aarch64-port-dev ] [NEW BUG]Missing LoadStore barrier in interpreter? In-Reply-To: <1880b8f1-7563-f50e-aef9-5c6032672844@redhat.com> References: <07ce7183-e57c-dc68-9391-3d1369c67e77@redhat.com> <1880b8f1-7563-f50e-aef9-5c6032672844@redhat.com> Message-ID: Thanks for confirming and posting the patch. Just realized void TemplateTable::fast_storefield(TosState state) in the same file has the same problem. Could someone help fix that too? Best, On Tue, Feb 12, 2019 at 1:28 AM Andrew Haley wrote: > On 2/12/19 9:05 AM, Yangfei (Felix) wrote: > > This is aarch64-specific and is supposed to be merged into: > aarch64-port/jdk8u-shenandoah and aarch64-port/jdk8u repos. > > > > Do we still need to send this to the 8u list ? If true, should I simply > CC to that list? > > Sorry, of course. No, don't post to 8u. Please forget I said that! :-) > > Only halfway down my first cup of coffee... > > -- > Andrew Haley > Java Platform Lead Engineer > Red Hat UK Ltd. > EAC8 43EB D3EF DB98 CC77 2FAD A5CD 6035 332F A671 > -- Lun Liu PhD Candidate Computer Science Department University of California, Los Angeles