buf_size: store ranges in the database instead of single values
authorDan Carpenter <dan.carpenter@oracle.com>
Thu, 19 Dec 2013 15:56:32 +0000 (18:56 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Thu, 19 Dec 2013 15:56:32 +0000 (18:56 +0300)
commitd4ca3d01d43d86b1472b73bddb1a1e1def667b35
tree953886a1ff080bfdb94537804b31f8d055dfb069
parent97e32f76e68519f1fb9508db4b213229a1c5450e
buf_size: store ranges in the database instead of single values

Instead of saving a single value then save a range_list.

Part of the complication with doing this was that match_array_assignment()
and match_alloc() were over-writting each other.  I introduced a hash
table with the allocation functions so that if we assigned one of them then
it would only use match_alloc() and not match_array_assignment().  The
difference is that match_alloc() handle kcalloc() and friends correctly.

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