about summary refs log tree commit diff
diff options
context:
space:
mode:
authorJeehoon Kang <jeehoon.kang@sf.snu.ac.kr>2015-07-29 22:48:25 +0900
committerJeehoon Kang <jeehoon.kang@sf.snu.ac.kr>2015-07-29 22:48:25 +0900
commit2081aa623daed4b90c45e77e88349f73b54e32d8 (patch)
tree056dc832112bade39fc9b369580eda8d47fc18aa
parent78bf4b6ff68420a718e8b0ed6b3016d1cf395083 (diff)
downloadrust-2081aa623daed4b90c45e77e88349f73b54e32d8.tar.gz
rust-2081aa623daed4b90c45e77e88349f73b54e32d8.zip
Fix a documentation bug for memory orderings
As described in the module documentation, the memory orderings in Rust
are the same with that of LLVM.  However, the documentation for the
memory orderings enum says the memory orderings are the same of that of
C++.  Note that they differ in that C++'s support the consume reads,
while LLVM's does not.  Hence this commit fixes the bug in the
documentation for the enum.
-rw-r--r--src/libcore/atomic.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libcore/atomic.rs b/src/libcore/atomic.rs
index c6434e71957..3d133b6b7b0 100644
--- a/src/libcore/atomic.rs
+++ b/src/libcore/atomic.rs
@@ -145,7 +145,7 @@ unsafe impl<T> Sync for AtomicPtr<T> {}
 /// "relaxed" atomics allow all reorderings.
 ///
 /// Rust's memory orderings are [the same as
-/// C++'s](http://gcc.gnu.org/wiki/Atomic/GCCMM/AtomicSync).
+/// LLVM's](http://llvm.org/docs/LangRef.html#memory-model-for-concurrent-operations).
 #[stable(feature = "rust1", since = "1.0.0")]
 #[derive(Copy, Clone)]
 pub enum Ordering {