public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/113835] [13/14 Regression] compiling std::vector with const size in C++20 is slow Date: Fri, 09 Feb 2024 06:58:31 +0000 [thread overview] Message-ID: <bug-113835-4-dHSAkyxTNf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-113835-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113835 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2024-02-09 Target Milestone|--- |13.3 Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Known to fail| |13.2.1, 14.0 Component|c++ |libstdc++ Known to work| |12.2.1 Summary|compiling std::vector with |[13/14 Regression] |const size in C++20 is slow |compiling std::vector with | |const size in C++20 is slow --- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> --- Confirmed with -std=c++20 -fsyntax-only constant expression evaluation : 1.80 ( 85%) 0.03 ( 14%) 1.84 ( 78%) 220M ( 88%) TOTAL : 2.13 0.22 2.36 250M Samples: 8K of event 'cycles', Event count (approx.): 9294971478 Overhead Samples Command Shared Object Symbol 16.33% 1385 cc1plus cc1plus [.] cxx_eval_constant_expression 4.35% 369 cc1plus cc1plus [.] cxx_eval_call_expression 3.90% 331 cc1plus cc1plus [.] cxx_eval_store_expression 3.16% 268 cc1plus cc1plus [.] hash_table<hash_map<tree_node*, tree_node*, simple_has 2.55% 216 cc1plus cc1plus [.] hash_table<hash_map<tree_node*, tree_node*, simple_has 2.15% 183 cc1plus cc1plus [.] ggc_internal_alloc 2.04% 173 cc1plus cc1plus [.] hash_table<int_cst_hasher, false, xcallocator>::find_s 1.98% 168 cc1plus cc1plus [.] tree_operand_check GCC 12 was fast (possibly std::vector wasn't constexpr there?)
next prev parent reply other threads:[~2024-02-09 6:58 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-02-08 17:11 [Bug c++/113835] New: " pobrn at protonmail dot com 2024-02-09 6:58 ` rguenth at gcc dot gnu.org [this message] 2024-02-09 13:42 ` [Bug libstdc++/113835] [13/14 Regression] " redi at gcc dot gnu.org 2024-02-12 10:45 ` jakub at gcc dot gnu.org 2024-02-12 15:00 ` ppalka at gcc dot gnu.org 2024-02-12 15:28 ` ppalka at gcc dot gnu.org 2024-02-12 15:38 ` jakub at gcc dot gnu.org 2024-03-07 20:40 ` law at gcc dot gnu.org 2024-05-21 9:19 ` [Bug libstdc++/113835] [13/14/15 " jakub 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-113835-4-dHSAkyxTNf@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).