[aarch64-port-dev ] FW: [Mach5] mach5-one-phh-JDK-8151779-20200427-2151-10554367: FAILED

Liu, Xin xxinliu at amazon.com
Wed Apr 29 23:43:13 UTC 2020


Hi, Nick,

Thanks for taking a look at this issue.  I figure out why.

There’re two separated issues. 
1. My toolchain was too old. That’s why I can’t reproduce the building failures feedbacked from submit repo. 

OpenJDK wiki says jdk13 Linux x86_64 supports gcc 8.2, so I believe it means the building hosts must use gcc 8.2+. 
My WIP patch does have a C++ issue captured by g++-8+.

2.  I can’t use adoptOpenJDK’s aarch64 jdk14 as boot-jdk.  Thanks for helping me to understand the problem. 
The pagesize of my aarch64 host is 4k.  I don't have access of adoptOpenJDK's build hosts. I have filed an issue to adoptJDK https://github.com/AdoptOpenJDK/openjdk14-binaries/issues/1
 
One trick here. It's very easy to cheat configure by hacking the boot-jdk.m4 to "$HEAD -n 2". Everything looks fine then. 
 
Thanks,
--lx

On 4/28/20, 3:14 AM, "hotspot-dev on behalf of Nick Gasson" <hotspot-dev-bounces at openjdk.java.net on behalf of nick.gasson at arm.com> wrote:

    CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.



    >
    > My nightly buildbot started failing recently on aarch64.
    > One issue is the error message of [cds] prevents configure from bootjdk determining.
    > https://hg.openjdk.java.net/jdk/jdk/file/1b8f9e72b22b/make/autoconf/boot-jdk.m4#l77
    >
    > ./bin/java --version
    > [0.006s][error][cds] Unable to map CDS archive -- os::vm_allocation_granularity() expected: 65536 actual: 4096
    > openjdk 14.0.1 2020-04-14
    > OpenJDK Runtime Environment AdoptOpenJDK (build 14.0.1+7)
    > OpenJDK 64-Bit Server VM AdoptOpenJDK (build 14.0.1+7, mixed mode)
    >
    > Are you aware of this issue? I can’t see [cds] line on my linux/x86_64 host.
    > Maybe it’s aarch64-only.  CC aarch-port-dev.
    >

    Was your boot JDK built on a machine configured with a different page
    size to your current machine? Looks like the CDS archive was dumped on a
    machine with 64k pages but you're running with 4k pages. There's a JBS
    issue for this:

    https://bugs.openjdk.java.net/browse/JDK-8236847


    Thanks,
    Nick



More information about the aarch64-port-dev mailing list