[3.14] gh-135871: Fix needless spinning in _PyMutex_LockTimed with zero timeout (gh-135872)
#135946
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ongh-135872) The free threading build could spin unnecessarily on `_Py_yield()` if the initial compare and swap failed. (cherry picked from commit cbfaf41) Co-authored-by: Joseph Tibbertsma <[email protected]>
vstinner
changed the title
_PyMutex_LockTimed with zero timeout (gh-135872)_PyMutex_LockTimed with zero timeout (gh-135872)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The free threading build could spin unnecessarily on
_Py_yield()if the initialcompare and swap failed.
(cherry picked from commit cbfaf41)
Co-authored-by: Joseph Tibbertsma [email protected]
_PyMutex_LockTimedspins and may fail unnecessarily in no-GIL builds #135871