| commit | 894cc5eac09953253addff00ff93a1acdd75ed65 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Tue, 21 Nov 2017 13:43:52 +0000 (21 16:43 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Wed, 22 Nov 2017 11:18:40 +0000 (22 14:18 +0300) | ||
| tree | 8d95e75e5b6a67b3d970a3863bffc9d7a1f0b57c | treesnapshot (tar.gz zip) |
| parent | 5e55933d8a7d742d19034b3f29d9e5c7957be2d4 | commitdiff |
implications: set_state() should trump implications
The problem here is that say it's implied that "a <= b" but the condition
is "a < b". The final true state should be "a < b" but it was instead set
to the implied state.
The exception is for smatch_extra states where the implied state and the
condition are always going to be the same, but the implied state has
implications associated with it which we want to preserve.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
The problem here is that say it's implied that "a <= b" but the condition
is "a < b". The final true state should be "a < b" but it was instead set
to the implied state.
The exception is for smatch_extra states where the implied state and the
condition are always going to be the same, but the implied state has
implications associated with it which we want to preserve.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| check_list.h | diffblobblamehistory | |
| smatch_implied.c | diffblobblamehistory |