| commit | 71f1e57d8bb5690b7fbda1aa14ff4baa2c719350 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Thu, 11 Oct 2012 12:22:00 +0000 (11 15:22 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Thu, 11 Oct 2012 12:22:00 +0000 (11 15:22 +0300) | ||
| tree | b1029a5c564a77e4a8e13ca44b375609d7005d6f | treesnapshot (tar.gz zip) |
| parent | df7c91199197e9a1b9a62cf5e1d516208512d248 | commitdiff |
math: improve how get_absolute_min/max() work
How it worked before is that get_absolute_max() was the same as
get_implied_max() except that if the value was unknown then it returned
the type_max() instead of whole_range.max.
This is still pretty much the case (for now), but the difference is that if
we do a bitwise AND or a RIGHTSHIFT those are handled differently.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
How it worked before is that get_absolute_max() was the same as
get_implied_max() except that if the value was unknown then it returned
the type_max() instead of whole_range.max.
This is still pretty much the case (for now), but the difference is that if
we do a bitwise AND or a RIGHTSHIFT those are handled differently.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_math.c | diffblobblamehistory |