JDK-8029025 : PPC64 (part 203): opto: Move static _in_dump_cnt to Compile object.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: port-stage-ppc-aix
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2013-11-22
  • Updated: 2014-07-29
  • Resolved: 2013-11-23
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 port-stage-ppc-aixFixed
To allow some special cases when dumping debug information about IR
nodes, _in_dump_cnt can be increased. Unfortunately this is a global
field.  If running with more than one compiler thread races can happen.
As consequence, dumping crashes e.g. in MachProjNode::adr_type().

This change moves the field to the Compile object.

It also introduces the compiler oracle 'option' feature for PrintAssembly.


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/