[jdk11u-dev] RFR: 8253795: Implementation of JEP 391: macOS/AArch64 Port [v7]

[Vladimir Kempik]

On Thu, 20 Jan 2022 15:43:46 GMT, Vladimir Kempik <vkempik at openjdk.org> wrote:

>> Initial version of JEP-391 backport to jdk11u.
>> Build system changes are mostly clean, except cds disabling part, it's copy&paste from aix part.
>> Things needing attention: os_bsd_aarch64.cpp and W^X transitions.
>> serviceability agent is mostly clean.
>> This passed GHA_tier1 testing.
>> Full regression testing is running now on Azul's infra, will report/update PR when done.
>> **Update: TCK passed, full regression testing is fine on intel platforms, macos/aarch64/openjdk11 is good compared to macos/aarch64/zulu11**
>> Sharing this PR slightly earlier to let other interested parties to run the tests too.
>> Example of cross-building on intel mac (needs Xcode12/13):
>> sh configure --with-boot-jdk=/Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home/ --with-build-jdk=/Library/Java/JavaVirtualMachines/zulu-11.jdk/Contents/Home/ --disable-warnings-as-errors --openjdk-target=aarch64-apple-darwin --with-extra-cflags='-arch arm64' --with-extra-ldflags='-arch arm64' --with-extra-cxxflags='-arch arm64'
>
> Vladimir Kempik has updated the pull request incrementally with one additional commit since the last revision:
> 
>   Ignore TestOnError.java on macos_aarch64

Thanks for analysis Thomas.
At Azul we have a testsuite to check java<->jni_native arguments passing on lots of different arguments combinations.
I have run them with fastdebug build on both macos11 and macos12 and found no failures

>It's weird that this is only happening in 11. Is it?

It's very weird.

The issue is intermittent which make me think it could be a rare corner case in interp wrapper generator.

If it were one more R18 failure then it would likely crash on macos12 and not macos11

-------------

PR: https://git.openjdk.java.net/jdk11u-dev/pull/715