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
8264788: Make SequentialSubTasksDone use-once #3372
8264788: Make SequentialSubTasksDone use-once #3372
Conversation
|
Webrevs
|
Note that it is possible to remove the CAS loop in
(And slightly fixing that assert in the destructor) |
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.
Looking at how SequentialSubTasksDone
is used, I don't really see the benefit of having assert(_num_claimed == _num_tasks)
in the destructor. If we drop that assertion, Atomic::add
is more readable.
I prefer Atomic::add
with the assertion removed, but this version is fine as well.
I changed to the |
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.
@tschatzl This change now passes all automated pre-integration checks. 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 105 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.
|
/integrate |
Thanks @albertnetymk @kstefanj for your reviews. |
@tschatzl Since your change was applied there have been 126 commits pushed to the
Your commit was automatically rebased without conflicts. Pushed as commit 125a847. |
Hi all,
can I have reviews for this change that simplifies code ahead?
SequentialSubTasksDone has some machinery to reset itself automatically after all tasks were claimed.
This is not used at all and can/should be removed.
Test: tier1-3
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jdk pull/3372/head:pull/3372
$ git checkout pull/3372
Update a local copy of the PR:
$ git checkout pull/3372
$ git pull https://git.openjdk.java.net/jdk pull/3372/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 3372
View PR using the GUI difftool:
$ git pr show -t 3372
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jdk/pull/3372.diff