-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8314061: [JVMCI] DeoptimizeALot stress logic breaks deferred barriers #15218
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 never! A progress list of the required criteria for merging this PR into |
|
@tkrodriguez The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
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 to me.
|
@tkrodriguez 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 10 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! /integrate |
|
Going to push as commit 1875b28.
Your commit was automatically rebased without conflicts. |
|
@tkrodriguez Pushed as commit 1875b28. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
JVMCIRuntime::new_array_common includes a little bit of stress logic that changes how it returns when DeoptimizeALot is set. This can cause it to bypass the call to SharedRuntime::on_slowpath_allocation_exit(current) which is where the deferred card mark logic lives. This can lead to random crashes of various kinds.
Progress
Issue
Reviewers
Reviewing
Using
gitCheckout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15218/head:pull/15218$ git checkout pull/15218Update a local copy of the PR:
$ git checkout pull/15218$ git pull https://git.openjdk.org/jdk.git pull/15218/headUsing Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15218View PR using the GUI difftool:
$ git pr show -t 15218Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15218.diff
Webrev
Link to Webrev Comment