* (slightly) inconsistent code in evaluate.c:type_difference
@ 2011-08-23 22:49 Jonathan Neuschäfer
0 siblings, 0 replies; only message in thread
From: Jonathan Neuschäfer @ 2011-08-23 22:49 UTC (permalink / raw)
To: linux-sparse
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 majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2011-08-23 22:49 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-08-23 22:49 (slightly) inconsistent code in evaluate.c:type_difference Jonathan Neuschäfer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).