JDK-6810855 : KILL vs. TEMP ordering restrictions are too strong
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: hs15
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: solaris_9
- CPU: sparc
- Submitted: 2009-02-26
- Updated: 2010-04-02
- Resolved: 2009-03-18
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 |
|---|---|---|
6u18Fixed  |
7Fixed |
hs15Fixed |
Related Reports
|
Relates :
|
Description
The support for TEMP operands in the adlc has some sanity checks that require TEMPs to come before KILLs since kill normally aren't really uses. This simplifies some of the logic for mapping between operands and inputs. The existing logic is being too strict since it complains about USE_KILLs instead of just raw KILLs. The code should be modified to ignore USE_KILLs.
Comments
|