The DIBuilder class is just a wrapper around debug info creation

[oota-llvm.git] / docs / Atomics.html
diff --git a/docs/Atomics.html b/docs/Atomics.html

index 9d9bdacd9bb25c6f0fc6a1606cbfd6aa6f3cb5b9..2358f4d2ef2268ccfa1ffb456d7b6be699c68cdf 100644 (file)
--- a/docs/Atomics.html
+++ b/docs/Atomics.html
@@ -4,7 +4,7 @@
  <head>
    <title>LLVM Atomic Instructions and Concurrency Guide</title>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
-  <link rel="stylesheet" href="llvm.css" type="text/css">
+  <link rel="stylesheet" href="_static/llvm.css" type="text/css">
  </head>
  <body>
  
@@ -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>