summaryrefslogtreecommitdiffstats
path: root/llvm/docs/LangRef.html
diff options
context:
space:
mode:
authorChris Lattner <sabre@nondot.org>2009-09-11 01:49:31 +0000
committerChris Lattner <sabre@nondot.org>2009-09-11 01:49:31 +0000
commit92ada5dc52f48b33035b6971c3a32f6b6acabc0f (patch)
tree9f0dd14306af415d1e3336705611a83811839359 /llvm/docs/LangRef.html
parent0b209a863208b4a0002f48fc82e514a3012e0593 (diff)
downloadbcm5719-llvm-92ada5dc52f48b33035b6971c3a32f6b6acabc0f.tar.gz
bcm5719-llvm-92ada5dc52f48b33035b6971c3a32f6b6acabc0f.zip
more typos
llvm-svn: 81499
Diffstat (limited to 'llvm/docs/LangRef.html')
-rw-r--r--llvm/docs/LangRef.html11
1 files changed, 6 insertions, 5 deletions
diff --git a/llvm/docs/LangRef.html b/llvm/docs/LangRef.html
index b3e58138918..bdc9e170642 100644
--- a/llvm/docs/LangRef.html
+++ b/llvm/docs/LangRef.html
@@ -2021,7 +2021,7 @@ Classifications</a> </div>
Undefined values may be of any type (other than label or void) and be used
anywhere a constant is permitted.</p>
-<p>Undefined values are useful, because it indicates to the compiler that the
+<p>Undefined values are useful because they indicate to the compiler that the
program is well defined no matter what value is used. This gives the
compiler more freedom to optimize. Here are some examples of (potentially
surprising) transformations that are valid (in pseudo IR):</p>
@@ -2058,10 +2058,11 @@ Unsafe:
<p>These logical operations have bits that are not always affected by the input.
For example, if "%X" has a zero bit, then the output of the 'and' operation will
always be a zero, no matter what the corresponding bit from the undef is. As
-such, it is unsafe to optimizer or assume that the result of the and is undef.
-However, it is safe to assume that all bits of the undef are 0, and optimize the
-and to 0. Likewise, it is safe to assume that all the bits of the undef operand
-to the or could be set, allowing the or to be folded to -1.</p>
+such, it is unsafe to optimize or assume that the result of the and is undef.
+However, it is safe to assume that all bits of the undef could be 0, and
+optimize the and to 0. Likewise, it is safe to assume that all the bits of
+the undef operand to the or could be set, allowing the or to be folded to
+-1.</p>
<div class="doc_code">
<pre>
OpenPOWER on IntegriCloud