From 349eb41af479b1e7412c2661d8e70c7a6415501a Mon Sep 17 00:00:00 2001 From: Chris Lattner Date: Tue, 8 Sep 2009 15:13:16 +0000 Subject: [PATCH] fix a couple typos pointed out by edwin and duncan git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@81219 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/LangRef.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/LangRef.html b/docs/LangRef.html index 596066d3270..b0bb562e7f3 100644 --- a/docs/LangRef.html +++ b/docs/LangRef.html @@ -2116,7 +2116,7 @@ arbitrarily change its value over its "live range". This is true because the "variable" doesn't actually have a live range. Instead, the value is logically read from arbitrary registers that happen to be around when needed, so the value is not neccesarily consistent over time. In fact, %A and %C need -to have the same semantics of the core LLVM "replace all uses with" concept +to have the same semantics or the core LLVM "replace all uses with" concept would not hold.

@@ -2136,7 +2136,7 @@ can be constant folded to undef because the undef could be an SNaN, and fdiv is not (currently) defined on SNaN's. However, in the second example, we can make a more aggressive assumption: because the undef is allowed to be an arbitrary value, we are allowed to assume that it could be zero. Since a divide by zero -is has undefined behavior, we are allowed to assume that the operation +it has undefined behavior, we are allowed to assume that the operation does not execute at all. This allows us to delete the divide and all code after it: since the undefined operation "can't happen", the optimizer can assume that it occurs in dead code.