Add mutex lock for CPU RNG #4798
Closed
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
Contributor
|
Adding a mutex won't make the results deterministic. It will serialize access within a single run, but there's no reason why this order has to be repeated in another one. |
apaszke
suggested changes
Jan 23, 2018
| { | ||
| uint64_t y; | ||
|
|
||
| pthread_mutex_lock(&_generator->mutex); |
This comment was marked as off-topic.
This comment was marked as off-topic.
Sorry, something went wrong.
Contributor
|
It also breaks the windows build. Thanks for the PR, built I'll close this in favor of #4041. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Perhaps a simpler alternative for #4041
I'm concerned that the shared generator will introduce extra randomness so that results are not controllable by setting random seed.