[aarch64-port-dev ] RFR: 8168503 JEP 297: Unified arm32/arm64 Port

[Andrew Haley]

I've just noticed a nasty problem.  "java -version" on AArch64 gives
no clue about which version of HotSpot, Oracle's or the aarch64-port
project, is running.  I hadn't realized that the version wasn't going
to appear anywhere.

And all that a crash says is

#  SIGSEGV (0xb) at pc=0x0000007fb7a0c2e4, pid=44736, tid=44737
#
# JRE version:  (9.0) (build )
# Java VM: OpenJDK 64-Bit Server VM (9-internal+0-adhoc.aph.hs, mixed mode, tiered, compressed oops, g1 gc, linux-aarch64)

There is a bit more in the log:

---------------  S U M M A R Y ------------
Command Line:
Host: AArch64 Processor rev 0 (aarch64), 48 cores, 62G, Random Linux Distro

I guess the Oracle proprietary release will have the Oracle copyright
etc., so that one wil be clear enough, and if it's from a Linux distro
we'll know which port they use, unless some distro (Gentoo?  Debian?)
is crazy enough to package both versions, in which case it's their
problem.

I had assumed that Oracle's port would call itself "arm64" or
somesuch, to distinguish it.

Even the bug database only has "aarch32" and "aarch64", so it's going
to be crazy hard to distinguish which port has a bug.  We should
really get that fixed.

It's funny how this stuff comes out of the woodwork.

Andrew.