public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/110167] excessive compile time when optimizing std::to_array
Date: Thu, 08 Jun 2023 10:22:49 +0000 [thread overview]
Message-ID: <bug-110167-4-qRqOdnaow5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110167-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110167
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #2)
> The "obvious" alternative impl using a lambda expression is even slower:
Actually for GCC 13 it's faster:
$ time ~/gcc/13/bin/g++ 110167.cc -c -O3
real 0m9.422s
user 0m9.232s
sys 0m0.170s
$ time ~/gcc/13/bin/g++ 110167.cc -c -O3 -DUSE_LAMBDA
real 0m6.403s
user 0m6.342s
sys 0m0.048s
So that's nice.
next prev parent reply other threads:[~2023-06-08 10:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-08 3:18 [Bug libstdc++/110167] New: " nightstrike at gmail dot com
2023-06-08 9:51 ` [Bug c++/110167] " redi at gcc dot gnu.org
2023-06-08 10:17 ` redi at gcc dot gnu.org
2023-06-08 10:21 ` redi at gcc dot gnu.org
2023-06-08 10:22 ` redi at gcc dot gnu.org [this message]
2023-06-08 11:05 ` redi at gcc dot gnu.org
2023-06-08 15:01 ` redi at gcc dot gnu.org
2023-06-08 15:09 ` redi at gcc dot gnu.org
2023-06-08 15:28 ` [Bug libstdc++/110167] " redi at gcc dot gnu.org
2023-06-08 15:30 ` [Bug libstdc++/110167] excessive compile time for std::to_array with huge arrays redi at gcc dot gnu.org
2023-06-08 15:44 ` redi at gcc dot gnu.org
2023-06-09 7:00 ` rguenth at gcc dot gnu.org
2023-06-09 12:08 ` cvs-commit at gcc dot gnu.org
2023-10-19 14:07 ` redi at gcc dot gnu.org
2024-03-12 14:17 ` cvs-commit at gcc dot gnu.org
2024-03-13 9:52 ` cvs-commit at gcc dot gnu.org
2024-03-13 10:00 ` redi 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-110167-4-qRqOdnaow5@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).