summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Robinson <paul_robinson@playstation.sony.com>2013-11-14 18:47:23 +0000
committerPaul Robinson <paul_robinson@playstation.sony.com>2013-11-14 18:47:23 +0000
commit687915ffff453a3cc2b56b6c961b752b4acfc2e5 (patch)
treedf132c9eef46848e9ee3ddf82bb208daa0d69a6a
parent410ba0c3d5777197e4f807b925056933007ec9e1 (diff)
downloadbcm5719-llvm-687915ffff453a3cc2b56b6c961b752b4acfc2e5.tar.gz
bcm5719-llvm-687915ffff453a3cc2b56b6c961b752b4acfc2e5.zip
Typos. (Test commit.)
llvm-svn: 194720
-rw-r--r--llvm/docs/Passes.rst2
-rw-r--r--llvm/docs/ProgrammersManual.rst4
2 files changed, 3 insertions, 3 deletions
diff --git a/llvm/docs/Passes.rst b/llvm/docs/Passes.rst
index d30c3ca4a00..029e472bcd3 100644
--- a/llvm/docs/Passes.rst
+++ b/llvm/docs/Passes.rst
@@ -476,7 +476,7 @@ transformation obviously invalidates the CFG, but can update forward dominator
-------------------------------------------------
This pass munges the code in the input function to better prepare it for
-SelectionDAG-based code generation. This works around limitations in it's
+SelectionDAG-based code generation. This works around limitations in its
basic-block-at-a-time approach. It should eventually be removed.
``-constmerge``: Merge Duplicate Global Constants
diff --git a/llvm/docs/ProgrammersManual.rst b/llvm/docs/ProgrammersManual.rst
index 2910a2aa1c1..99aa5c7877b 100644
--- a/llvm/docs/ProgrammersManual.rst
+++ b/llvm/docs/ProgrammersManual.rst
@@ -1172,7 +1172,7 @@ The drawback of SetVector is that it requires twice as much space as a normal
set and has the sum of constant factors from the set-like container and the
sequential container that it uses. Use it **only** if you need to iterate over
the elements in a deterministic order. SetVector is also expensive to delete
-elements out of (linear time), unless you use it's "pop_back" method, which is
+elements out of (linear time), unless you use its "pop_back" method, which is
faster.
``SetVector`` is an adapter class that defaults to using ``std::vector`` and a
@@ -2080,7 +2080,7 @@ the ``llvm_stop_multithreaded()`` call. You can also use the
Note that both of these calls must be made *in isolation*. That is to say that
no other LLVM API calls may be executing at any time during the execution of
-``llvm_start_multithreaded()`` or ``llvm_stop_multithreaded``. It's is the
+``llvm_start_multithreaded()`` or ``llvm_stop_multithreaded``. It is the
client's responsibility to enforce this isolation.
The return value of ``llvm_start_multithreaded()`` indicates the success or
OpenPOWER on IntegriCloud