JDK-6468406 : PhiNode Identity & Ideal must find the same unique input patterns
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 5.0
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: solaris_9
- CPU: sparc
- Submitted: 2006-09-07
- Updated: 2010-04-02
- Resolved: 2006-11-14
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 |
|---|---|---|
6u4Fixed  |
7Fixed |
hs10Fixed |
Description
Mostly a refactoring of the code in PhiNode's Identity and Ideal which identified phi's receiving a unique value on multiple control paths, possibly masked by constaint casts and self loops. The factored code was encapsulated in a new method PhiNode::unique_input. This fixes a bug caused by PhiNode Identity and Ideal not looking for the same patterns. Also, common code was factored out from PhiNode's Identity and Ideal which looked for patterns like: x = (x==0)?0:x and generalized to allow constraint casts in the pattern.
Comments
|