https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16351
--- Comment #38 from David Binderman <dcb314 at hotmail dot com> --- (In reply to Manuel López-Ibáñez from comment #35) > I fear this case might be quite common and lead to many false positives that > are then quite hard to understand due to the poor location info in the > middle-end. I tried out the new warning flag by compiling the current Linux kernel and see something similar. No definately NULL pointers found, which is good news, but also about 60 messages about potentially NULL pointers. I checked a few of the 60 and couldn't see anything wrong. I didn't bother checking the rest. Suggest don't bother emitting warnings about potentially NULL pointers and keep the new code about definately NULL pointers. 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. Meanwhile, I'll be ignoring the warnings about potentially NULL.
