[Bug c++/68767] [6 regression] spurious warning: null argument where non-null required

[jakub at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68767

--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jorn Wolfgang Rennecke from comment #11)
> (In reply to Jakub Jelinek from comment #10)
>  > Of course, the question is if the warning isn't really desirable, the user
> > should really just choose some non-NULL magic value to pass in the
> > impossible cases.
> 
> Are you saying the *_TYPE definitions in newlib-stdint.h should not use 0 in
> any branches of their expressions?

If you pass such *_TYPE definitions to functions with nonnull argument, maybe
yes.  Find out some other invalid type, like "".