| commit | 2b519ae3d66720e4f73dc777d3f93f6b91e0b523 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Thu, 19 Nov 2020 12:53:08 +0000 (19 15:53 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Thu, 19 Nov 2020 12:53:08 +0000 (19 15:53 +0300) | ||
| tree | 50968ac800d7a866057852237457aefafb1c9daa | treesnapshot (tar.gz zip) |
| parent | 26964408a15584cae5aecd3c79df9f787cdc6740 | commitdiff |
function_hooks/unwind: introduce return_implies_exact()
The problem is the difference between "can be" and "must be". In the
original code if the function returned unknown the we called the
implies_callback because it could be true. But with the
return_implies_exact() the call back is only called if it *must* be true.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
The problem is the difference between "can be" and "must be". In the
original code if the function returned unknown the we called the
implies_callback because it could be true. But with the
return_implies_exact() the call back is only called if it *must* be true.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| check_unwind.c | diffblobblamehistory | |
| smatch.h | diffblobblamehistory | |
| smatch_function_hooks.c | diffblobblamehistory |