JDK-6913075 : EA identifies escape state incorrectly after 6895383 fix
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: hs17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: solaris_10
- CPU: sparc
- Submitted: 2009-12-23
- Updated: 2010-04-03
- Resolved: 2010-01-19
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
In some cases EA incorrectly identifies escape state of allocations passed as call arguments. It use ArgEscape instead of GlobalEscape which leads to incorrect elimination of locks.
Comments
|