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

package info (click to toggle)
swiftlang 6.0.3-2
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 2,519,992 kB
  • sloc: cpp: 9,107,863; ansic: 2,040,022; asm: 1,135,751; python: 296,500; objc: 82,456; f90: 60,502; lisp: 34,951; pascal: 19,946; sh: 18,133; perl: 7,482; ml: 4,937; javascript: 4,117; makefile: 3,840; awk: 3,535; xml: 914; fortran: 619; cs: 573; ruby: 573
file content (29 lines) | stat: -rw-r--r-- 1,068 bytes parent folder | download | duplicates (15) 
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);
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}}
    }
}