Recommit this grammar fix that was backed out along with nocapture.

git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@61189 91177308-0d34-0410-b5e6-96231b3b80d8
This commit is contained in:
Nick Lewycky
2008-12-18 02:15:05 +00:00
parent 7224170f6a
commit 78eb804068

View File

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