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++/108645] Change in behavior, std::accumulate doesn't always work as expected in C++20 builds
Date: Fri, 03 Feb 2023 10:01:33 +0000	[thread overview]
Message-ID: <bug-108645-4-MZ1cZAghp6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108645-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> 	  const auto __size = __lhs.size() + __rhs.size();
> 	  if (__size > __lhs.capacity() && __size <= __rhs.capacity())
> 	    return std::move(__rhs.insert(0, __lhs));

It would be possible to change that logic to:

          const auto __size = __lhs.size() + __rhs.size();
          if (__size <= __rhs.capacity() && __rhs.capacity() >
__lhs.capacity())
            return std::move(__rhs.insert(0, __lhs));

That way if both strings have sufficient capacity, we would return the larger
of the two capacities. In general, the returned string is more likely to be the
one that gets reused, and this way it would be more likely to have additional
spare capacity.

In some usage patterns this would be a pessimization, because it would tend to
coalesce all the larger capacities into one string, leaving smaller, less
useful strings behind. Also, inserting into the beginning of the RHS takes more
work than simply appending to the end of the LHS. So I don't think it's clear
that this would be a definite improvement.

It wouldn't change anything in your example anyway, because there is no
dynamically allocated memory anywhere except the accumulator value, which is
always the LHS.

  parent reply	other threads:[~2023-02-03 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 21:00 [Bug libstdc++/108645] New: " eteran at alum dot rit.edu
2023-02-02 21:05 ` [Bug libstdc++/108645] " eteran at alum dot rit.edu
2023-02-03  1:40 ` pinskia at gcc dot gnu.org
2023-02-03  9:32 ` redi at gcc dot gnu.org
2023-02-03 10:01 ` redi at gcc dot gnu.org [this message]
2023-02-03 10:08 ` 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-108645-4-MZ1cZAghp6@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).