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

[Bob Vandette]

I checked with the hotspot compiler team and their manager and they are ok with
using the labels “arm64” and “aarch64” to mark bugs that are specific to 64-bit aarch64
builds that are done using hotspot/src/cpu/arm versus hotspot/src/cpu/aarch64 sources.

Please publicize this label’s use throughout interested OpenJDK developers.

Bob.


> On Mar 16, 2017, at 2:40 PM, Bob Vandette <bob.vandette at oracle.com> wrote:
> 
> 
>> On Mar 16, 2017, at 2:27 PM, Andrew Haley <aph at redhat.com> wrote:
>> 
>> On 16/03/17 18:03, Bob Vandette wrote:
>> 
>>> I agree that this is an issue but I’m not sure that it’s a show
>>> stopper.
>>> 
>>> The Oracle build will not have OpenJDK in the version string which
>>> will help to differentiate our binaries from OpenJDK builds.
>> 
>> Right, like I said.
>> 
>>> The bug database field that I think you are describing is only an
>>> indication of the architecture that a bug can be reproduced on.  It
>>> is not meant to describe the sources that were used to produce the
>>> binaries or where the binaries came from.  That should to be
>>> specified elsewhere in the bug report.
>> 
>> OK.  I would surely have tried to insist that the version strings were
>> different for our two ports at the time your port was committed, but I
>> blew my chance.
>> 
>>> I don’t like the idea of listing arm64 in the version string since
>>> we are only using arm64 internally to trigger the use of the hotspot
>>> “arm” directory.  We’d also end up with lots of incorrect bug
>>> entries since folks will fail to use arm64 to report a bug in the
>>> Oracle 64-bit ARM port running on an aarch64 based system.
>>> 
>>> If we start putting build configuration information in the version
>>> string, then where do we stop.
>> 
>> It's going to be rather horrible, though.  How do we reproduce a bug
>> if we don't know what port is causing the bug?  How do we even ask the
>> question if we don't know what the ports are called?  I always assumed
>> we were "aarch64" and you were "arm64".  How are we to ask a user if
>> we can't tell them what to look for?
>> 
>> Even if we don't change anything in OpenJDK itself, we'll still have
>> to agree on a label to use in the bug database.  I don't know what
>> labels we should use, but we should agree on them now.  Do you have
>> any preferences?
> 
> I agree that a label would be very useful.  For this purpose, I’m not opposed
> to using the arm64 versus aarch64 names.   Let me check around to see
> if anyone has a better suggestion.
> 
> Bob.
> 
> 
> 
>> 
>> Andrew.
>