RFR: 8073139 PPC64: User-visible arch directory and os.arch value on ppc64le cause issues with Java tooling
david.holmes at oracle.com
Wed Dec 9 03:10:23 UTC 2015
I can sponsor for you Sasha. Just email me the changeset, or a link thereto.
On 9/12/2015 3:44 AM, Alexander Smundak wrote:
> Thank you for the review.
> If everyone involved is satisfied with the patch, I need a sponsor.
> On Mon, Dec 7, 2015 at 8:46 PM, David Holmes <david.holmes at oracle.com> wrote:
>> On 8/12/2015 1:44 PM, Alexander Smundak wrote:
>>> It is achievable by adding a small ppc-specific check to the
>>> @@ -282,6 +282,8 @@
>>> elif test "x$OPENJDK_TARGET_OS" != xmacosx && test
>>> "x$OPENJDK_TARGET_CPU" = xx86_64; then
>>> # On all platforms except MacOSX replace x86_64 with amd64.
>>> + elif test "x$OPENJDK_TARGET_CPU" = xppc64le; then
>>> + OPENJDK_TARGET_CPU_LEGACY="ppc64"
>>> However, there is a code in make/Images.gmk using
>>> $(call info-file-item, "OS_ARCH", "$(OPENJDK_TARGET_CPU_LEGACY)")
>>> so that the 'release' file in the image directory will now have
>>> instead of "ppc64le".
>>> If someone can tell me which other variable I should use to achieve
>>> that without changing the contents of the 'release' file on other
>>> platforms, I'll be grateful.
>> Okay never mind - and thanks for looking into this. I see now this is set
>> ./autoconf/flags.m4: COMMON_CCXXFLAGS_JDK="$COMMON_CCXXFLAGS_JDK
>> -DARCH='\"$OPENJDK_TARGET_CPU_LEGACY\"' -D$OPENJDK_TARGET_CPU_LEGACY"
>> so there is no way to add a second value without introducing some additional
>> variable. At the hotspot level it could be handled differently if we had a
>> platform_ppc64le file, as it could just be added to the SYSDEFS.
More information about the hotspot-dev