summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStefanus Du Toit <stefanus.du.toit@intel.com>2013-06-20 14:02:44 +0000
committerStefanus Du Toit <stefanus.du.toit@intel.com>2013-06-20 14:02:44 +0000
commitafea27befa957f2de268dfe01a04e96ad8b7a079 (patch)
treee24eddc8a2c23c72cec0f50fc2256385b214a81d
parent440dfe9644108b72f1fc3d116b6924eb47440f15 (diff)
downloadllvm-afea27befa957f2de268dfe01a04e96ad8b7a079.tar.gz
llvm-afea27befa957f2de268dfe01a04e96ad8b7a079.tar.bz2
llvm-afea27befa957f2de268dfe01a04e96ad8b7a079.tar.xz
Fix typos "metatadata" -> "metadata" in the LangRef.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@184426 91177308-0d34-0410-b5e6-96231b3b80d8
-rw-r--r--docs/LangRef.rst12
1 files changed, 6 insertions, 6 deletions
diff --git a/docs/LangRef.rst b/docs/LangRef.rst
index 2c55d333a6..a0073ddc55 100644
--- a/docs/LangRef.rst
+++ b/docs/LangRef.rst
@@ -4641,16 +4641,16 @@ alignment results in undefined behavior. Underestimating the alignment
may produce less efficient code. An alignment of 1 is always safe.
The optional ``!nontemporal`` metadata must reference a single
-metatadata name ``<index>`` corresponding to a metadata node with one
+metadata name ``<index>`` corresponding to a metadata node with one
``i32`` entry of value 1. The existence of the ``!nontemporal``
-metatadata on the instruction tells the optimizer and code generator
+metadata on the instruction tells the optimizer and code generator
that this load is not expected to be reused in the cache. The code
generator may select special instructions to save cache bandwidth, such
as the ``MOVNT`` instruction on x86.
The optional ``!invariant.load`` metadata must reference a single
-metatadata name ``<index>`` corresponding to a metadata node with no
-entries. The existence of the ``!invariant.load`` metatadata on the
+metadata name ``<index>`` corresponding to a metadata node with no
+entries. The existence of the ``!invariant.load`` metadata on the
instruction tells the optimizer and code generator that this load
address points to memory which does not change value during program
execution. The optimizer may then move this load around, for example, by
@@ -4726,9 +4726,9 @@ alignment results in undefined behavior. Underestimating the
alignment may produce less efficient code. An alignment of 1 is always
safe.
-The optional ``!nontemporal`` metadata must reference a single metatadata
+The optional ``!nontemporal`` metadata must reference a single metadata
name ``<index>`` corresponding to a metadata node with one ``i32`` entry of
-value 1. The existence of the ``!nontemporal`` metatadata on the instruction
+value 1. The existence of the ``!nontemporal`` metadata on the instruction
tells the optimizer and code generator that this load is not expected to
be reused in the cache. The code generator may select special
instructions to save cache bandwidth, such as the MOVNT instruction on