JDK-8213845 : ARM32: Interpreter doesn't call result handler after native calls
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: 8,9,10,11,12
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: arm
- Submitted: 2018-11-14
- Updated: 2021-04-09
- Resolved: 2018-11-23
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 11 | JDK 12 |
|---|---|
| 11.0.12Fixed | 12 b22Fixed  |
Related Reports
|
Relates :
|
Description
ARM32 interpreter and C1 doesn't use JNI call result handers properly since "returned value is already in appropriate format" (templateInterpreterGenerator_arm.cpp:32) . Now (since JDK-8209637) we have JNIBooleanTest.java test that shows the approach is not correct: the JNI call jboolean return value >1 makes a mess in further java execution.
JTwork/runtime/BoolReturn/JNIBooleanTest.jtr:
----------System.err:(13/852)----------
java.lang.RuntimeException: Error: bar(2) = false in iteration 2
at JNIBooleanTest.main(JNIBooleanTest.java:61)
Comments
|