forked from OSchip/llvm-project
0c33406aaa
In the analyzer's path-sensitive reports, when a report goes through a branch and the branch condition cannot be decided to be definitely true or false (based on the previous execution path), an event piece is added that tells the user that a new assumption is added upon the symbolic value of the branch condition. For example, "Assuming 'a' is equal to 3". The text of the assumption is hand-crafted in various manners depending on the AST expression. If the AST expression is too complex and the text of the assumption fails to be constructed, the event piece is omitted. This causes loss of information and misunderstanding of the report. Do not omit the event piece even if the expression is too complex; add a piece with a generic text instead. Differential Revision: https://reviews.llvm.org/D23300 llvm-svn: 283301 |
||
---|---|---|
.. | ||
DynDispatchBifurcate.m | ||
InlineObjCClassMethod.m | ||
InlineObjCInstanceMethod.h | ||
InlineObjCInstanceMethod.m | ||
ObjCDynTypePopagation.m | ||
ObjCImproperDynamictallyDetectableCast.m | ||
RetainCountExamples.m | ||
analysis-order.c | ||
assume-super-init-does-not-return-nil.m | ||
containers.cpp | ||
dyn-dispatch-bifurcate.cpp | ||
eager-reclamation-path-notes.c | ||
eager-reclamation-path-notes.cpp | ||
false-positive-suppression.c | ||
false-positive-suppression.cpp | ||
false-positive-suppression.m | ||
inline-defensive-checks.c | ||
inline-defensive-checks.cpp | ||
inline-defensive-checks.m | ||
path-notes.c | ||
path-notes.cpp | ||
path-notes.m | ||
retain-count-self-init.m | ||
stl.cpp | ||
test-always-inline-size-option.c | ||
test_objc_inlining_option.m |