JDK-8072016 : Array copy may cause infinite cycle of deoptimization/compilation
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-01-30
- Updated: 2015-06-03
- Resolved: 2015-02-11
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 9 |
|---|
9 b52Fixed  |
Related Reports
|
Relates :
|
Description
LibraryCallKit::inline_arraycopy() checks if we've seen too many traps at current method/bytecode but in case of tightly couples allocation we record the trap at the method/bci of the allocation.
Comments
|