| commit | 5a49d6669f3a41db0760c30791db9d9253140a8e | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Tue, 23 May 2017 08:24:36 +0000 (23 11:24 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Tue, 23 May 2017 08:24:36 +0000 (23 11:24 +0300) | ||
| tree | dc76328912c955eb0511d64746d0fbbc2b9492e5 | treesnapshot (tar.gz zip) |
| parent | 7b3f7e973c3978f57fc4457b7eb255bec5b32c3b | commitdiff |
extra: don't overwrite the implications for useless pointer limits
There was a function which said we limited a pointer to either zero or
valid. We started out with an unknown value but with implications for
NULL and non-NULL. So to limit it to NULL and valid is basically
useless.
Probably we shouldn't even store that useless information in the DB.
But anyway, I've filtered it out here.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
There was a function which said we limited a pointer to either zero or
valid. We started out with an unknown value but with implications for
NULL and non-NULL. So to limit it to NULL and valid is basically
useless.
Probably we shouldn't even store that useless information in the DB.
But anyway, I've filtered it out here.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_extra.c | diffblobblamehistory |