You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On x86 (or any platform with JitDispatchJ9Method enabled), there is an optimization in J9RecognizedCallTransformer::process_java_lang_invoke_MethodHandle_linkToStaticSpecial which directly dispatches the method handle. At the moment this is not an issue, but the fix for #20677 needs to change the extra field of the J9Method to J9_JIT_NEVER_TRANSLATE, which causes an Invalid JIT return address error in the stack walker. This is may be due to vm->initialMethods.throwDefaultConflict having no ROM method.
Dealing with this will likely also fix #21193, so opening this issue to discuss separately.
The text was updated successfully, but these errors were encountered:
On x86 (or any platform with JitDispatchJ9Method enabled), there is an optimization in
J9RecognizedCallTransformer::process_java_lang_invoke_MethodHandle_linkToStaticSpecial
which directly dispatches the method handle. At the moment this is not an issue, but the fix for #20677 needs to change theextra
field of the J9Method toJ9_JIT_NEVER_TRANSLATE
, which causes an InvalidJIT return address
error in the stack walker. This is may be due tovm->initialMethods.throwDefaultConflict
having no ROM method.Dealing with this will likely also fix #21193, so opening this issue to discuss separately.
The text was updated successfully, but these errors were encountered: