[llvm] r308090 - [docs] AliasAnalysis: clarify that PartialAlias doesn't enforce

Nuno Lopes via llvm-commits llvm-commits at lists.llvm.org
Sat Jul 15 02:09:24 PDT 2017


Author: nlopes
Date: Sat Jul 15 02:09:24 2017
New Revision: 308090

URL: http://llvm.org/viewvc/llvm-project?rev=308090&view=rev
Log:
[docs] AliasAnalysis: clarify that PartialAlias doesn't enforce
objects to start at the same address

As discussed on the ML, there's consensus that this is what the implementations
do and it seems sensible.

Modified:
    llvm/trunk/docs/AliasAnalysis.rst

Modified: llvm/trunk/docs/AliasAnalysis.rst
URL: http://llvm.org/viewvc/llvm-project/llvm/trunk/docs/AliasAnalysis.rst?rev=308090&r1=308089&r2=308090&view=diff
==============================================================================
--- llvm/trunk/docs/AliasAnalysis.rst (original)
+++ llvm/trunk/docs/AliasAnalysis.rst Sat Jul 15 02:09:24 2017
@@ -132,7 +132,8 @@ The ``MayAlias`` response is used whenev
 same object.
 
 The ``PartialAlias`` response is used when the two memory objects are known to
-be overlapping in some way, but do not start at the same address.
+be overlapping in some way, regardless whether they start at the same address
+or not.
 
 The ``MustAlias`` response may only be returned if the two memory objects are
 guaranteed to always start at exactly the same location. A ``MustAlias``




More information about the llvm-commits mailing list