From 4b03014d14ebb5588ca6d9ad73f74d92f4cdc54d Mon Sep 17 00:00:00 2001 From: Nuno Lopes Date: Sat, 15 Jul 2017 09:09:24 +0000 Subject: [PATCH] [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. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@308090 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/AliasAnalysis.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/AliasAnalysis.rst b/docs/AliasAnalysis.rst index e201333f300..0a5cb00a48d 100644 --- a/docs/AliasAnalysis.rst +++ b/docs/AliasAnalysis.rst @@ -132,7 +132,8 @@ The ``MayAlias`` response is used whenever the two pointers might refer to the 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``