public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/105838] [10/11/12/13 Regression] g++ 12.1.0 runs out of memory or time when building const std::vector of std::strings Date: Mon, 05 Dec 2022 20:50:57 +0000 [thread overview] Message-ID: <bug-105838-4-kQj0aE68Wx@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 #12 from Jason Merrill <jason at gcc dot gnu.org> --- Another significant part of the problem is that vector<string> doesn't have a generic initializer_list constructor. Adding template <typename __elt> _GLIBCXX20_CONSTEXPR vector(initializer_list<__elt> __l, const allocator_type& __a = allocator_type()) : _Base(__a) { _M_range_initialize(__l.begin(), __l.end(), random_access_iterator_tag()); } so that it can construct from initializer_list<const char *> makes the construction into a simple loop over a static array. Users can do this optimization manually by writing e.g. auto init = { "aahing", "aaliis", "aarrgh", "abacas", "abacus", "abakas", "abamps", "abands", "abased", "abaser", "abases", "abasia", }; const std::vector<std::string> lst (init.begin(), init.end()); and so using the (template) iterator constructor instead of the (non-template) initializer_list constructor. But that shouldn't be necessary. Jonathan, has anyone suggested adding generic init_list constructors to the container classes? What do you think about doing the above translation in the compiler? Is the compiler allowed to do that?
next prev parent reply other threads:[~2022-12-05 20:50 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 [this message] 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 ` [Bug c++/105838] [10/11/12 " cvs-commit at gcc dot gnu.org 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-kQj0aE68Wx@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).