[aarch64-port-dev ] RFR: 8168503 JEP 297: Unified arm32/arm64 Port (original) (raw)
Bob Vandette bob.vandette at oracle.com
Tue Mar 21 15:25:58 UTC 2017
- Previous message: [aarch64-port-dev ] RFR: 8168503 JEP 297: Unified arm32/arm64 Port
- Next message: [aarch64-port-dev ] RFR: 8168503 JEP 297: Unified arm32/arm64 Port
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I’d prefer to use something like these System properties.
"java.vendor" JRE vendor name "java.vendor.url" JRE vendor URL
or to add something to the “release” file.
HOTSPOT_ARCH_DIR=arm
or
HOTSPOT_ARCH_DIR=aarch64
Bob.
On Mar 21, 2017, at 10:26 AM, Andrew Haley <aph at redhat.com> wrote:
On 16/03/17 18:03, Bob Vandette wrote: If we start putting build configuration information in the version string, then where do we stop. Two separate ports is pretty large for a "build configuration issue". How about we define a unique global dynamic symbol? Then, at least, it's just a matter of using nm or equivalent to have a look at which port we have. Andrew.
- Previous message: [aarch64-port-dev ] RFR: 8168503 JEP 297: Unified arm32/arm64 Port
- Next message: [aarch64-port-dev ] RFR: 8168503 JEP 297: Unified arm32/arm64 Port
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]