X-Git-Url: http://plrg.eecs.uci.edu/git/?p=oota-llvm.git;a=blobdiff_plain;f=docs%2FAliasAnalysis.html;h=97a813344d894dea99fa9489ee2a02136ee82f96;hp=1569fb8e688ca71df0ff5968d4761ea7b3dc0864;hb=e642658480ed0c9cde023a165edca237ba90bd31;hpb=30baa95afdf1199c2c5514310907b01ce5584cf5

diff --git a/docs/AliasAnalysis.html b/docs/AliasAnalysis.html
index 1569fb8e688..97a813344d8 100644
--- a/docs/AliasAnalysis.html
+++ b/docs/AliasAnalysis.html
@@ -192,11 +192,11 @@ and returns MustAlias, MayAlias, or NoAlias as appropriate.
 
 <div class="doc_text">
 <p>The NoAlias response is used when the two pointers refer to distinct objects,
-even regardless of whether the pointers compare equal.  For example, freed
-pointers don't alias any pointers that were allocated afterwards.  As a
-degenerate case, pointers returned by malloc(0) have no bytes for an object,
-and are considered NoAlias even when malloc returns the same pointer.  The same
-rule applies to NULL pointers.</p>
+regardless of whether the pointers compare equal.  For example, freed pointers
+don't alias any pointers that were allocated afterwards.  As a degenerate case,
+pointers returned by malloc(0) have no bytes for an object, and are considered
+NoAlias even when malloc returns the same pointer.  The same rule applies to
+NULL pointers.</p>
 
 <p>The MayAlias response is used whenever the two pointers might refer to the
 same object.  If the two memory objects overlap, but do not start at the same