Skip to content

Conversation

@shipilev
Copy link
Member

@shipilev shipilev commented Mar 26, 2025

Assembler GC barriers have quite a bit of coding to support 32-bit x86. As 32-bit x86 is removed, we can clean up those parts.

We can eliminate !LP64 blocks quite easily. We can also prune passing around thread argument, and just trust that r15_thread is always available.

Additional testing:

  • Linux x86_64 server fastdebug, tier1
  • Linux x86_64 server fastdebug, all

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-8351157: Clean up x86 GC barriers after 32-bit x86 removal (Sub-task - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 24253

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Mar 26, 2025

👋 Welcome back shade! 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 Mar 26, 2025

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

8351157: Clean up x86 GC barriers after 32-bit x86 removal

Reviewed-by: kbarrett, wkemper, tschatzl

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

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

@openjdk
Copy link

openjdk bot commented Mar 26, 2025

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

@openjdk openjdk bot added hotspot hotspot-dev@openjdk.org shenandoah shenandoah-dev@openjdk.org labels Mar 26, 2025
@shipilev shipilev marked this pull request as ready for review March 26, 2025 18:30
@openjdk openjdk bot added the rfr Pull request is ready for review label Mar 26, 2025
@mlbridge
Copy link

mlbridge bot commented Mar 26, 2025

Webrevs

Copy link

@kimbarrett kimbarrett left a comment

Choose a reason for hiding this comment

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

Looks good.

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Mar 26, 2025
@openjdk openjdk bot removed the ready Pull request is ready to be integrated label Mar 27, 2025
@shipilev
Copy link
Member Author

@tschatzl, @earthling-amzn -- want to look at G1 and Shenandoah parts, respectively?

@shipilev
Copy link
Member Author

shipilev commented Apr 9, 2025

Friendly reminder :)

Copy link

@kimbarrett kimbarrett left a comment

Choose a reason for hiding this comment

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

Still looks good.

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

@earthling-amzn earthling-amzn left a comment

Choose a reason for hiding this comment

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

This is a nice simplification.

@shipilev
Copy link
Member Author

@tschatzl -- are you fine with G1 cleanups?

@shipilev
Copy link
Member Author

Thanks! I merged with current mainline locally, and there are no surprises. So I am integrating.

/integrate

@openjdk
Copy link

openjdk bot commented Apr 10, 2025

Going to push as commit 73c8c75.
Since your change was applied there have been 27 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 10, 2025
@openjdk openjdk bot closed this Apr 10, 2025
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Apr 10, 2025
@openjdk
Copy link

openjdk bot commented Apr 10, 2025

@shipilev Pushed as commit 73c8c75.

💡 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 hotspot-dev@openjdk.org integrated Pull request has been integrated shenandoah shenandoah-dev@openjdk.org

Development

Successfully merging this pull request may close these issues.

4 participants