902f02db72
There are very few tests here because SValBuilder is fairly aggressive about not building SymExprs that we can't evaluate, which saves memory and CPU but also makes it very much tied to the current constraint manager. We should probably scale back here and let things decay to UnknownVal later on. bitwise-ops.c tests that for the SymExprs we do create, we persist our assumptions about them. traversal-path-unification.c tests that we do clean out constraints on arbitrary SymExprs once they have actually died. llvm-svn: 164623
14 lines
507 B
C
14 lines
507 B
C
// RUN: %clang_cc1 -analyze -analyzer-checker=core,debug.ExprInspection -verify %s
|
|
|
|
void clang_analyzer_eval(int);
|
|
#define CHECK(expr) if (!(expr)) return; clang_analyzer_eval(expr)
|
|
|
|
void testPersistentConstraints(int x, int y) {
|
|
// Sanity check
|
|
CHECK(x); // expected-warning{{TRUE}}
|
|
CHECK(x & 1); // expected-warning{{TRUE}}
|
|
|
|
// False positives due to SValBuilder giving up on certain kinds of exprs.
|
|
CHECK(1 - x); // expected-warning{{UNKNOWN}}
|
|
CHECK(x & y); // expected-warning{{UNKNOWN}}
|
|
} |