diff options
| author | Nick Lewycky <nicholas@mxc.ca> | 2011-09-11 15:50:05 +0000 |
|---|---|---|
| committer | Nick Lewycky <nicholas@mxc.ca> | 2011-09-11 15:50:05 +0000 |
| commit | e4481d8ce5aa333b0dc43f307bc8fb47c694e3e2 (patch) | |
| tree | cc5165ba875a713a442c99ad980442447699eba4 /docs | |
| parent | 5366ca4e06fc00efb3ce7d0841c4c66789fbddeb (diff) | |
s/SequeuentiallyConsistent/SequentiallyConsistent/g
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@139481 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/Atomics.html | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/Atomics.html b/docs/Atomics.html index 9d9bdacd9b..fc15e27c39 100644 --- a/docs/Atomics.html +++ b/docs/Atomics.html @@ -437,10 +437,10 @@ void f(int* a) { SequentiallyConsistent operations may not be reordered.</dd> <dt>Notes for code generation</dt> <dd>SequentiallyConsistent loads minimally require the same barriers - as Acquire operations and SequeuentiallyConsistent stores require + as Acquire operations and SequentiallyConsistent stores require Release barriers. Additionally, the code generator must enforce - ordering between SequeuentiallyConsistent stores followed by - SequeuentiallyConsistent loads. This is usually done by emitting + ordering between SequentiallyConsistent stores followed by + SequentiallyConsistent loads. This is usually done by emitting either a full fence before the loads or a full fence after the stores; which is preferred varies by architecture.</dd> </dl> |