Make more operations volatile and add compiler fences #6
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.
Related to issue #4.
Added some fences to prevent compiler reordering, and a rudimentary volatile version of
ptr::copy_nonoverlapping
. Unfortunately this thing is probably a bit less efficient than the standard library version which uses a nice LLVM intrinsic, but Rust doesn't expose the volatile flag of that intrinsic as a stable function currently.