JDK-8031188 : Fix for 8029015: PPC64 (part 216): opto: trap based null and range checks
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: port-stage-ppc-aix
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- CPU: ppc
- Submitted: 2014-01-06
- Updated: 2014-07-29
- Resolved: 2014-01-07
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.
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 |
Description
fixup_flow can add new blocks with a branch instruction. Doing so after a trap based check added the branch behind the wrong Proj node. The branch would jump to the proper target, but build_oop_map analyses a wrong control flow. Fix: Swap the Projs in the block list so that the new block is added behind the proper node.