| commit | 16c4a7ea6037661b2154556c94ad4ae4948b7e72 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Wed, 18 Oct 2017 08:41:48 +0000 (18 11:41 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Wed, 18 Oct 2017 08:41:48 +0000 (18 11:41 +0300) | ||
| tree | 6d03b65e528e22be034d488c8941f853ce42130b | treesnapshot (tar.gz zip) |
| parent | bd6e0786d09d712068cae8b6fccf1105b88e28e6 | commitdiff |
buf_size: don't store obvious sizes in the DB
Say a function takes a struct foo pointer, it's waste of time to store that
we're passing a struct foo size object. That's assumed from the type.
Also the old behavior caused a lot of false positives when the struct
changed to a different size and it took a while for the size information to
propagate through the call tree.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Say a function takes a struct foo pointer, it's waste of time to store that
we're passing a struct foo size object. That's assumed from the type.
Also the old behavior caused a lot of false positives when the struct
changed to a different size and it took a while for the size information to
propagate through the call tree.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_buf_size.c | diffblobblamehistory |