-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8267112: JVMCI compiler modules should be kept upgradable #4014
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 kvn! A progress list of the required criteria for merging this PR into |
Looks good. My only suggestion would have been to avoid mentioning "Graal" in the PR title and description. This is really about making |
@vnkozlov 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 41 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. ➡️ To integrate this PR with the above commit message to the |
Thank you, Mandy. |
/reviewer credit @dougxc |
@vnkozlov |
@erikj79, are you okay with these changes? |
Thank you, Erik. |
/integrate |
@vnkozlov Since your change was applied there have been 41 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 2effdd1. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
JDK-8264806 changes removed sources and also removed JVMCI compiler from list of upgradable modules. JVMCI compiler modules should be upgradable in JDK to work with GraalVM.
Make these modules upgradable again and empty by leaving only reference to JVMCI (jdk.internal.vm.ci) module. It does not restore sources - only
module-info.java
files are kept.Note, we continue discussion about JDK-8265091: "Use Module API to export JVMCI packages at runtime" to see if we can remove these
module-info.java
files.Changes were proposed by @dougxc after testing JDK-8264806 changes with GraalVM.
I restored related code in some tests for them to pass.
Testing: full tier1-tier3.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/4014/head:pull/4014
$ git checkout pull/4014
Update a local copy of the PR:
$ git checkout pull/4014
$ git pull https://git.openjdk.java.net/jdk pull/4014/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 4014
View PR using the GUI difftool:
$ git pr show -t 4014
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/4014.diff