JDK-6625997 : CastPP, CheckCastPP and Proj nodes are not dead loop safe
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 7
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: solaris_9
- CPU: sparc
- Submitted: 2007-11-05
- Updated: 2011-03-08
- Resolved: 2011-03-08
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 6 | JDK 7 | Other |
|---|---|---|
6u14Fixed  |
7Fixed |
hs11Resolved |
Description
CastPP, CheckCastPP and Proj nodes are not "dead" loop safe after the putback 20061023120554.jrose.dolphin-cleanups which added new mmethods Ideal_allocation(), Ideal_klass(), Ideal_length(). These methods could bypass the nodes chain to get a klass or an array's length from inputs of Allocation node: Allocate <- Proj <- CheckCastPP. As result dead data loop could be created.
Comments
|