math: sort of handle conditions
commit2292df76d4231806cede20f1b785a05a76b15df5
authorDan Carpenter <dan.carpenter@oracle.com>
Sat, 14 Apr 2012 23:15:25 +0000 (15 02:15 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Sat, 14 Apr 2012 23:15:25 +0000 (15 02:15 +0300)
treec4552706a45b2034d47ed31ccfcccf11058a6557
parent30c4316408bdf37260bdcf736655c315a8a88328
math: sort of handle conditions

It turns out that "foo = !x;" is handled in a special way in
smatch_condition.c and it doesn't call get_value().  It assumes that foo
can be either 0 or 1 at the end, and does some stuff with implications.

I'm not sure exactly what the correct thing to do is.  This change is a
partial improvement though because now __smatch_implied(1 < 2); produces
what you would expect it to.

Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
smatch_math.c