extra: fix how hard max values are propagated1.71
commit7fcfe2595638393c26ffbe0abe13dae6a1c5b70f
authorDan Carpenter <dan.carpenter@oracle.com>
Mon, 25 Jan 2021 09:40:26 +0000 (25 12:40 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Mon, 25 Jan 2021 09:40:26 +0000 (25 12:40 +0300)
tree25465b41977b3002e3aa112e13ac80bc3acdaa07
parentebf8db91ac4a87b353f64fc88a0162875590e6ef
extra: fix how hard max values are propagated

If you have "if (foo > bar) {" then in the original code if "bar" was known
then "foo" was said to have a hard max.  But now if "bar" has a hard max
then "foo" now has a hard max.

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