| commit | 0c8e16241cd879865d7e855d224eb66d8bd304c5 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Thu, 31 Jan 2013 20:16:01 +0000 (31 23:16 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Thu, 31 Jan 2013 20:16:01 +0000 (31 23:16 +0300) | ||
| tree | ee7be9bc6c18c43b18628bd99b8656b200ede366 | treesnapshot (tar.gz zip) |
| parent | 1fc8b1e237fb151313a447faa8f26984134da3cc | commitdiff |
absolute: delete smatch_absolute.c
The hard max/min stuff replaced smatch_absolute.c.
Say we have the following code:
unsigned char x = z;
We know that since x is a char it can't be more than 255. That's useful
information, but we shouldn't complain if x is used as an offset into
a 4 element array.
The idea was to store the 255 upper limit in smatch_absolute.c and any
lower limits we could find in smatch_extra.c.
But now we store everything in smatch_extra.c and we set the ->hard_max
flag if we think we're sure about it.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
The hard max/min stuff replaced smatch_absolute.c.
Say we have the following code:
unsigned char x = z;
We know that since x is a char it can't be more than 255. That's useful
information, but we shouldn't complain if x is used as an offset into
a 4 element array.
The idea was to store the 255 upper limit in smatch_absolute.c and any
lower limits we could find in smatch_extra.c.
But now we store everything in smatch_extra.c and we set the ->hard_max
flag if we think we're sure about it.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>