File: solver-sym-simplification-with-proper-range-type.c

package info (click to toggle)
llvm-toolchain-13 1%3A13.0.1-11
  • links: PTS, VCS
  • area: main
  • in suites: bookworm
  • size: 1,418,840 kB
  • sloc: cpp: 5,290,826; ansic: 996,570; asm: 544,593; python: 188,212; objc: 72,027; lisp: 30,291; f90: 25,395; sh: 24,898; javascript: 9,780; pascal: 9,398; perl: 7,484; ml: 5,432; awk: 3,523; makefile: 2,913; xml: 953; cs: 573; fortran: 539
file content (29 lines) | stat: -rw-r--r-- 1,064 bytes parent folder | download | duplicates (6) 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
 
// RUN: %clang_analyze_cc1 %s \
// RUN:   -analyzer-checker=core \
// RUN:   -analyzer-checker=debug.ExprInspection \
// RUN:   -verify

// Here we test that the range based solver equivalency tracking mechanism
// assigns a properly typed range to the simplified symbol.

void clang_analyzer_printState();
void clang_analyzer_eval(int);

void f(int a0, int b0, int c)
{
    int a1 = a0 - b0;
    int b1 = (unsigned)a1 + c;
    if (c == 0) {

        int d = 7L / b1; // ...
        // At this point b1 is considered non-zero, which results in a new
        // constraint for $a0 - $b0 + $c. The type of this sym is unsigned,
        // however, the simplified sym is $a0 - $b0 and its type is signed.
        // This is probably the result of the inherent improper handling of
        // casts. Anyway, Range assignment for constraints use this type
        // information. Therefore, we must make sure that first we simplify the
        // symbol and only then we assign the range.

        clang_analyzer_eval(a0 - b0 != 0); // expected-warning{{TRUE}}
    }
}