Skip to content

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

Closed
wants to merge 1 commit into from

Conversation

JohnTortugo
Copy link
Contributor

@JohnTortugo JohnTortugo commented Apr 14, 2025

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

  • Change must be properly reviewed (1 review required, with at least 1 Reviewer)
  • Change must not contain extraneous whitespace
  • Commit message must refer to an issue

Issue

  • JDK-8354541: Remove Shenandoah post barrier expand loop opts (Bug - P4)

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

@bridgekeeper
Copy link

bridgekeeper bot commented Apr 14, 2025

👋 Welcome back cslucas! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

@openjdk
Copy link

openjdk bot commented Apr 14, 2025

@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:

8354541: Remove Shenandoah post barrier expand loop opts

Reviewed-by: shade

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 master branch:

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 in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

@openjdk openjdk bot added the rfr Pull request is ready for review label Apr 14, 2025
@openjdk
Copy link

openjdk bot commented Apr 14, 2025

@JohnTortugo The following labels will be automatically applied to this pull request:

  • hotspot
  • shenandoah

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.

@mlbridge
Copy link

mlbridge bot commented Apr 14, 2025

Webrevs

Copy link
Member

@shipilev shipilev left a 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?

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Apr 15, 2025
@JohnTortugo
Copy link
Contributor Author

/integrate

@openjdk openjdk bot added the sponsor Pull request is ready to be sponsored label Apr 16, 2025
@openjdk
Copy link

openjdk bot commented Apr 16, 2025

@JohnTortugo
Your change (at version bc1dbaf) is now ready to be sponsored by a Committer.

@earthling-amzn
Copy link
Contributor

/sponsor

@openjdk
Copy link

openjdk bot commented Apr 17, 2025

Going to push as commit 4eae9b5.
Since your change was applied there have been 123 commits pushed to the master branch:

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Apr 17, 2025
@openjdk openjdk bot closed this Apr 17, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review sponsor Pull request is ready to be sponsored labels Apr 17, 2025
@openjdk
Copy link

openjdk bot commented Apr 17, 2025

@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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants