Skip to content

Conversation

@benty-amzn
Copy link

@benty-amzn benty-amzn commented Dec 5, 2025

The STATIC_ASSERT below this typedef appears to be out of date.

The barriers check thread local copy of gc state, which is stored in ShenandoahThreadLocalData::_gc_state and is type char, so the size requirement described by the assert is maintained even after this change.

Change passes all tier1 tests locally when run with Shenandoah GC.


Progress

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

Issue

  • JDK-8352914: Shenandoah: Change definition of ShenandoahSharedValue to int32_t to leverage platform atomics (Enhancement - P4)

Reviewers

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28681/head:pull/28681
$ git checkout pull/28681

Update a local copy of the PR:
$ git checkout pull/28681
$ git pull https://git.openjdk.org/jdk.git pull/28681/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28681

View PR using the GUI difftool:
$ git pr show -t 28681

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28681.diff

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Dec 5, 2025

👋 Welcome back btaylor! 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 Dec 5, 2025

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

8352914: Shenandoah: Change definition of ShenandoahSharedValue to int32_t to leverage platform atomics

Reviewed-by: wkemper, ysr

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 29 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 (@earthling-amzn, @ysramakrishna) 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 hotspot-gc hotspot-gc-dev@openjdk.org shenandoah shenandoah-dev@openjdk.org labels Dec 5, 2025
@openjdk
Copy link

openjdk bot commented Dec 5, 2025

@benty-amzn The following labels will be automatically applied to this pull request:

  • hotspot-gc
  • 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.

@openjdk openjdk bot added the rfr Pull request is ready for review label Dec 5, 2025
@mlbridge
Copy link

mlbridge bot commented Dec 5, 2025

Webrevs

@earthling-amzn
Copy link
Contributor

/reviewers 2

This looks good to me, but would appreciate another reviewer.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Dec 5, 2025
@openjdk
Copy link

openjdk bot commented Dec 5, 2025

@earthling-amzn
The total number of required reviews for this PR (including the jcheck configuration and the last /reviewers command) is now set to 2 (with at least 1 Reviewer, 1 Author).

@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Dec 5, 2025
Copy link
Member

@ysramakrishna ysramakrishna left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any comparative performance numbers?

🚢

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Dec 5, 2025
@benty-amzn
Copy link
Author

I will check some performance numbers before and after this patch.

/integrate

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

openjdk bot commented Dec 8, 2025

@benty-amzn
Your change (at version 90923ab) is now ready to be sponsored by a Committer.

@ysramakrishna
Copy link
Member

/sponsor

@openjdk
Copy link

openjdk bot commented Dec 9, 2025

Going to push as commit b86b2cb.
Since your change was applied there have been 29 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 Dec 9, 2025
@openjdk openjdk bot closed this Dec 9, 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 Dec 9, 2025
@openjdk
Copy link

openjdk bot commented Dec 9, 2025

@ysramakrishna @benty-amzn Pushed as commit b86b2cb.

💡 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

Labels

hotspot-gc hotspot-gc-dev@openjdk.org integrated Pull request has been integrated shenandoah shenandoah-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

3 participants