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++/105589] [12/13 Regression] [ICE] templated type alias over std::array with bound type in template function fails Date: Sun, 15 May 2022 16:29:39 +0000 [thread overview] Message-ID: <bug-105589-4-jZmEH6OJnK@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105589-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105589 --- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-12 branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:40f749b364b740f41ea6b211f81c21919a2e8bee commit r12-8380-g40f749b364b740f41ea6b211f81c21919a2e8bee Author: Jason Merrill <jason@redhat.com> Date: Fri May 13 16:07:10 2022 -0400 c++: array {}-init [PR105589] My patch for 105191 made us use build_value_init more frequently from build_vec_init_expr, but build_value_init doesn't like to be called to initialize a class in a template. That's caused trouble in the past, and seems like a strange restriction, so let's fix it. PR c++/105589 PR c++/105191 PR c++/92385 gcc/cp/ChangeLog: * init.cc (build_value_init): Handle class in template. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/initlist-array16.C: New test.
next prev parent reply other threads:[~2022-05-15 16:29 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-13 1:25 [Bug c++/105589] New: " cuzdav at gmail dot com 2022-05-13 7:57 ` [Bug c++/105589] [12/13 Regression] " rguenth at gcc dot gnu.org 2022-05-13 13:28 ` ppalka at gcc dot gnu.org 2022-05-13 19:56 ` jason at gcc dot gnu.org 2022-05-15 16:24 ` jason at gcc dot gnu.org 2022-05-15 16:25 ` jason at gcc dot gnu.org 2022-05-15 16:28 ` cvs-commit at gcc dot gnu.org 2022-05-15 16:29 ` cvs-commit at gcc dot gnu.org [this message] 2022-05-15 16:29 ` jason at gcc dot gnu.org 2022-10-04 18:25 ` pinskia 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-105589-4-jZmEH6OJnK@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).