JDK-6914206 : change way of permission checking for generated MethodHandle adapters
- Type: Enhancement
- Component: hotspot
- Sub-Component: compiler
- Affected Version: hs17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2010-01-05
- Updated: 2013-01-31
- Resolved: 2010-01-19
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 |
|---|---|---|
6u21Fixed  |
7Fixed |
hs17Fixed |
Description
Currently generated MH adapters are faked to be in the same class as the callee to overcome permission problems. I would be better, also for inlining heuristics, to put these adapters in the InvokeDynamic/MethodHandle classes to be able to indentify them easily in the compiler.
Comments
|