-
Notifications
You must be signed in to change notification settings - Fork 92
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
8324646: Avoid Class.forName in SecureRandom constructor #258
8324646: Avoid Class.forName in SecureRandom constructor #258
Conversation
👋 Welcome back ogillespie! A progress list of the required criteria for merging this PR into |
This backport pull request has now been updated with issue from the original commit. |
|
Webrevs
|
/approval request Performance improvement in SecureRandom. which I have seen on the hot path. Clean backport, simple change with low risk in my opinion. |
@olivergillespie |
Hi @olivergillespie |
/approval request Performance improvement in SecureRandom, which I have seen on the hot path. Clean backport, simple change with low risk in my opinion (re-requesting now for July update and it has been in tip for a few weeks). Similar to 8324648 which was just approved. |
@olivergillespie |
@olivergillespie, please back port to 22, too, also, there are failing tests. removing the label |
Thanks, sorry @GoeLin for not understanding the backport procedure properly. I thought approval came first, before final testing/review etc., my mistake! Backport to 22 (approval requested): openjdk/jdk22u#98 Tests are now passing after merging from master. Benchmark results (
Hopefully I didn't miss anything this time, so I'll request approval again - thanks. |
/approval request Performance improvement in |
@olivergillespie |
@olivergillespie 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 22 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 (@shipilev) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
/integrate |
@olivergillespie |
/sponsor |
Going to push as commit eaa8ed9.
Your commit was automatically rebased without conflicts. |
@shipilev @olivergillespie Pushed as commit eaa8ed9. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Hi all,
This pull request contains a backport of commit 8ef918d6 from the openjdk/jdk repository.
The commit being backported was authored by Oli Gillespie on 9 Feb 2024 and was reviewed by Aleksey Shipilev and Weijun Wang.
Thanks!
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk21u-dev.git pull/258/head:pull/258
$ git checkout pull/258
Update a local copy of the PR:
$ git checkout pull/258
$ git pull https://git.openjdk.org/jdk21u-dev.git pull/258/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 258
View PR using the GUI difftool:
$ git pr show -t 258
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk21u-dev/pull/258.diff
Webrev
Link to Webrev Comment