-
Bug
-
Resolution: Fixed
-
P1
-
9, 10, 11
-
b28
-
s390x
-
linux
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8210173 | 12 | Volker Simonis | P1 | Resolved | Fixed | b09 |
JDK-8210082 | 11.0.2 | Volker Simonis | P1 | Resolved | Fixed | b01 |
JDK-8210074 | 11.0.1 | Volker Simonis | P1 | Resolved | Fixed | b08 |
The template interpreter for s390x doesn't call the result handler in the native entry. This can lead to wrong results being passed as return values from native calls which return jboolean values if these values are not exactly '1' or '0' (i.e. a return value of '2' will be interpreted as 'false').
The result handler normalizes such results and maps any value > 0 to 'true'.
The result handler normalizes such results and maps any value > 0 to 'true'.
- backported by
-
JDK-8210074 [s390x] Interpreter doesn't call result handler after native calls
-
- Resolved
-
-
JDK-8210082 [s390x] Interpreter doesn't call result handler after native calls
-
- Resolved
-
-
JDK-8210173 [s390x] Interpreter doesn't call result handler after native calls
-
- Resolved
-
- relates to
-
JDK-8211064 [AArch64] Interpreter and c1 don't correctly handle jboolean results in native calls
-
- Resolved
-
-
JDK-8213845 ARM32: Interpreter doesn't call result handler after native calls
-
- Resolved
-