JDK-8012125 : Comments for ConstantPoolCache should reflect the addition of resolved_references in ConstantPool
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 8
- Priority: P5
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2013-04-12
- Updated: 2014-06-26
- Resolved: 2014-03-27
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 b08Fixed  |
Related Reports
|
Relates :
|
Description
The new MethodHandle implementation (LambdaForm) places "appendix argument" in the ConstantPoolCache when resolving invokedynamic and invokehandle bytecodes. It used to be stored in ConstantPoolCache::_f1 before NPG (JDK-6984705), but it is stored in the resolved_references array in ConstantPool now instead (JDK-6964458). The comments in ConstantPoolCache for the _f1 field missed this change, and should be updated.