Re: [PATCH] Call infer_non_null() directly when checking for non-null.

Of course, one needs the patch... On 10/28/20 10:04 PM, Andrew MacLeod wrote: The ranger currently handles "inferred" non-nulls with a special cache.. inferred ranges are thing like a_2 = *b_1 the dereference of b_1 implies that any use of b_1 after that statement is non-null  (or a trap wou

[PATCH] Call infer_non_null() directly when checking for non-null.

The ranger currently handles "inferred" non-nulls with a special cache.. inferred ranges are thing like a_2 = *b_1 the dereference of b_1 implies that any use of b_1 after that statement is non-null  (or a trap would have happened).  The problem is that most ranges are calculated as a result