-
Notifications
You must be signed in to change notification settings - Fork 5.8k
8202449: overflow handling in Random.doubles #8791
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 rgiulietti! A progress list of the required criteria for merging this PR into |
@rgiulietti The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
Currently, this method is specified to throw when the range [origin, bound) given by the arguments is so large that its size (bound - origin) overflows. Since the proposed implementation doesn't suffer from this limitation, the specification needs to be modified, thus the need for a CSR. |
Hi, the major code changes are in
where the checks are more tolerant, and in
that extend the accepted range. In case the range size overflows, the methods half the range, generate a value inside the reduced range and finally double the outcome. |
} else { | ||
/* avoids overflow at the cost of 3 more multiplications */ | ||
float halfOrigin = 0.5f * origin; | ||
r = (r * (0.5f * bound - halfOrigin) + halfOrigin) * 2.0f; |
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.
This could be done in double arithmetic, but I think it is better to keep it in float arithmetic for similarity with the code in the double version of the method.
@rgiulietti 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 298 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. Possible candidates are the reviewers of this PR (@jddarcy) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@rgiulietti |
/sponsor |
Going to push as commit c8cff1b.
Your commit was automatically rebased without conflicts. |
@jddarcy @rgiulietti Pushed as commit c8cff1b. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Extend the range of Random.doubles(double, double) and similar methods.
Progress
Issues
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/8791/head:pull/8791
$ git checkout pull/8791
Update a local copy of the PR:
$ git checkout pull/8791
$ git pull https://git.openjdk.java.net/jdk pull/8791/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 8791
View PR using the GUI difftool:
$ git pr show -t 8791
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/8791.diff