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

[Andrew Haley]

On Tue, 14 Dec 2021 15:17:55 GMT, Andrew Haley <aph at openjdk.org> wrote:

>>> > Rosetta's JDK performance is subpar. Also one need to consider rosetta's bugs which might interfere with jdk. And last point - rosetta won't be there forever.
>>> 
>>> Sure, all true, although last time I looked Rosetta was only 40% worse. Rosetta won't be there forever, but it might outlive JDK 11. We'll have to take everything into account, and review this very carefully.
>>> 
>>> Just for my information: if I apply this, will it be essentially identical to aarch64-port/jdk11u ?
>> 
>> It's an outdated version there, basically what was in zulu11 by that time.
>> But the jep-391 (for jdk17) had evolved before reaching the final version, W^X is different at least
>> This PR is partly based on that old patch, for os_bsd_aarch64.cpp, rest is a backport of the newer JEP-391 from upstream.
>
>> > Just for my information: if I apply this, will it be essentially identical to aarch64-port/jdk11u ?
>> 
>> It's an outdated version there, basically what was in zulu11 by that time. But the jep-391 (for jdk17) had evolved before reaching the final version, W^X is different at least This PR is partly based on that old patch, for os_bsd_aarch64.cpp, rest is a backport of the newer JEP-391 from upstream.
> 
> Ouch! That's terrible, I had no idea. So everybody who is building AArch64 from non-Azul trees has a broken release.

> @theRealAph FYI, about possible consequences for other platforms in jdk11u-dev JDK-8253816: Support macOS W^X it's all under MACOS_AARCH64_ONLY, so isolated to just one platform

Sure, but this is a failure of process. It means that AArch64/MacOS would be going straight in to 11u mainline without being first baked in AArch64-port/11u.

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

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