public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kndevl at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/94510] New: nullptr_t implicitly cast to zero twice in std::array
Date: Tue, 07 Apr 2020 08:23:27 +0000 [thread overview]
Message-ID: <bug-94510-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94510
Bug ID: 94510
Summary: nullptr_t implicitly cast to zero twice in std::array
Product: gcc
Version: 9.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: kndevl at outlook dot com
Target Milestone: ---
`std::array<int, 3> arr{ nullptr, 0, 0 };` is expected to fail to compile
similar to how `std::array<int, 3> arr{ nullptr, 0, 1 };` fails. What I infer
is that if all elements are effectively zero, type conversions are not checked.
This makes sense if a variable of static storage duration is initialized to
zero and std::array constructor can ignore the arguments in the initializer if
all arguments are implicitly zero.
Is there anything on the C++ standard that allows this optimization I am
missing here?
# This works fine, as expected
`g++ -save-temps -c not-bug.cpp`
> not-bug.cpp: In function ‘void test()’:
> not-bug.cpp:4:43: error: cannot convert ‘std::nullptr_t’ to ‘int’ in initialization
> 4 | std::array<int, 3> arr{ nullptr, 0, 1 };
# This compiles fine, but this should error out
`g++ -save-temps -c bug.cpp`
I built the tip of gcc yesterday. It had the same bug.
Any pointers on how I can go about debugging this?
- Does type checking happen during GENERIC stage?
- How do I print the source string corresponding to a TREE struct?
next reply other threads:[~2020-04-07 8:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 8:23 kndevl at outlook dot com [this message]
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
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@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).