-
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
8314157: G1: "yielded" is not initialized on some paths after JDK-8140326 #15359
8314157: G1: "yielded" is not initialized on some paths after JDK-8140326 #15359
Conversation
👋 Welcome back tschatzl! A progress list of the required criteria for merging this PR into |
Webrevs
|
… relying on external initialization
…unconditionally in G1ClearBitmapClosure already, so no issue here.
@tschatzl 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 22 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 |
Thanks @albertnetymk @walulyai for your reviews /integrate |
Going to push as commit 742e319.
Your commit was automatically rebased without conflicts. |
Hi all,
can I have reviews for this change that fixes a bug with with some variable not being initialized, leading to (minor) unnecessary work.
The use of the
yielded
variable is an optimization to not re-check TARSes again if there has been no yielding (safepoint) while processing. Maybe it is useful to remove it because the re-echeck for TARS isn't that expensive anyway.Testing: tier1-3
Thanks,
Thomas
Note: this has been edited to only cover the uninitialized variables after after @albertnetymk pointed out that the original error analysis has been wrong. There is some more information in the CR about the original analysis.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/15359/head:pull/15359
$ git checkout pull/15359
Update a local copy of the PR:
$ git checkout pull/15359
$ git pull https://git.openjdk.org/jdk.git pull/15359/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 15359
View PR using the GUI difftool:
$ git pr show -t 15359
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/15359.diff
Webrev
Link to Webrev Comment