JDK-8059880 : Get rid of LambdaForm interpretation
- Type: Bug
- Component: core-libs
- Sub-Component: java.lang.invoke
- Affected Version: 8u40,9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2014-10-07
- Updated: 2016-05-27
- Resolved: 2014-11-24
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 8 | JDK 9 |
|---|---|
8u40Fixed  |
9 b42Fixed |
Description
LambdaForm interpretation consumes excessive amount of stack space (up to 7 frames per MethodHandle in the chain). LambdaForm sharing significantly reduce LambdaForm interpretation. It allows to completely turn off interpretation (effectively -Djava.lang.invoke.MethodHandle.COMPILE_THRESHOLD=0) without causing startup/warmup regressions.
Comments
|