JDK-8043235 : Type-based optimizations interfere with continuation methods
- Type: Bug
- Component: core-libs
- Sub-Component: jdk.nashorn
- Affected Version: 9
- Priority: P2
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2014-05-15
- Updated: 2015-01-21
- Resolved: 2014-05-15
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 b17Fixed |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
Description
CodeGenerator has some type-based optimizations that only work for expressions of object types (namely, nullCheck and undefinedCheck). These optimizations kick in also if their operands get deoptimized to Object type even if they had a narrower type earlier. Transferring the control from a method to its continuation (rest-of) version is sensitive to having the same shape of stack at the same call sites as the method being deoptimized; these two optimizations violate this invariant though, and need to be disabled when they would affect the shape of the stack.