-
Notifications
You must be signed in to change notification settings - Fork 5.9k
8354541: Remove Shenandoah post barrier expand loop opts #24630
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 cslucas! A progress list of the required criteria for merging this PR into |
@JohnTortugo 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 92 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 |
@JohnTortugo The following labels 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 lists. If you would like to change these labels, use the /label pull request command. |
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 OK in principle. This would likely not matter in the future when we switch to late barrier expansion for Shenandoah, following the examples of Z and G1. Have you seen any performance impact at all with this patch?
/integrate |
@JohnTortugo |
/sponsor |
Going to push as commit 4eae9b5.
Your commit was automatically rebased without conflicts. |
@earthling-amzn @JohnTortugo Pushed as commit 4eae9b5. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Please review this patch to remove Shenandoah post-barrier expand loop optimizations. This optimization was added in the first iteration os Shenandoah barriers. Nowadays, we try to always insert LRB at the earliest place and the impact of these optimizations is minimal; they are also frequent source of bugs.
Tested on OSX Aarch64 & Linux amd64 with JTREG tier1-3.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/24630/head:pull/24630
$ git checkout pull/24630
Update a local copy of the PR:
$ git checkout pull/24630
$ git pull https://git.openjdk.org/jdk.git pull/24630/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 24630
View PR using the GUI difftool:
$ git pr show -t 24630
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/24630.diff
Using Webrev
Link to Webrev Comment