JDK-6939203 : JSR 292 needs method handle constants
- Type: Bug
- Component: hotspot
- Sub-Component: compiler
- Affected Version: 7
- Priority: P3
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2010-03-30
- 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 :
|
Description
In order to compile constant references to method handles and method types, the constant pool structure needs to be able to represent method handle references, and the ldc instruction updated (as it was for Class constants). This feature completes the role of method handle as a lightweight but dynamic access point to any bytecode operation. Without the ability to perform 'ldc', building a handle to a proposed bytecode level member access is 1-2 orders of magnitude more expensive, requiring a reflective lookup. For a draft specification, see the package information in the JSR 292 javadoc. It is posted here for review: http://cr.openjdk.java.net/~jrose/pres/indy-javadoc-mlvm/
Comments
|