8260048: Shenandoah: ShenandoahMarkingContext asserts are unnecessary#2164
8260048: Shenandoah: ShenandoahMarkingContext asserts are unnecessary#2164shipilev wants to merge 2 commits intoopenjdk:masterfrom
Conversation
|
👋 Welcome back shade! A progress list of the required criteria for merging this PR into |
zhengyu123
left a comment
There was a problem hiding this comment.
Looks good and trivial.
|
@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: 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 18 new commits pushed to the
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 |
|
/integrate |
|
@shipilev Since your change was applied there have been 29 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 5940287. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
There are two
shenandoah_assert_not_forwardedasserts that are not necessary inmark_{strong,weak}, because the only caller already asserts this higher-level invariant. There is no need to check it inShenandoahMarkingContextonce again. This simplifies the fastpath in fastdebug builds.Additional testing:
hotspot_gc_shenandoahtier1,tier2with ShenandoahProgress
Issue
Reviewers
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2164/head:pull/2164$ git checkout pull/2164