https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16351
--- Comment #39 from Manuel López-Ibáñez <manu at gcc dot gnu.org> --- (In reply to David Binderman from comment #38) > It could even be the case that the "potential NULL" code gets > put into some backwater flag away from -Wall, and, after a suitable period > of more testing, the "definately NULL" code gets to go into > prime time of -Wall. We could split the flag into -Wnull-dereference and -Wmaybe-null-dereference.
