public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "akim.demaille at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56373] New: -Wzero-as-null-pointer-constant: does not catch issues with smart pointers
Date: Mon, 18 Feb 2013 11:35:00 -0000	[thread overview]
Message-ID: <bug-56373-4@http.gcc.gnu.org/bugzilla/> (raw)


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56373

             Bug #: 56373
           Summary: -Wzero-as-null-pointer-constant: does not catch issues
                    with smart pointers
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: minor
          Priority: P3
         Component: c++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: akim.demaille@gmail.com


Hi all,

Sorry if this report is bogus.  I would expect GCC to complain about the
following uses of 0 instead of nullptr, but it does not.

$ cat foo.cc
#include <memory>
struct foo {};

int main ()
{
  std::shared_ptr<foo> a = 0;
  std::shared_ptr<foo> b(0);
  std::shared_ptr<foo> c{0};
  foo *d = 0;
}
$ g++-mp-4.8 -std=c++11 -Wall -Wzero-as-null-pointer-constant /tmp/foo.cc 
/tmp/foo.cc: In function 'int main()':
/tmp/foo.cc:9:12: warning: zero as null pointer constant
[-Wzero-as-null-pointer-constant]
   foo *d = 0;
            ^
/tmp/foo.cc:9:8: warning: unused variable 'd' [-Wunused-variable]
   foo *d = 0;
        ^
$ g++-mp-4.8  --version
g++-mp-4.8 (MacPorts gcc48 4.8-20130210_0) 4.8.0 20130210 (experimental)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

It's also a bit sad that only d is diagnosed as useless, although I do
understand that the shared_ptr has a constructor and a destructor that use
it.

Cheers!


             reply	other threads:[~2013-02-18 11:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-18 11:35 akim.demaille at gmail dot com [this message]
2013-02-18 12:08 ` [Bug c++/56373] " redi at gcc dot gnu.org
2013-02-18 12:53 ` akim.demaille at gmail dot com
2013-02-18 13:21 ` redi at gcc dot gnu.org
2013-02-18 13:23 ` akim.demaille at gmail dot com
2013-02-18 16:06 ` paolo.carlini at oracle dot com
2013-02-18 16:07 ` paolo.carlini at oracle dot com
2013-02-20  9:03 ` paolo at gcc dot gnu.org
2013-02-20  9:04 ` paolo.carlini at oracle dot com

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-56373-4@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).