| commit | 135e965c2f8432e38493bba8e7dbc2f8876482c3 | |
| author | Dan Carpenter <error27@gmail.com> | |
| Sun, 21 Mar 2010 12:29:13 +0000 (21 15:29 +0300) | ||
| committer | Dan Carpenter <error27@gmail.com> | |
| Sun, 21 Mar 2010 12:29:13 +0000 (21 15:29 +0300) | ||
| tree | ac466005d3030672db17981fff92efb642ad289b | treesnapshot (tar.gz zip) |
| parent | 299e88b41641d967b34b00b1b85a6406492a9887 | commitdiff |
extra: assume impossible things are impossible
I've waffled back and forth on how to handle this:
if (x < 0) {
if (x == 10)
__smatch_value("x");
}
What should smatch print there? One approach has been to say that maybe
smatch was wrong before and x can be 10. But my new approach which I've
been moving to is to say, "It's probably just a macro asking if x is 10.
let's assume that the check is bogus. x = (empty)"
Signed-off-by: Dan Carpenter <error27@gmail.com>
I've waffled back and forth on how to handle this:
if (x < 0) {
if (x == 10)
__smatch_value("x");
}
What should smatch print there? One approach has been to say that maybe
smatch was wrong before and x can be 10. But my new approach which I've
been moving to is to say, "It's probably just a macro asking if x is 10.
let's assume that the check is bogus. x = (empty)"
Signed-off-by: Dan Carpenter <error27@gmail.com>
| smatch_extra.c | diffblobblamehistory |