JDK-6953576 : bottom_type for matched AddPNodes doesn't always agree with ideal
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: hs17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: solaris_9
- CPU: sparc
- Submitted: 2010-05-18
- Updated: 2010-09-24
- Resolved: 2010-06-01
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 |
|---|---|---|
| 6u21pFixed | 7Fixed  |
hs19Fixed |
Description
6715633 added an assert to make sure that the adr_type of nodes doesn't change during matching. If the address pieces are matched separately this assert can fail because the logic in AddPNode::mach_bottom_type isn't the equivalent to AddPNode::bottom_type. The fix is to simply capture the bottom_type when transforming the nodes.
Comments
|