public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94510] [9/10 Regression] nullptr_t implicitly cast to zero twice in std::array
Date: Tue, 07 Apr 2020 18:51:43 +0000	[thread overview]
Message-ID: <bug-94510-4-rrJfjDziFG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-94510-4@http.gcc.gnu.org/bugzilla/>

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

Martin Sebor <msebor at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |patch

--- Comment #10 from Martin Sebor <msebor at gcc dot gnu.org> ---
POINTER_TYPE_P() is zero because while nullptr is specified to be "the pointer
literal is the keyword nullptr" it also "...is a prvalue of type
std::nullptr_t. [Note: std::nullptr_t is a distinct type that is neither a
pointer type nor a pointer-to-member type; ..."  Of course -- a pointer literal
that doesn't have a pointer type, makes perfect sense.

Another closely related regression r270155 introduced is the missing warning
for the following test case:

$ cat t.C && gcc-8 -S -Wall t.C
#include <stddef.h>

int a[2] = { NULL };

t.C:3:19: warning: converting to non-pointer type ‘int’ from NULL
[-Wconversion-null]
 int a[2] = { NULL };
                   ^

The patch at the link below restores both diagnostics:
  https://gcc.gnu.org/pipermail/gcc-patches/2020-April/543482.html

  parent reply	other threads:[~2020-04-07 18:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-07  8:23 [Bug c++/94510] New: " kndevl at outlook dot com
2020-04-07  8:24 ` [Bug c++/94510] " kndevl at outlook dot com
2020-04-07  8:24 ` kndevl at outlook dot com
2020-04-07  8:25 ` kndevl at outlook dot com
2020-04-07  8:25 ` kndevl at outlook dot com
2020-04-07  8:26 ` kndevl at outlook dot com
2020-04-07  8:30 ` kndevl at outlook dot com
2020-04-07  8:30 ` kndevl at outlook dot com
2020-04-07 11:59 ` [Bug c++/94510] [9/10 Regression] " redi at gcc dot gnu.org
2020-04-07 16:08 ` msebor at gcc dot gnu.org
2020-04-07 18:51 ` msebor at gcc dot gnu.org [this message]
2020-04-22  6:28 ` cvs-commit at gcc dot gnu.org
2020-04-22  6:29 ` [Bug c++/94510] [9 " jason at gcc dot gnu.org
2020-04-22 20:39 ` cvs-commit at gcc dot gnu.org
2020-04-22 21:56 ` jason at gcc dot gnu.org

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