Ensure memory barriers when setting/getting atomic boolean #707
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
ghost
assigned
|
I've fixed the Regarding C atomic code: it could actually have no memory barriers assuming it does not call other Ruby methods. Since when it is in a C Ruby code, it cannot be switched to other Thread and GVL takes care of visibility on the later Thread switch. However nobody ever redid it in this way depending on these assumptions (facts). |
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.
After reviewing the atomic boolean code a bit, I noticed the atomic boolean was not using memory barriers when getting and setting values. This PR ensures that those memory barriers are used in all places.