diff options
author | Zhongxing Xu <xuzhongxing@gmail.com> | 2009-04-01 03:23:38 +0000 |
---|---|---|
committer | Zhongxing Xu <xuzhongxing@gmail.com> | 2009-04-01 03:23:38 +0000 |
commit | 113cc14e9ccf9c63553cd0803096f3c938052870 (patch) | |
tree | 48f5e14aaf66a41aaf83556297cf9a20e179c713 /docs | |
parent | 8a8d8afa3df40e9f122d2b826f1a825a66f6908d (diff) | |
download | clang-113cc14e9ccf9c63553cd0803096f3c938052870.tar.gz |
Update docs.
git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@68183 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'docs')
-rw-r--r-- | docs/AnalyzerRegions.txt | 24 |
1 files changed, 24 insertions, 0 deletions
diff --git a/docs/AnalyzerRegions.txt b/docs/AnalyzerRegions.txt index d2177ec160..af36c3be84 100644 --- a/docs/AnalyzerRegions.txt +++ b/docs/AnalyzerRegions.txt @@ -70,6 +70,30 @@ MEMORY REGIONS and REGION TAXONOMY NOTE: We plan not to use loc::SymbolVal in RegionStore and remove it gradually. + Symbolic regions get their rvalue types through the following ways: + * through the parameter or global variable that points to it, e.g.: + + void f(struct s* p) { + ... + } + + The symbolic region pointed to by 'p' has type 'struct s'. + + * through explicit or implicit casts, e.g.: + void f(void* p) { + struct s* q = (struct s*) p; + ... + } + + We attach the type information to the symbolic region lazily. For the first + case above, we create the TypedViewRegion only when the pointer is actually + used to access the pointee memory object, that is when the element or field + region is created. For the cast case, the TypedViewRegion is created when + visiting the CastExpr. + + The reason for doing lazy typing is that symbolic regions are sometimes only + used to do location comparison. + Pointer Casts Pointer casts allow people to impose different 'views' onto a chunk of memory. |