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 c++/110127] -fimplicit-constexpr leads to extremely slow and memory intensive compilation Date: Mon, 05 Jun 2023 16:43:55 +0000 [thread overview] Message-ID: <bug-110127-4-SQA692PAfa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110127-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110127 Patrick Palka <ppalka at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Last reconfirmed| |2023-06-05 See Also| |https://gcc.gnu.org/bugzill | |a/show_bug.cgi?id=109678 Known to fail| |12.1.0, 12.3.0, 13.1.0 Status|UNCONFIRMED |NEW Ever confirmed|0 |1 CC| |jason at gcc dot gnu.org, | |ppalka at gcc dot gnu.org Known to work| |14.0 --- Comment #1 from Patrick Palka <ppalka at gcc dot gnu.org> --- Thanks for the bug report, confirmed with GCC 12.1,12.3, 13.1 and the 13 release branch, so not a regression. On trunk the testcase compiles quickly ever since r14-409-g4b8d0d4d7fd245 for PR109678. It seems backporting that commit to the 13 branch would fix the slowness there too.
next prev parent reply other threads:[~2023-06-05 16:43 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-05 14:29 [Bug c++/110127] New: " fiesh at zefix dot tv 2023-06-05 16:43 ` ppalka at gcc dot gnu.org [this message] 2023-06-06 6:47 ` [Bug c++/110127] " fiesh at zefix dot tv 2023-08-14 18:21 ` ppalka 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-110127-4-SQA692PAfa@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).