https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95354
--- Comment #5 from Haoxin Tu ---
(In reply to Jonathan Wakely from comment #4)
> (In reply to Haoxin Tu from comment #3)
> > I see. Are there any cases that can trigger the UB of nonnull-attribute? I
> > doubt the usage of “-fsanitize=nonnull-at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95354
--- Comment #4 from Jonathan Wakely ---
(In reply to Haoxin Tu from comment #3)
> I see. Are there any cases that can trigger the UB of nonnull-attribute? I
> doubt the usage of “-fsanitize=nonnull-attribute” in GCC...
Yes, just use the attribut
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95354
--- Comment #3 from Haoxin Tu ---
I see. Are there any cases that can trigger the UB of nonnull-attribute? I
doubt the usage of “-fsanitize=nonnull-attribute” in GCC...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95354
--- Comment #2 from Jonathan Wakely ---
Allowing the attribute on individual parameters might be nice though.
I hate the fact that for C++ member functions the first parameter is the
implicit 'this' pointer which always has to be non-null anyway
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95354
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
