public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "haoxintu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/95354] GCC misuse "nonnull-attribute" option and can not detect it as UB as well
Date: Wed, 27 May 2020 11:43:12 +0000	[thread overview]
Message-ID: <bug-95354-4-21fPlbk3k3@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95354-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Haoxin Tu <haoxintu at gmail dot com> ---
(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-attribute” in GCC...
> 
> Yes, just use the attribute correctly.
> 
> Using:
> 
> __attribute__((nonnull)) void has_nonnull_argument(int *p) { 
>      ; 
> }
> 
> will cause UBsan to diagnose it:
> 
> nn.cc:7:25: runtime error: null pointer passed as argument 1, which is
> declared to never be null

Thanks, Jonathan, Got it ~

      parent reply	other threads:[~2020-05-27 11:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27  4:25 [Bug c++/95354] New: " haoxintu at gmail dot com
2020-05-27  4:50 ` [Bug c++/95354] " pinskia at gcc dot gnu.org
2020-05-27  9:16 ` redi at gcc dot gnu.org
2020-05-27  9:32 ` haoxintu at gmail dot com
2020-05-27 10:46 ` redi at gcc dot gnu.org
2020-05-27 11:43 ` haoxintu at gmail dot com [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-95354-4-21fPlbk3k3@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).