[llvm-commits] [llvm] r61189 - /llvm/trunk/docs/AliasAnalysis.html

[Nick Lewycky]

Author: nicholas
Date: Wed Dec 17 20:15:05 2008
New Revision: 61189

URL: http://llvm.org/viewvc/llvm-project?rev=61189&view=rev
Log:
Recommit this grammar fix that was backed out along with nocapture.

Modified:
    llvm/trunk/docs/AliasAnalysis.html

Modified: llvm/trunk/docs/AliasAnalysis.html
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/AliasAnalysis.html?rev=61189&r1=61188&r2=61189&view=diff

==============================================================================
--- llvm/trunk/docs/AliasAnalysis.html (original)
+++ llvm/trunk/docs/AliasAnalysis.html Wed Dec 17 20:15:05 2008
@@ -192,11 +192,11 @@
 
 <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