-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8371672: G1: G1YoungGenSizer handling of NewRatio, NewSize and MaxNewSize #28255
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
base: master
Are you sure you want to change the base?
Conversation
|
👋 Welcome back aboldtch! A progress list of the required criteria for merging this PR into |
|
@xmas92 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 101 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 |
Webrevs
|
|
/issue add JDK-8370494 |
|
/issue add JDK-8370494 |
|
@xmas92 |
| } else if (user_specified_NewSize) { | ||
| _sizer_kind = SizerNewSizeOnly; | ||
| } else { | ||
| assert(user_specified_MaxNewSize, ""); |
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.
postcond(
G1YoungGenSizer ignores these values if they are not from the command line. Resulting in a different _sizer_kind than expected.
The NewSize and MaxNewSize are also not bounded by the Initial and Max heap size respectively (JDK-8370494).
I suggest we rewrite this logic using
!FLAG_IS_DEFAULTto always get the correct behaviour. And only useFLAG_IS_CMDLINEfor issuing warnings to the user when we ergonomically change or ignore these values to be compatible.As well as adding the proper truncation for HeapSize incompatible values.
Progress
Issues
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28255/head:pull/28255$ git checkout pull/28255Update a local copy of the PR:
$ git checkout pull/28255$ git pull https://git.openjdk.org/jdk.git pull/28255/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 28255View PR using the GUI difftool:
$ git pr show -t 28255Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28255.diff
Using Webrev
Link to Webrev Comment