public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka 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: Mon, 12 Feb 2024 15:00:26 +0000	[thread overview]
Message-ID: <bug-113835-4-OHi2UxhIrn@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

--- Comment #4 from Patrick Palka <ppalka at gcc dot gnu.org> ---
r13-6421 just makes us use mce_true and mce_uknown during trial constant
evaluation of x's initialization, so my guess is before that commit the
evaluation was quickly aborted as soon as it saw a std::is_constant_evaluated()
call, and afterwards we evaluate is_constant_evaluated() to true and keep going
until we hit constexpr_loop_limit / constexpr_ops_limit.  So perhaps we should
have reduced limits for trial constant evaluation?

  parent reply	other threads:[~2024-02-12 15:00 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 ` [Bug libstdc++/113835] [13/14 Regression] " rguenth at gcc dot gnu.org
2024-02-09 13:42 ` 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 [this message]
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-OHi2UxhIrn@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: link
Be 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).