-
Notifications
You must be signed in to change notification settings - Fork 733
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
Add SVM validations for JITServer ResolvedHandle/DynamicMethod APIs #20875
Conversation
@mpirvu could you please review? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Conflicts must be resolved before starting testing. |
The JITServer version of getResolvedDynamicMethod and getResolvedHandleMethod were missing SVM validations, which caused errors when generate AOT support for Method Handles with JITServer. Signed-off-by: Irwin D'Souza <[email protected]>
8bed0ad
to
58b5f4d
Compare
jenkins test sanity plinuxjit,xlinuxjit,zlinuxjit,alinux64jit jdk21 |
All failing tests look like this:
Looking at the actual test output:
Not really sure why the test is failing, but either way it doesn't look related to this change since the change is AOT related and AOT MH is not enabled by default. |
All the VectorAPI tests are currently failing with JITServer because the verbose options are global and are not passed to the server. This is a known issue and needs to be fixed by changing the tests to look at JIT compilation logs and not at vlogs. vlogs are mostly for runtime diagnostics and not for optimizer diagnostics. |
Since all failures are known, this PR is ready to be merged. |
The JITServer version of getResolvedDynamicMethod and getResolvedHandleMethod were missing SVM validations, which caused errors when enabling AOT support for Method Handles with JITServer.