-
Notifications
You must be signed in to change notification settings - Fork 384
add another weak mem consistency test #2370
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
Conversation
Ah, but unfortunately, the test still passes even if I replace the FAA by loads... bummer.^^ But still, seems like a good test to have. |
I think this is because of #2164. Try atomically reading x, y and z before spawning the threads (or hoist the allocation outside the loop and atomically write zero as initialisation) |
Ah, yes, with some initial stores added the bad execution happens quickly when I replace the FAA by a load. :) |
@bors r+ |
add another weak mem consistency test `@cbeuw` your code seems to do this correctly? :D
@bors retry r+ |
add another weak mem consistency test `@cbeuw` your code seems to do this correctly? :D
@bors retry r+ |
☀️ Test successful - checks-actions |
@cbeuw your code seems to do this correctly? :D