-
Notifications
You must be signed in to change notification settings - Fork 10
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
Eagerly reset shared state in async_rw_mutex
#677
Conversation
bors try |
tryBuild failed: |
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.
LGTM thanks!
6c1e5cc
to
76f8e93
Compare
I've split out the spinlock change into a separate PR: #679. |
async_rw_mutex
async_rw_mutex
bors try |
tryBuild failed: |
bors try |
Note that I have bumped the stdexec commit used for the nvhpc configuration in CI to the one from #678. I have not changed anything else so #678 is still needed. However, nvc++ presumably miscompiling the test with the older commit (the |
tryBuild failed: |
This does actually need #678 to go in first because of some changes in stdexec. The |
169beb8
to
5bbc6f3
Compare
I've removed the stdexec changes from this PR and simply disabled the new test for now with nvhpc+stdexec. It needs to be reenabled again in #678. bors merge |
677: Eagerly reset shared state in `async_rw_mutex` r=msimberg a=msimberg Eagerly reset the shared state held by the operation state to allow continuations to run as early as possible. This fixes a deadlock that occurred in the added test case. Co-authored-by: Mikael Simberg <mikael.simberg@iki.fi>
Build failed: |
Eagerly reset the shared state held by the operation state to allow continuations to run as early as possible. This fixes a deadlock that occurred in the added test case.