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++/111286] [12/13/14 Regression] ICE on functional cast empty brace-init-list to const array reference Date: Mon, 05 Feb 2024 22:25:27 +0000 [thread overview] Message-ID: <bug-111286-4-RPhBCS3ioW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111286-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111286 --- Comment #6 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-13 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:c21c46032ebafb8fc36b7f02f2886a831e8c696a commit r13-8283-gc21c46032ebafb8fc36b7f02f2886a831e8c696a Author: Jason Merrill <jason@redhat.com> Date: Mon Feb 5 13:54:22 2024 -0500 c++: prvalue of array type [PR111286] Here we want to build a prvalue array to bind to the T reference, but we were wrongly trying to strip cv-quals from the array prvalue, which should be treated the same as a class prvalue. PR c++/111286 gcc/cp/ChangeLog: * tree.cc (rvalue): Don't drop cv-quals from an array. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/initlist-array22.C: New test. (cherry picked from commit c7e8381748f78335e9fef23f363b6a9e4463ce7e)
next prev parent reply other threads:[~2024-02-05 22:25 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-04 19:12 [Bug c++/111286] New: ICE on functional cast " leni536 at gmail dot com 2023-09-04 19:18 ` [Bug c++/111286] [12/13/14 Regression] ICE on functional cast empty brace-init-list " pinskia at gcc dot gnu.org 2023-09-05 14:19 ` mpolacek at gcc dot gnu.org 2023-09-13 7:01 ` gayathri.gottumukkala.27 at gmail dot com 2024-02-05 18:40 ` jason at gcc dot gnu.org 2024-02-05 21:33 ` cvs-commit at gcc dot gnu.org 2024-02-05 22:25 ` cvs-commit at gcc dot gnu.org 2024-02-05 22:25 ` cvs-commit at gcc dot gnu.org [this message] 2024-02-05 22:26 ` 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-111286-4-RPhBCS3ioW@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).