Skip to content
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

8327477: Parallel: Remove _data_location and _highest_ref in ParallelCompactData #18139

Closed
wants to merge 2 commits into from

Conversation

albertnetymk
Copy link
Member

@albertnetymk albertnetymk commented Mar 6, 2024

Trivial removing dead code.


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-8327477: Parallel: Remove _data_location and _highest_ref in ParallelCompactData (Enhancement - P4)

Reviewers

Reviewing

Using git

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

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

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 18139

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

Using diff file

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

Webrev

Link to Webrev Comment

@bridgekeeper
Copy link

bridgekeeper bot commented Mar 6, 2024

👋 Welcome back ayang! 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 openjdk bot changed the title 8327477 8327477: Parallel: Remove unused ParallelCompactData::_highest_ref Mar 6, 2024
@openjdk openjdk bot added the rfr Pull request is ready for review label Mar 6, 2024
@openjdk
Copy link

openjdk bot commented Mar 6, 2024

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

@openjdk openjdk bot added the hotspot-gc hotspot-gc-dev@openjdk.org label Mar 6, 2024
@mlbridge
Copy link

mlbridge bot commented Mar 6, 2024

Webrevs

Copy link
Member

@lgxbslgx lgxbslgx left a comment

Choose a reason for hiding this comment

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

Looks like a leftover of JDK-8323518. One nit.

Comment on lines 367 to 363
// These enable optimizations that are only partially implemented. Use
// debug builds to prevent the code fragments from breaking.
HeapWord* _data_location;
HeapWord* _highest_ref;
#endif // #ifdef ASSERT
Copy link
Member

Choose a reason for hiding this comment

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

Now, we only have one field here. So the word These in the comment should be revised to This? Or the comment needs more adjustment.

Copy link
Member Author

Choose a reason for hiding this comment

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

Actually, _data_location is used only for printing, and it records the corresponding heap-addr of a region, if I read the code correctly. How about removing _data_location as well, given its limited value?

Copy link
Member

Choose a reason for hiding this comment

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

it records the corresponding heap-addr of a region, if I read the code correctly.

I searched the code and think you are right. It is good to remove _data_location.

@openjdk
Copy link

openjdk bot commented Mar 7, 2024

@albertnetymk Please do not rebase or force-push to an active PR as it invalidates existing review comments. Note for future reference, the bots always squash all changes into a single commit automatically as part of the integration. See OpenJDK Developers’ Guide for more information.

@albertnetymk albertnetymk changed the title 8327477: Parallel: Remove unused ParallelCompactData::_highest_ref 8327477 Mar 7, 2024
@openjdk openjdk bot changed the title 8327477 8327477: Parallel: Remove _data_location and _highest_ref in ParallelCompactData Mar 7, 2024
Copy link
Member

@lgxbslgx lgxbslgx 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
Copy link

openjdk bot commented Mar 8, 2024

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

8327477: Parallel: Remove _data_location and _highest_ref in ParallelCompactData

Reviewed-by: gli, 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 8 new commits pushed to the master branch:

  • bdd1aeb: 8312383: Log X509ExtendedKeyManager implementation class name in TLS/SSL connection
  • fb4610e: 8327444: simplify RESTARTABLE macro usage in JDK codebase
  • de428da: 8327426: RISC-V: Move alignment shim into initialize_header() in C1_MacroAssembler::allocate_array
  • 8dbd4b3: 8326446: The User and System of jdk.CPULoad on Apple M1 are inaccurate
  • 7c5e6e7: 8327147: Improve performance of Math ceil, floor, and rint for x86
  • 972e81d: 8326611: Clean up vmTestbase/nsk/stress/stack tests
  • 5aae803: 8327390: JitTester: Implement temporary folder functionality
  • 784f11c: 8327238: Remove MetadataAllocationFailALot* develop flags

Please see this link for an up-to-date comparison between the source branch of this pull request and 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 ready Pull request is ready to be integrated label Mar 8, 2024
@albertnetymk
Copy link
Member Author

Thanks for review.

/integrate

@openjdk
Copy link

openjdk bot commented Mar 8, 2024

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

  • bdd1aeb: 8312383: Log X509ExtendedKeyManager implementation class name in TLS/SSL connection
  • fb4610e: 8327444: simplify RESTARTABLE macro usage in JDK codebase
  • de428da: 8327426: RISC-V: Move alignment shim into initialize_header() in C1_MacroAssembler::allocate_array
  • 8dbd4b3: 8326446: The User and System of jdk.CPULoad on Apple M1 are inaccurate
  • 7c5e6e7: 8327147: Improve performance of Math ceil, floor, and rint for x86
  • 972e81d: 8326611: Clean up vmTestbase/nsk/stress/stack tests
  • 5aae803: 8327390: JitTester: Implement temporary folder functionality
  • 784f11c: 8327238: Remove MetadataAllocationFailALot* develop flags

Your commit was automatically rebased without conflicts.

@openjdk openjdk bot added the integrated Pull request has been integrated label Mar 8, 2024
@openjdk openjdk bot closed this Mar 8, 2024
@openjdk openjdk bot removed ready Pull request is ready to be integrated rfr Pull request is ready for review labels Mar 8, 2024
@openjdk
Copy link

openjdk bot commented Mar 8, 2024

@albertnetymk Pushed as commit f9d479f.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.

@albertnetymk albertnetymk deleted the trivial branch March 8, 2024 09:39
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