Some cleanup in the interp_only_mode implementation is needed:
- The interp_only_mode in JavaThread is represented with a counter that is increment and decremented. This value should only take values 0 and 1. An assert is needed when it is going out of bounds.
- The function JvmtiThreadState::process_pending_interp_only() does a sync on the the JvmtiThreadState_lock which is not really needed and can be removed. It is called in a VTMS transition and so, can not clash with the SetEventNotificationMode because it sets a JvmtiVTMSTransitionDisabler.
- The interp_only_mode in JavaThread is represented with a counter that is increment and decremented. This value should only take values 0 and 1. An assert is needed when it is going out of bounds.
- The function JvmtiThreadState::process_pending_interp_only() does a sync on the the JvmtiThreadState_lock which is not really needed and can be removed. It is called in a VTMS transition and so, can not clash with the SetEventNotificationMode because it sets a JvmtiVTMSTransitionDisabler.
- causes
-
JDK-8357800 Initialize JvmtiThreadState bool fields with bool literals
-
- Resolved
-
- links to
-
Commit(master)
openjdk/jdk/411a63ea
-
Review(master)
openjdk/jdk/25060