db: don't split NULL and non-NULL unnecessarily
commitce9e3e2078021d10cc29183f0b38a500b4a5b167
authorDan Carpenter <dan.carpenter@oracle.com>
Fri, 22 Jun 2018 11:49:53 +0000 (22 14:49 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Fri, 22 Jun 2018 11:49:53 +0000 (22 14:49 +0300)
tree38ffe8846d6bb2a3c4a9b0bd218c3ab3202a31cb
parenta9f624c643592f39bfb5ce89a7e099c1a3e11fa2
db: don't split NULL and non-NULL unnecessarily

Say a function returns an unknown pointer, we were splitting it up between
NULL and non-NULL.  But that wasn't useful because we didn't know it could
be NULL and also the states were the same on both sides so it doesn't give
us any information.

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