| commit | 4469500cba9be84b44cf1dc332b120ad133c5d2b | |
| author | Dan Carpenter <error27@gmail.com> | |
| Sun, 12 Apr 2009 04:49:33 +0000 (12 07:49 +0300) | ||
| committer | Dan Carpenter <error27@gmail.com> | |
| Sun, 12 Apr 2009 04:49:33 +0000 (12 07:49 +0300) | ||
| tree | 61d0da8515f1f5e91fea9df724c52c43f47b99ad | treesnapshot (tar.gz zip) |
| parent | 12ef3b0569dde0bd0fbedebc3285365206b522f4 | commitdiff |
Don't the implications for the state determining the implications.
When we set a state that implies that the current state is the implied
state for now. So when we come to a branch all the check scripts
get to set their states. Then anything that doesn't get set maybe has
implications that can be set.
The problem is for smatch_extra we can't set the state first or we
erase any implications. But we also don't want to set the implications,
we want to set it ourselves.
So we smatch_implied calls the smatch_extra condition hook after it sets
the implications. Also it doesn't set the states in smatch_implied.
Signed-off-by: Dan Carpenter <error27@gmail.com>
When we set a state that implies that the current state is the implied
state for now. So when we come to a branch all the check scripts
get to set their states. Then anything that doesn't get set maybe has
implications that can be set.
The problem is for smatch_extra we can't set the state first or we
erase any implications. But we also don't want to set the implications,
we want to set it ourselves.
So we smatch_implied calls the smatch_extra condition hook after it sets
the implications. Also it doesn't set the states in smatch_implied.
Signed-off-by: Dan Carpenter <error27@gmail.com>
| smatch_implied.c | diffblobblamehistory |