-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8293020: jmod should not be treated as "small" tool for large modules #10062
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 shade! A progress list of the required criteria for merging this PR into |
Webrevs
|
|
@shipilev 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 23 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 |
|
/label core-libs |
|
@shipilev |
|
If anyone from core-libs crowd wants to chime in, welcome. Otherwise, I'll integrate soon. |
|
/integrate |
|
Going to push as commit d2eed07.
Your commit was automatically rebased without conflicts. |
This is similar to JDK-8245168, but the blanket change to allow all modules be compiled with default options is a net loss. Instead, we can hand-pick the major offenders (large modules) where running jmod with normal tool options improves performance.
I instrumented the jmod to tell me the times it needs to create individual modules, and hand-picked three top modules that take multiple seconds to run.
Motivational
make clean-images imagestimes:I think we can accept the
slowdebugregression in favor of improvements onreleaseandfastdebugthat most people seem to be building every day.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk pull/10062/head:pull/10062$ git checkout pull/10062Update a local copy of the PR:
$ git checkout pull/10062$ git pull https://git.openjdk.org/jdk pull/10062/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 10062View PR using the GUI difftool:
$ git pr show -t 10062Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/10062.diff