| commit | 987f0b4bafcbb3f9d3c2dc94596af85a4fc8ee4e | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Fri, 17 Jun 2016 09:47:25 +0000 (17 12:47 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Fri, 17 Jun 2016 09:47:25 +0000 (17 12:47 +0300) | ||
| tree | 006f9cd2ad322b1ad033bfc10e37b4f50b1d6000 | treesnapshot (tar.gz zip) |
| parent | b9d0cc4b392c35e20980886ac79e5004c61af582 | commitdiff |
extra: ignore truncated limits
So the issue is, say you have a parameter with range "0-1,16". But the
function we're calling takes a bool. Then it will return PARAM_LIMIT set
to 1 or 0.
Before we would say that after that function was called the parameter was
0-1, which is wrong. We should do something smarter with this but for now
just ignore it.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
So the issue is, say you have a parameter with range "0-1,16". But the
function we're calling takes a bool. Then it will return PARAM_LIMIT set
to 1 or 0.
Before we would say that after that function was called the parameter was
0-1, which is wrong. We should do something smarter with this but for now
just ignore it.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_extra.c | diffblobblamehistory |