-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8344414: ZGC: Another division by zero in rule_major_allocation_rate #22228
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 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 72 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
|
fisk
left a comment
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.
Looks good.
Added tag jdk-24+26 for changeset 8485cb1
fisk
left a comment
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.
Even better.
|
Thanks for the reviews. |
|
Going to push as commit 63af2f4.
Your commit was automatically rebased without conflicts. |
This specific issue was known since #20888. As well as a more serious issue in
calculate_extra_young_gc_timewhich may introduce aNaN. This specific issue is sane as long as we have IEEE 754 sans the C++ standard making division by zero UB.As discussed in #21304 it is probably better to try and tackle the division by zero issue by making sure the input is never zero. This patch introduces a small offset to the average which will effectively leave the value unchanged unless it is zero, and behave as almost zero in calculations without causing actual division by zero.
There is still the issue with
NaN, this patch adds a short circuit when this can occur and returns the analytical result of the calculation.Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/22228/head:pull/22228$ git checkout pull/22228Update a local copy of the PR:
$ git checkout pull/22228$ git pull https://git.openjdk.org/jdk.git pull/22228/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 22228View PR using the GUI difftool:
$ git pr show -t 22228Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/22228.diff
Using Webrev
Link to Webrev Comment