about summary refs log tree commit diff
diff options
context:
space:
mode:
authorRalf Jung <post@ralfj.de>2019-05-20 09:50:37 +0200
committerRalf Jung <post@ralfj.de>2019-05-20 09:50:37 +0200
commitb9be68ce2ed75a3801075f66f50200e329211400 (patch)
tree6b847391bb1d5d6b43cc5f030ce90b15ca38a1be
parentcaef1e833fbd9de740d521114d716a11a29b71cb (diff)
downloadrust-b9be68ce2ed75a3801075f66f50200e329211400.tar.gz
rust-b9be68ce2ed75a3801075f66f50200e329211400.zip
remove confusing remarks about mixed volatile and non-volatile accesses
-rw-r--r--src/libcore/ptr.rs6
1 files changed, 0 insertions, 6 deletions
diff --git a/src/libcore/ptr.rs b/src/libcore/ptr.rs
index ada784e9ce7..fc3525b1184 100644
--- a/src/libcore/ptr.rs
+++ b/src/libcore/ptr.rs
@@ -810,9 +810,6 @@ pub unsafe fn write_unaligned<T>(dst: *mut T, src: T) {
 /// to not be elided or reordered by the compiler across other volatile
 /// operations.
 ///
-/// Memory accessed with `read_volatile` or [`write_volatile`] should not be
-/// accessed with non-volatile operations.
-///
 /// [`write_volatile`]: ./fn.write_volatile.html
 ///
 /// # Notes
@@ -881,9 +878,6 @@ pub unsafe fn read_volatile<T>(src: *const T) -> T {
 /// to not be elided or reordered by the compiler across other volatile
 /// operations.
 ///
-/// Memory accessed with [`read_volatile`] or `write_volatile` should not be
-/// accessed with non-volatile operations.
-///
 /// `write_volatile` does not drop the contents of `dst`. This is safe, but it
 /// could leak allocations or resources, so care should be taken not to overwrite
 /// an object that should be dropped.