diff options
| author | Anna Zaks <ganna@apple.com> | 2013-03-28 23:15:22 +0000 |
|---|---|---|
| committer | Anna Zaks <ganna@apple.com> | 2013-03-28 23:15:22 +0000 |
| commit | 05fb371efc0edf15ef4aa8acea373fcc1211ad68 (patch) | |
| tree | 0220acc1df41102a6a55caf285bfb964cf408be2 /clang/lib/StaticAnalyzer/Core/CheckerManager.cpp | |
| parent | 96b42608abbed1a32ad03d905a9377c09a0efb57 (diff) | |
| download | bcm5719-llvm-05fb371efc0edf15ef4aa8acea373fcc1211ad68.tar.gz bcm5719-llvm-05fb371efc0edf15ef4aa8acea373fcc1211ad68.zip | |
[analyzer] Apply the suppression rules to the nil receiver only if the value participates in the computation of the nil we warn about.
We should only suppress a bug report if the IDCed or null returned nil value is directly related to the value we are warning about. This was
not the case for nil receivers - we would suppress a bug report that had an IDCed nil receiver on the path regardless of how it’s
related to the warning.
1) Thread EnableNullFPSuppression parameter through the visitors to differentiate between tracking the value which
is directly responsible for the bug and other values that visitors are tracking (ex: general tracking of nil receivers).
2) in trackNullOrUndef specifically address the case when a value of the message send is nil due to the receiver being nil.
llvm-svn: 178309
Diffstat (limited to 'clang/lib/StaticAnalyzer/Core/CheckerManager.cpp')
0 files changed, 0 insertions, 0 deletions
