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++/109305] Allocator copy in basic_string::operator=
Date: Mon, 27 Mar 2023 21:03:14 +0000 [thread overview]
Message-ID: <bug-109305-4-EyuEvWsftg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109305-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109305
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
Last reconfirmed| |2023-03-27
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Marc-André Laverdière from comment #0)
> Created attachment 54773 [details]
> Self-contained preprocessed reproducer
>
> In basic_string& operator=(const basic_string& __str), I noticed this line:
>
> auto __alloc = __str._M_get_allocator();
>
> This creates a local copy of the allocator object. I doubt this is
> intentional, but I could be wrong.
It's completely intentional. The function needs to allocate new storage, so it
needs a non-const allocator that compares equal to __str.get_allocator().
As the comment hints at, the order of the operations is important. We don't
want to update the allocator in *this until after we've allocated the storage,
because that could throw. So we make a copy of the allocator, use it to
allocate memory, then only if that was successful we replace the allocator in
*this.
Why do you think this local copy is a problem?
next prev parent reply other threads:[~2023-03-27 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 19:04 [Bug libstdc++/109305] New: " marc-andre.laverdiere at synopsys dot com
2023-03-27 19:09 ` [Bug libstdc++/109305] " pinskia at gcc dot gnu.org
2023-03-27 19:12 ` pinskia at gcc dot gnu.org
2023-03-27 21:03 ` redi at gcc dot gnu.org [this message]
2023-03-28 16:04 ` marc-andre.laverdiere at synopsys dot com
2023-03-28 16:19 ` redi at gcc dot gnu.org
2023-03-28 16:21 ` redi at gcc dot gnu.org
2023-03-28 16:25 ` chgros at synopsys dot com
2023-03-28 16:35 ` redi at gcc dot gnu.org
2023-03-28 16:38 ` 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-109305-4-EyuEvWsftg@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).