JDK-8209414 : AArch64: method handle invocation does not respect JVMTI interp_only mode
- Type: Bug
- Component: hotspot
- Sub-Component: svc
- Affected Version: 8-aarch64,11,12,13
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: linux
- CPU: aarch64
- Submitted: 2018-08-13
- Updated: 2022-07-20
- Resolved: 2019-01-09
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 | JDK 13 | Other |
|---|---|---|---|
| 11.0.17-oracleFixed | 12 b27Fixed  |
13Fixed |
openjdk8u292Fixed |
Related Reports
|
Relates :
|
Description
2 test cases of Java debug interface related failed on some AArch64 machines vmTestbase/vm/mlvm/indy/stress/jdi/breakpointInCompiledCode/Test.java vmTestbase/vm/mlvm/meth/func/jdi/breakpoint/Test.java When the interpreter dispatches a method, it should check the JavaThread::interp_only_mode_offset() field in the thread structure, and if it's non-zero call the interpreted entry point even if a compiled entry exists. When we use a java.lang.invoke.MethodHandle to invoke a method, the method dispatch is instead handled by a special intrinsic that's implemented in methodHandles_aarch64.cpp. This eventually calls MethodHandles::jump_from_method_handle which checks the JVMTI interp_mode_only flag. But the test is incorrect.
Comments
|