On Wed, Apr 05, 2017 at 12:29:03PM +0100, Daniel P. Berrange wrote:
On Wed, Apr 05, 2017 at 12:38:23PM +0200, Martin Kletzander wrote:
[...]
> How about we enable it by default for build with new enough GCC
(so that
> it reports these errors without silently dropping the non-NULL checks)?
Yes, it seems that we can use -fno-delete-null-pointer-checks to prevent
GCC from optimizing away the NULL pointer checks, while having nonnull
attributes enabled all the time.
Or that, yes. So I'll drop this one.