db: Use extra sm->possible to decide if splitting the returns makes sense
commit8be0469c1ad10d4b3fd632ecf5211e5f303e721b
authorDan Carpenter <dan.carpenter@oracle.com>
Tue, 24 Jul 2018 10:50:26 +0000 (24 13:50 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Tue, 24 Jul 2018 10:50:26 +0000 (24 13:50 +0300)
treea0209dcba090ffa6bc624444fe777a3980a2f0b6
parentb664c8a3191dbcd2dd7b9b49323dc371e1a2d14a
db: Use extra sm->possible to decide if splitting the returns makes sense

If there isn't a separate NULL or error pointer state then it doesn't
make sense to try to split the states apart.  There are two problems with
splitting it apart in that case.  You end up thinking that the function
can return NULL when really it just returns unknown.  And also you end
storing duplicate data in the DB.

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