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++/108773] [13 Regression] ICE in gimplify_var_or_parm_decl, at gimplify.cc:3058 compiling ceph since r13-4563-g1e1847612d7f169f Date: Thu, 09 Mar 2023 21:26:51 +0000 [thread overview] Message-ID: <bug-108773-4-tPtAJOzB2Z@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108773-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108773 --- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Jason Merrill <jason@gcc.gnu.org>: https://gcc.gnu.org/g:e0324e2629e25a90c13c68b4eef1e47b091970c3 commit r13-6566-ge0324e2629e25a90c13c68b4eef1e47b091970c3 Author: Jason Merrill <jason@redhat.com> Date: Mon Mar 6 22:57:57 2023 -0500 c++: allocator temps in list of arrays [PR108773] The optimization to reuse the same allocator temporary for all string constructor calls was breaking on this testcase, because the temps were already in the argument to build_vec_init, and replacing them with references to one slot got confused with calls at multiple levels (for the initializer_list backing array, and then again for the array member of the std::array). Fixed by reusing the whole TARGET_EXPR instead of pulling out the slot; gimplification ensures that it's only initialized once. I also moved the check for initializing a std:: class down into the tree walk, and handle multiple temps within a single array element initialization. PR c++/108773 gcc/cp/ChangeLog: * init.cc (find_allocator_temps_r): New. (combine_allocator_temps): Replace find_allocator_temp. (build_vec_init): Adjust. gcc/testsuite/ChangeLog: * g++.dg/cpp0x/initlist-array18.C: New test. * g++.dg/cpp0x/initlist-array19.C: New test.
next prev parent reply other threads:[~2023-03-09 21:26 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-13 12:54 [Bug c++/108773] New: internal compiler error: in gimplify_var_or_parm_decl, at gimplify.cc:3058 compiling ceph kkeithle at redhat dot com 2023-02-13 13:04 ` [Bug c++/108773] " kkeithle at redhat dot com 2023-02-13 13:05 ` marxin at gcc dot gnu.org 2023-02-13 13:16 ` [Bug c++/108773] [13 Regression] ICE in gimplify_var_or_parm_decl, at gimplify.cc:3058 compiling ceph since r13-4563-g1e1847612d7f169f marxin at gcc dot gnu.org 2023-02-13 13:18 ` marxin at gcc dot gnu.org 2023-02-13 13:27 ` jakub at gcc dot gnu.org 2023-02-13 14:27 ` jakub at gcc dot gnu.org 2023-02-13 14:39 ` jakub at gcc dot gnu.org 2023-02-13 15:54 ` jakub at gcc dot gnu.org 2023-02-13 16:03 ` marxin at gcc dot gnu.org 2023-02-13 16:11 ` jakub at gcc dot gnu.org 2023-02-13 17:06 ` jakub at gcc dot gnu.org 2023-02-13 17:07 ` jakub at gcc dot gnu.org 2023-02-27 10:33 ` rguenth at gcc dot gnu.org 2023-03-07 3:01 ` jason at gcc dot gnu.org 2023-03-08 3:35 ` jason at gcc dot gnu.org 2023-03-09 21:26 ` cvs-commit at gcc dot gnu.org [this message] 2023-03-09 21:30 ` jason at gcc dot gnu.org 2023-03-13 18:07 ` kkeithle at redhat dot com
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-108773-4-tPtAJOzB2Z@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).