RFR: 8073139 PPC64: User-visible arch directory and os.arch value on ppc64le cause issues with Java tooling
asmundak at google.com
Fri Dec 4 17:55:18 UTC 2015
I am not convinced that increasing the complexity of the already quite
machinery to avoid three additional checks in the source file is the
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