public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janschultke at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/110945] std::basic_string::assign dramatically slower than other means of copying memory
Date: Tue, 08 Aug 2023 10:51:05 +0000	[thread overview]
Message-ID: <bug-110945-4-sp9OryeJhP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110945-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from Jan Schultke <janschultke at googlemail dot com> ---
Also it looks like GCC doesn't emit memcpy or memmove in either of the first
benchmarks. Those statements refer to the corresponding clang output, actually.
What's consistent for both compilers is that .assign() is dramatically slower
than any other method.

  parent reply	other threads:[~2023-08-08 10:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-08 10:42 [Bug libstdc++/110945] New: " janschultke at googlemail dot com
2023-08-08 10:43 ` [Bug libstdc++/110945] " janschultke at googlemail dot com
2023-08-08 10:51 ` janschultke at googlemail dot com [this message]
2023-08-08 10:55 ` janschultke at googlemail dot com
2023-08-08 11:02 ` redi at gcc dot gnu.org
2023-08-08 11:03 ` redi at gcc dot gnu.org
2023-08-08 11:16 ` redi at gcc dot gnu.org
2023-08-08 11:17 ` redi at gcc dot gnu.org
2023-08-08 11:19 ` janschultke at googlemail dot com
2023-08-08 11:23 ` redi at gcc dot gnu.org
2023-08-08 11:27 ` redi at gcc dot gnu.org
2023-08-08 11:36 ` redi at gcc dot gnu.org
2023-08-08 11:56 ` redi at gcc dot gnu.org
2023-08-08 12:02 ` redi at gcc dot gnu.org
2023-08-08 12:54 ` redi at gcc dot gnu.org
2023-08-08 16:04 ` redi at gcc dot gnu.org
2023-08-17 20:31 ` cvs-commit at gcc dot gnu.org
2023-08-17 20:40 ` 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-110945-4-sp9OryeJhP@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).