-
Notifications
You must be signed in to change notification settings - Fork 148
8340398: [JVMCI] Unintuitive behavior of UseJVMCICompiler option #1024
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
Conversation
|
👋 Welcome back toddjonker! A progress list of the required criteria for merging this PR into |
|
@toddjonker This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be: You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 47 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. ➡️ To flag this PR as ready for integration with the above commit message, type |
|
This backport pull request has now been updated with issue from the original commit. |
|
|
|
/approval request This streamlines configuration of our JDK+Graal distro, which in turn allows two failing tests to pass without modification. A corresponding backport PR for JDK23 is openjdk/jdk23u#136 |
|
@toddjonker |
|
Hi Todd, Also, how did you test this backport? |
|
Hi Goetz, I understand there's judgement call here. The PR changes the behavior when:
Currently, Coming from the perspective of a Truffle user may be more convincing. The current behavior is such that adding While this is a behavior change, it seems unlikely that users would deploy libgraal and not want it used by JVMCI. (Certainly a Truffle user will want it!) BTW, I run tiers 1-3 on linux-x86_64-server-release and all pass modulo two tests that are known to fail in our environment. |
|
Thanks. Ok, so let's go that way. |
|
Thanks Goetz! |
|
/integrate |
|
@toddjonker |
|
/sponsor |
|
Going to push as commit b010fdc.
Your commit was automatically rebased without conflicts. |
|
@Rudometov @toddjonker Pushed as commit b010fdc. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Clean backport of patch authored by @tzezula and approved by @dougxc
The patch default-enables
useJVMCINativeLibrarywhenEnableJVMCIis on andlibgraalpresent. While this is a behavior change, it seems unlikely that users would deploylibgraaland not want it used by JVMCI.This streamlines configuration of our JDK+Graal distro, which in turn allows two failing tests to pass without modification.
Equivalent backport to 23: openjdk/jdk23u#136
Progress
Issue
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/1024/head:pull/1024$ git checkout pull/1024Update a local copy of the PR:
$ git checkout pull/1024$ git pull https://git.openjdk.org/jdk21u-dev.git pull/1024/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 1024View PR using the GUI difftool:
$ git pr show -t 1024Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/1024.diff
Webrev
Link to Webrev Comment