JDK-6891750 : deopt blob kills values in O5
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: hs17
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: solaris_9
- CPU: sparc
- Submitted: 2009-10-15
- 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 |
|---|---|---|
6u21Fixed  |
7Fixed |
hs17Fixed |
Related Reports
|
Relates :
|
Description
Sometime in 1.5 the deopt blob was rewritten to use I5 to hold a copy of the current deoptimization mode instead of O5. Before save_live_registers I5 is actually O5 which might contain a live value on 64 bit since we rely on register windows to save those values. In 32-bit mode the O registers are explicitly saved since they might contain 64 bit values. The fix is simply to use an L register as a cache like we do for G2_thread.
Comments
|