Details
-
Enhancement
-
Resolution: Fixed
-
P3
-
None
-
None
-
b23
Backports
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8149188 | 8u101 | Gerald Thornbrugh | P3 | Resolved | Fixed | b01 |
JDK-8145820 | 8u92 | Gerald Thornbrugh | P3 | Resolved | Fixed | b02 |
JDK-8155264 | emb-8u101 | Gerald Thornbrugh | P3 | Resolved | Fixed | b01 |
Description
When configuring the hotspot build the build system sets up the ARCH variable to reflect the target cpu. Currently the value is initialized to OPENJDK_TARGET_CPU_LEGACY, which is the internal legacy cpu name. For example, on x86 64-bit this is amd64 on linux (but x86_64 on mac).
Depending on the platform ARCH is either honored or ignored. Solaris for example overrides the value of ARCH with the output from 'uname -p' (see hotspot/make/solaris/makefiles/defs.make). On BSD/OSX the value is also overidden, but with the output from 'uname -m' (see hotspot/make/bsd/makefiles/defs.make). Windows is.. different.
On Linux the ARCH variable is honored, but if it is *not* set it is initialized to the output from 'uname -m' (see hotspot/make/linux/makefiles/defs.make).
The goal in the new (JDK) build system is to have the "legacy" value gradually removed in favor of the other variables. We should move towards setting ARCH to OPENJDK_TARGET_CPU_ARCH instead of OPENJDK_TARGET_CPU_LEGACY and make sure the Hotspot build system picks it up correctly.
Depending on the platform ARCH is either honored or ignored. Solaris for example overrides the value of ARCH with the output from 'uname -p' (see hotspot/make/solaris/makefiles/defs.make). On BSD/OSX the value is also overidden, but with the output from 'uname -m' (see hotspot/make/bsd/makefiles/defs.make). Windows is.. different.
On Linux the ARCH variable is honored, but if it is *not* set it is initialized to the output from 'uname -m' (see hotspot/make/linux/makefiles/defs.make).
The goal in the new (JDK) build system is to have the "legacy" value gradually removed in favor of the other variables. We should move towards setting ARCH to OPENJDK_TARGET_CPU_ARCH instead of OPENJDK_TARGET_CPU_LEGACY and make sure the Hotspot build system picks it up correctly.
Attachments
Issue Links
- backported by
-
JDK-8145820 Use OPENJDK_TARGET_CPU_ARCH instead of legacy value for hotspot ARCH
-
- Resolved
-
-
JDK-8149188 Use OPENJDK_TARGET_CPU_ARCH instead of legacy value for hotspot ARCH
-
- Resolved
-
-
JDK-8155264 Use OPENJDK_TARGET_CPU_ARCH instead of legacy value for hotspot ARCH
-
- Resolved
-
- relates to
-
JDK-8048232 Fix for 8046471 breaks PPC64 build
-
- Resolved
-
-
JDK-8146979 Backport of 8046471 breaks ppc64 build in jdk8u because 8072383 was badly backported before
-
- Closed
-