RFR: 8073139 PPC64: User-visible arch directory and os.arch value on ppc64le cause issues with Java tooling
david.holmes at oracle.com
Mon Dec 7 01:08:09 UTC 2015
On 5/12/2015 3:55 AM, Alexander Smundak wrote:
> I am not convinced that increasing the complexity of the already quite
> intricate build
> machinery to avoid three additional checks in the source file is the
> right trade-off.
Does that mean you looked at how to achieve this?
I think there is a more general issue that a ppc64le build is-a ppc64
build, so the latter should always be defined.
> On Thu, Dec 3, 2015 at 11:59 PM, David Holmes <david.holmes at oracle.com> wrote:
>> On 4/12/2015 4:29 AM, Alexander Smundak wrote:
>>> On Wed, Dec 2, 2015 at 10:30 PM, David Holmes <david.holmes at oracle.com>
>>>> agent code:
>>>> I'm still unclear why you can't, or shouldn't, pass through -Dppc64 and
>>>> -Dppc64le, such that you don't need to check for either being defined ??
>>> You mean, add -Dppc64 to the compilation flags explicitly if the value
>>> of the OPENJDK_TARGET_CPU_LEGACY is 'ppc64le'?
>> Yes. Is that feasible?
More information about the hotspot-dev