Skip to content

Handle default conflict error for direct dispatch method handles #21540

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
matthewhall2 opened this issue Apr 1, 2025 · 0 comments
Open

Handle default conflict error for direct dispatch method handles #21540

matthewhall2 opened this issue Apr 1, 2025 · 0 comments

Comments

@matthewhall2
Copy link
Contributor

matthewhall2 commented Apr 1, 2025

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant