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 libstdc++/110739] std::format for chrono types compiles very slowly
Date: Wed, 19 Jul 2023 12:55:58 +0000	[thread overview]
Message-ID: <bug-110739-4-dxRkwBD2l1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110739-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110739

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Created attachment 55580
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55580&action=edit
Instantiate less code for chrono formatters, take 2

In this patch the converters like _S_date and _S_hms are called by _M_format
before passing the argument to _M_x, _M_d_e etc. so that those function
templates are only called with arguments that are already the right type. This
reduces the number of different instantiations of those function templates.

But this doesn't really help either.

  parent reply	other threads:[~2023-07-19 12:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-19 11:33 [Bug libstdc++/110739] New: " redi at gcc dot gnu.org
2023-07-19 11:40 ` [Bug libstdc++/110739] " redi at gcc dot gnu.org
2023-07-19 12:55 ` redi at gcc dot gnu.org [this message]
2023-07-25 10:52 ` 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-110739-4-dxRkwBD2l1@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).