| commit | cb10055b1d0f2e67f5320e1b3193def266ef90d1 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Wed, 15 Jun 2016 18:57:24 +0000 (15 21:57 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Wed, 15 Jun 2016 18:57:24 +0000 (15 21:57 +0300) | ||
| tree | 38f1ff66d7c7e10191cb081c80a1f5ea8fcad79a | treesnapshot (tar.gz zip) |
| parent | 684d22382af791033338d2b06d0d44dff45274ee | commitdiff |
db: split on boolean parameter
This is quite a hack, but you know I'm not above that. What my observation
is, is that we have a bunch of functions which do:
void whatever(int a, int b, int read_or_write) {
And depending on what read_or_write does, it behaves totally differently.
This code, does not change very much, because it tries to split on bool
as a last resort. So most of the time it only affects void functions.
Also it only finds one bool param, it prefers the right most params.
It makes the DB slightly larger.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
This is quite a hack, but you know I'm not above that. What my observation
is, is that we have a bunch of functions which do:
void whatever(int a, int b, int read_or_write) {
And depending on what read_or_write does, it behaves totally differently.
This code, does not change very much, because it tries to split on bool
as a last resort. So most of the time it only affects void functions.
Also it only finds one bool param, it prefers the right most params.
It makes the DB slightly larger.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_db.c | diffblobblamehistory |