JDK-8016491 : PPC64 (part 2): Clean up PPC defines.
  • Type: Enhancement
  • Component: hotspot
  • Sub-Component: runtime
  • Affected Version: port-stage-ppc-aix
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: ppc
  • Submitted: 2013-06-12
  • Updated: 2016-10-24
  • Resolved: 2013-06-21
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8 JDK 9 Other
8u20Fixed 9Fixed openjdk7u,port-stage-ppc-aixFixed
Description
This is preparation for PPC64 integration: http://openjdk.java.net/jeps/175
This and following ppc64 changes will go into staging repository first and tested there: http://hg.openjdk.java.net/ppc-aix-port/stage/

Reorganize PPC defines.  Distinguish PPC, PPC64 and PPC32.
PPC should guard code needed on PPC regardless of word size.
PPC32 and PPC64 should guard code needed in the 64-bit or
the 32-bit port.

http://hg.openjdk.java.net/ppc-aix-port/jdk8/hotspot/file/df79d76c17ab/ppc_patches/0002_PPC_defines.patch
Comments
Author: goetz Date: 2013-06-19 12:29 +0200 URL: http://hg.openjdk.java.net/ppc-aix-port/stage/hotspot/rev/0f03ff49c720
21-06-2013
We don't use 3 architecture designators on other platforms to distinguish between "common", 32-bit and 64-bit, so why do we need to do so for PPC ? The normal approach would be to add _LP64=1 specific ifdefs within an architectural ifdef.
13-06-2013