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++/105838] [10/11/12 Regression] g++ 12.1.0 runs out of memory or time when building const std::vector of std::strings Date: Mon, 12 Jun 2023 08:57:16 +0000 [thread overview] Message-ID: <bug-105838-4-b1r0jd2Gc0@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-105838-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105838 --- Comment #23 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:2764335bd336f2360d465ffcaa8f2c33f7321ab4 commit r14-1705-g2764335bd336f2360d465ffcaa8f2c33f7321ab4 Author: Jason Merrill <jason@redhat.com> Date: Tue Dec 6 18:10:48 2022 -0500 c++: build initializer_list<string> in a loop [PR105838] I previously applied this change in r13-4565 but reverted it due to PR108071. That PR was then fixed by r13-4712, but I didn't re-apply this change then because we weren't making the array static; since r14-1500 for PR110070 we now make the initializer array static, so let's bring this back. In situations where the maybe_init_list_as_range optimization isn't viable, we can build an initializer_list<string> with a loop over a constant array of string literals. This is represented using a VEC_INIT_EXPR, which required adjusting a couple of places that expected the initializer array to have the same type as the target array and fixing build_vec_init not to undo our efforts. PR c++/105838 gcc/cp/ChangeLog: * call.cc (convert_like_internal) [ck_list]: Use maybe_init_list_as_array. * constexpr.cc (cxx_eval_vec_init_1): Init might have a different type. * tree.cc (build_vec_init_elt): Likewise. * init.cc (build_vec_init): Handle from_array from a TARGET_EXPR. Retain TARGET_EXPR of a different type. gcc/testsuite/ChangeLog: * g++.dg/tree-ssa/initlist-opt5.C: New test.
next prev parent reply other threads:[~2023-06-12 8:57 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-06-03 16:22 [Bug c++/105838] New: " eisjmbjdfcukqlaely at nthrl dot com 2022-06-13 12:47 ` [Bug c++/105838] " rguenth at gcc dot gnu.org 2022-06-13 12:52 ` rguenth at gcc dot gnu.org 2022-06-14 11:56 ` rguenth at gcc dot gnu.org 2022-06-14 13:10 ` [Bug c++/105838] [10/11/12/13 Regression] " rguenth at gcc dot gnu.org 2022-06-14 13:11 ` rguenth at gcc dot gnu.org 2022-06-14 13:37 ` jakub at gcc dot gnu.org 2022-06-28 10:49 ` jakub at gcc dot gnu.org 2022-07-10 20:39 ` pinskia at gcc dot gnu.org 2022-07-11 15:43 ` luydorarko at vusra dot com 2022-12-05 17:57 ` jason at gcc dot gnu.org 2022-12-05 18:30 ` jakub at gcc dot gnu.org 2022-12-05 20:50 ` jason at gcc dot gnu.org 2022-12-05 20:58 ` jason at gcc dot gnu.org 2022-12-05 22:27 ` redi at gcc dot gnu.org 2022-12-05 22:34 ` jakub at gcc dot gnu.org 2022-12-05 23:57 ` jason at gcc dot gnu.org 2022-12-08 18:34 ` cvs-commit at gcc dot gnu.org 2022-12-08 18:41 ` cvs-commit at gcc dot gnu.org 2022-12-08 18:45 ` cvs-commit at gcc dot gnu.org 2022-12-15 5:26 ` cvs-commit at gcc dot gnu.org 2023-01-09 22:41 ` cvs-commit at gcc dot gnu.org 2023-06-02 15:01 ` [Bug c++/105838] [10/11/12/13/14 " cvs-commit at gcc dot gnu.org 2023-06-12 8:57 ` cvs-commit at gcc dot gnu.org [this message] 2023-07-07 10:43 ` [Bug c++/105838] [11/12 " rguenth at gcc dot gnu.org 2023-08-19 9:22 ` fxcoudert 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-105838-4-b1r0jd2Gc0@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).