-
Notifications
You must be signed in to change notification settings - Fork 6.2k
8374151: Cleanup minor markWord function disorder #28928
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 stefank! A progress list of the required criteria for merging this PR into |
|
@stefank 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 1 new commit pushed to the
Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
Webrevs
|
dholmes-ora
left a comment
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.
Seems trivially fine.
I'm assuming this will allow some incoming valhalla changes to slide in more easily.
Maybe only marginally. The removal in #28927 clarifies an assumption in the Valhalla code that I was reviewing. And while discussing other cleanups to the markWord code in Valhalla, I noticed that markWord file could probably benefit from a clearer grouping of the existing function. So, this change isn't strictly necessary, but I do think it aids the readability of the file. |
|
Thanks for reviewing! |
|
The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork: git checkout 8374151_markword_discorder
git fetch https://git.openjdk.org/jdk.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push |
|
/integrate |
|
@stefank This pull request has not yet been marked as ready for integration. |
robcasloz
left a comment
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 good, and trivial.
|
Thanks for re-reviewing! |
I propose a minor restructuring to have the hash, monitor, and displaced_marker_helper functions grouped instead of intermixed.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/28928/head:pull/28928$ git checkout pull/28928Update a local copy of the PR:
$ git checkout pull/28928$ git pull https://git.openjdk.org/jdk.git pull/28928/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 28928View PR using the GUI difftool:
$ git pr show -t 28928Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/28928.diff
Using Webrev
Link to Webrev Comment