JDK-8177390: java -version does not differentiate between which port of AArch64 is used

[David Holmes]

I won't be able to look at this until Monday. But adding a property will 
require CCC and careful consideration.

David

On 25/03/2017 3:45 AM, Bob Vandette wrote:
>
>> On Mar 24, 2017, at 1:40 PM, Mario Torre <neugens at redhat.com> wrote:
>>
>> On Fri, Mar 24, 2017 at 6:24 PM, Bob Vandette <bob.vandette at oracle.com> wrote:
>>
>>>> Would that be acceptable?
>>>
>>> I’m not opposed to the approach, just the name of the property.
>>>
>>> The “community” is free to build a 64-bit (aarch64) ARM port from either hotspot/src/cpu/arm
>>> or hotspot/src/cpu/aarch64 sources, so aarch64.community.port is a bit misleading since
>>> binaries produced from either port can be a “community” port.
>>>
>>> What we are trying to differenciate are the two difference cpu and os_cpu directories
>>> used to produce an aarch64 image.  I’m hopeful that one day, we’ll consolidate these
>>> two ports so I don’t want to do anything too permanent.
>>>
>>> Can we use the property hotspot.target.cpu.port={aarch64,arm}
>>
>> Absolutely, I wasn't very happy with it either, and the Oracle port is
>> a "community" port too, after all.
>>
>> Do you want me to also add "arm" to the -Xinternalversion string
>> output like I did with "aarch64”?
>
> Yes, but let’s make sure David Holmes is also ok with the approach.
>
> We might want to put (hotspot.target.cpu.port=arm or aarch64) in the -Xinteralversion string
> instead of just the cpu name.
>
> Bob.
>
>>
>> Cheers,
>> Mario
>