Dirty locals copied across threads require program-order constraints #6122
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.
We previously lacked SHARED_WRITE events in program order in a newly-spawned
thread for dirty locals being copied from the spawning thread. This resulted in
spurious failures as reading from initial values seemed possible, when the
from-read constraint should have prevented such reads.
Also, replace the variable "t" by the more descriptive "new_thread_nr."