JDK-8075766 : 4.10.2.2: Clarify details for exceptional local variable array
- Type: Sub-task
- Component: specification
- Sub-Component: vm
- Affected Version: 8
- Priority: P4
- Status: Closed
- Resolution: Fixed
- Submitted: 2015-03-23
- Updated: 2018-08-03
- Resolved: 2016-09-28
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 9 |
|---|
9Fixed  |
Description
Step 4 of the data-flow analysis fails to specify that the local variable array must be computed specially (akin to the operand stack) when the successor instruction is a handler. In particular, the local variable array to be merged into the successor instruction is NOT the local variable array computed in step 2, but rather the local variable array immediately PRIOR to step 2. (The type-checking verifier models this correctly via the oft-seen clause exceptionStackFrame(StackFrame, ExceptionStackFrame).) (As a separate matter of presentation, the paragraph "In the special case of control transfer to an exception handler ..." should appear after the common-case bullets about visiting the successor instruction.)