(slightly) inconsistent code in evaluate.c:type_difference

Hello, Sparse devs,

in evaluate.c, at lines 623 and 624, t1 and t2 are expected not to be NULL, while a few lines later (630 and 638), they are checked to avoid a NULL pointer dereference. That's at least a bit confusing.

Thanks,
Jonathan Neuschäfer
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html