JDK-8218004 : Clean up terminology for shared methods within the JVM for indy and condy support
- Type: Enhancement
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 13
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2019-01-29
- Updated: 2019-08-15
- Resolved: 2019-02-13
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 13 |
|---|
13 b08Fixed  |
Related Reports
|
Relates :
|
Description
Many methods in the JVM are used by both invokedynamic and dynamic constant but still have a name that contains the word "invoke_dynamic" within them. For example: ConstantPool::invoke_dynamic_name_and_type_ref_index_at ConstantPool::invoke_dynamic_bootstrap_specifier_index ConstantPool::invoke_dynamic_operand_base This is a small enhancement task to clean up these names with the intention of making them more common for both indy and condy.