JDK-6964498 : JSR 292 invokedynamic sites need local bootstrap methods
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 7
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2010-06-26
- 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 |
|---|---|---|
| 6u21pFixed | 7Fixed  |
hs19Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
In order to be compositional, invokedynamic instructions should individually specify their linkage semantics, in the form of a reference to a bootstrap method. This is fairly straightforward, since (a) the constant pool already contains method handle references, and (b) the invokedynamic index can be treated as an ordered pair of BSM and NameAndType, just as an invokevirtual index is treated as an ordered pair of class and NameAndType. The Java language support will need a way (presumably based on JSR 308 annotations) to specify the bootstrap methods.
Comments
|