| commit | 82f60f7702496f13e80dac4706e2608f52bc6344 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Fri, 15 Jul 2016 10:53:06 +0000 (15 13:53 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Sat, 16 Jul 2016 21:44:52 +0000 (17 00:44 +0300) | ||
| tree | 770cd9a621aac6fade96a252111ef3ae500a4cb5 | treesnapshot (tar.gz zip) |
| parent | 6b846942997a7761e18f5d8dddd7a84f0239cef6 | commitdiff |
extra: improve how "if (foo & ~0xF)" is handled
In the previous code we said that if you had "if (foo & 0xf0) {" then we
knew that foo was a minimum of 0x10. Now we're saying that if you have
"if (foo & ~0xff) " then we know that foo is a maximum of 0xff.
Looking at it now, I see that this could be tightened further still... :/
There is a lot of work to do.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
In the previous code we said that if you had "if (foo & 0xf0) {" then we
knew that foo was a minimum of 0x10. Now we're saying that if you have
"if (foo & ~0xff) " then we know that foo is a maximum of 0xff.
Looking at it now, I see that this could be tightened further still... :/
There is a lot of work to do.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_extra.c | diffblobblamehistory |