From 75ae2f14f164b44ad6da3e91eb93cd813f8061ce Mon Sep 17 00:00:00 2001 From: Zhongxing Xu Date: Thu, 2 Apr 2009 01:14:56 +0000 Subject: [PATCH] update docs. Replace 'lattice' with 'tree'. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@68271 91177308-0d34-0410-b5e6-96231b3b80d8 --- docs/AnalyzerRegions.txt | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/docs/AnalyzerRegions.txt b/docs/AnalyzerRegions.txt index 62f23e4618..c9c4ab30df 100644 --- a/docs/AnalyzerRegions.txt +++ b/docs/AnalyzerRegions.txt @@ -146,15 +146,16 @@ Pointer Casts For toll-free bridging casts, we return the original region. - We can set up a lattice for pointer types, with the most general type 'void*' - at the top. The lattice enforces a partial order among types. + We can set up a partial order for pointer types, with the most general type + 'void*' at the top. The partial order forms a tree with 'void*' as its root + node. - Every MemRegion has a root position in the type lattice. For example, the - pointee region of 'void *p' has its root position at the top of the lattice. + Every MemRegion has a root position in the type tree. For example, the pointee + region of 'void *p' has its root position at the root node of the tree. VarRegion of 'int x' has its root position at the 'int type' node. - TypedViewRegion is used to move the region down or up in the lattice. Moving - down in the lattice adds a TypedViewRegion. Moving up in the lattice removes a + TypedViewRegion is used to move the region down or up in the tree. Moving + down in the tree adds a TypedViewRegion. Moving up in the tree removes a TypedViewRegion. Do we want to allow moving up beyond the root position? This happens when: -- 2.40.0