| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
In C, comparisons between signed and unsigned numbers are always done in
unsigned-space. Thus, we should know that "i >= 0U" is always true, even
if 'i' is signed. Similarly, "u >= 0" is also always true, even though '0'
is signed.
Part of <rdar://problem/13239003> (false positives related to std::vector)
llvm-svn: 177806
|
| |
|
|
| |
llvm-svn: 156920
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This involves keeping track of three separate types: the symbol type, the
adjustment type, and the comparison type. For example, in "$x + 5 > 0ULL",
if the type of $x is 'signed char', the adjustment type is 'int' and the
comparison type is 'unsigned long long'. Most of the time these three types
will be the same, but we should still do the right thing when the
comparison value is out of range, and wraparound should be calculated in
the adjustment type.
This also re-disables an out-of-bounds test; we were extracting the symbol
from non-additive SymIntExprs, but then throwing away the integer.
Sorry for the large patch; both the basic and range constraint managers needed
to be updated together, since they share code in SimpleConstraintManager.
llvm-svn: 156361
|
| |
|
|
| |
llvm-svn: 156061
|
| |
|
|
|
|
| |
be the common root package.
llvm-svn: 136835
|
| |
|
|
|
|
| |
misnomer award.
llvm-svn: 126676
|
| |
|
|
| |
llvm-svn: 126607
|
| |
|
|
|
|
| |
The constant was copied from clang's limits.h.
llvm-svn: 106732
|
| |
|
|
|
|
| |
fails on linux.
llvm-svn: 106661
|
| |
|
|
| |
llvm-svn: 106639
|
|
|
const2
llvm-svn: 106339
|
