-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
8270098: ZGC: ZBarrierSetC2::clone_at_expansion fails with "Guard against surprises" assert #5048
Conversation
…inst surprises" assert
👋 Welcome back thartmann! A progress list of the required criteria for merging this PR into |
/label add hotspot-compiler |
@TobiHartmann |
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!
@TobiHartmann 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 2 new commits 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 |
Thanks for the review, Nils! |
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.
Good.
Thanks for the review, Vladimir! |
/integrate |
Going to push as commit 2384e12.
Your commit was automatically rebased without conflicts. |
@TobiHartmann Pushed as commit 2384e12. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
The fix for JDK-8268125 (PR 53) assumed that only dead code can have a clone array with an unknown array ptr type at expansion time. As
TestObjectArrayClone::testCloneObject
proves, that is not true because we can invokeObject::clone
on any object, including arrays.As a result, invoking
Object::clone
on an Object array leads to triggering the "Guard against surprises" assert in debug and to incorrectly using theT_LONG
copy stub (without GC barriers) in product. I was not able to trigger a crash in product but a corresponding runtime check (see patch) triggered reliably.The fix is to fall back to
ZBarrierSetRuntime::clone
if the array ptr type is unknown. I will backport this fix to JDK 17u.Thanks,
Tobias
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/5048/head:pull/5048
$ git checkout pull/5048
Update a local copy of the PR:
$ git checkout pull/5048
$ git pull https://git.openjdk.java.net/jdk pull/5048/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 5048
View PR using the GUI difftool:
$ git pr show -t 5048
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/5048.diff