public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Wed, 22 Apr 2020 06:28:19 +0000 [thread overview] Message-ID: <bug-94510-4-ndChZ7A7BQ@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 --- Comment #11 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:587970215f4681def390e2a791aa3ba6adb65158 commit r10-7864-g587970215f4681def390e2a791aa3ba6adb65158 Author: Martin Sebor <msebor@gmail.com> Date: Wed Apr 22 02:27:54 2020 -0400 c++: reject scalar array initialization with nullptr [PR94510] The change committed to GCC 9 to allow string literals as template arguments caused the compiler to prune away, and thus miss diagnosing, conversion from nullptr to int in an array initializer. After looking at various approaches to improving the pruning, we realized that the only place the pruning is necessary is in the mangler. gcc/cp/ChangeLog 2020-04-22 Martin Sebor <msebor@redhat.com> Jason Merrill <jason@redhat.com> PR c++/94510 * decl.c (reshape_init_array_1): Avoid stripping redundant trailing zero initializers... * mangle.c (write_expression): ...and handle them here even for pointers to members by calling zero_init_expr_p. * cp-tree.h (zero_init_expr_p): Declare. * tree.c (zero_init_expr_p): Define. (type_initializer_zero_p): Remove. * pt.c (tparm_obj_values): New hash_map. (get_template_parm_object): Store to it. (tparm_object_argument): New. gcc/testsuite/ChangeLog 2020-04-22 Martin Sebor <msebor@redhat.com> PR c++/94510 * g++.dg/init/array58.C: New test. * g++.dg/init/array59.C: New test. * g++.dg/cpp2a/nontype-class34.C: New test. * g++.dg/cpp2a/nontype-class35.C: New test.
next prev parent reply other threads:[~2020-04-22 6:28 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 2020-04-22 6:28 ` cvs-commit at gcc dot gnu.org [this message] 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-ndChZ7A7BQ@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: linkBe 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).