[aarch64-port-dev ] Review Request JDK-8175819: OS name and arch in JMOD files should match the values as in the bundle name

[Stuart Monteith]

ARMv8-A introduced the AArch64 execution state and the A64 instruction
set. The AArch32 execution state was created with the T32 and A32
instruction sets (that are almost identical to the ARMv7 instruction
sets). Officially, "arm64" has no meaning. Unfortunately, adoption of
this terminology hasn't been consistent, but I believe it is fitting
that OpenJDK is consistent with the GNU triples, which do use aarch64.
"arm64", at best, seems to mean machines/kernels that support ARMv8-A,
which may or may not have AArch64 support.

BR,
    Stuart



On 4 April 2017 at 09:39, Andrew Haley <aph at redhat.com> wrote:
> On 04/04/17 09:04, Magnus Ihse Bursie wrote:
>> Why change from the well-established "aarch64" to the virtually unused
>> "arm64"? As far as I know, using the name "arm64" for the aarch64
>> platform is something that has only been done in the (recently opened)
>> closed Oracle port. This change, however, proposes to change the value
>> in the release file even for the open aarch64 port, which has always
>> been known by that name.
>
> That's definitely wrong.  The name of the architecture is "aarch64".
> "arm64" is not a thing.
>
> Andrew.
>