Skip to content

Conversation

@walulyai
Copy link
Member

@walulyai walulyai commented Nov 11, 2025

Hi,

Please review this fix to a misalignment in G1HeapRegion::print_on. Additionally, increased the field width for hrm_index as this also causes misalignment on large heaps.


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-8371625: G1: G1HeapRegion::print_on misalignment (Enhancement - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 28229

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

Using diff file

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

Using Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Nov 11, 2025

👋 Welcome back iwalulya! 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 Nov 11, 2025

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

8371625: G1: G1HeapRegion::print_on misalignment

Reviewed-by: ayang, 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 64 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 openjdk bot added the hotspot-gc hotspot-gc-dev@openjdk.org label Nov 11, 2025
@openjdk
Copy link

openjdk bot commented Nov 11, 2025

@walulyai The following label will be automatically applied to this pull request:

  • hotspot-gc

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command.

@walulyai walulyai marked this pull request as ready for review November 11, 2025 09:51
@openjdk openjdk bot added the rfr Pull request is ready for review label Nov 11, 2025
@mlbridge
Copy link

mlbridge bot commented Nov 11, 2025

Webrevs

@openjdk openjdk bot added the ready Pull request is ready to be integrated label Nov 11, 2025
@walulyai
Copy link
Member Author

Thanks for the reviews!

/integrate

@openjdk
Copy link

openjdk bot commented Nov 12, 2025

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

openjdk bot commented Nov 12, 2025

@walulyai Pushed as commit 400a83d.

💡 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

Development

Successfully merging this pull request may close these issues.

3 participants