aboutsummaryrefslogtreecommitdiff
path: root/lib/StaticAnalyzer/Checkers/CallAndMessageChecker.cpp
diff options
context:
space:
mode:
authorJordan Rose <jordan_rose@apple.com>2012-08-04 00:25:30 +0000
committerJordan Rose <jordan_rose@apple.com>2012-08-04 00:25:30 +0000
commit522f46f497d9ccecc8bc2f5ec132b9bb7060dee1 (patch)
tree42ef5544bc0d67d1eaf361bbb5c950af31c17953 /lib/StaticAnalyzer/Checkers/CallAndMessageChecker.cpp
parentaa6eccce0cd6e15229cdee52177477371890d3c4 (diff)
[analyzer] Don't assume values bound to references are automatically non-null.
While there is no such thing as a "null reference" in the C++ standard, many implementations of references (including Clang's) do not actually check that the location bound to them is non-null. Thus unlike a regular null dereference, this will not cause a problem at runtime until the reference is actually used. In order to catch these cases, we need to not prune out paths on which the input pointer is null. git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@161288 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'lib/StaticAnalyzer/Checkers/CallAndMessageChecker.cpp')
0 files changed, 0 insertions, 0 deletions