db: hook up call_implies infrastructure
commita2085f1a50bc5f7bc288d72d99df123dc86337aa
authorDan Carpenter <dan.carpenter@oracle.com>
Tue, 24 Jul 2018 12:03:46 +0000 (24 15:03 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Tue, 24 Jul 2018 12:05:34 +0000 (24 15:05 +0300)
tree05ef5d41e6448a335f14dc08bf76aab39d350a2c
parentda2678fc7bc52a03334e98c99f0b26b4f1067278
db: hook up call_implies infrastructure

call_implies and return_implies are very similar and we can re-use some
of the code.  return_implies means that say "every path through the
function dereferenced a pointer".  call_implies means that at the start
of the function we know that param 2 is the size of the param 1 buffer.

But one trick is that not only is call_implies called at the start of the
function call, it's also hooked into the caller so the caller can use
the information that param 2 is the size of the buffer.

I generally think we will want to push all the call_implies iformation into
the cache_db before printing it.

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