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: Tue, 28 Mar 2023 16:35:38 +0000 [thread overview]
Message-ID: <bug-109305-4-OJdOS8S4Dx@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
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #5)
> Removing it would make the code less efficient and more complex.
In fact, I don't even see how it would be possible, except by making *another*
copy, e.g.
--- a/libstdc++-v3/include/bits/basic_string.h
+++ b/libstdc++-v3/include/bits/basic_string.h
@@ -1588,20 +1588,33 @@ _GLIBCXX_BEGIN_NAMESPACE_CXX11
_M_destroy(_M_allocated_capacity);
_M_data(_M_use_local_data());
_M_set_length(0);
+ std::__alloc_on_copy(_M_get_allocator(),
+ __str._M_get_allocator());
}
else
{
+ auto __backup_alloc = _M_get_allocator();
+ std::__alloc_on_copy(_M_get_allocator(),
+ __str._M_get_allocator());
const auto __len = __str.size();
- auto __alloc = __str._M_get_allocator();
- // If this allocation throws there are no effects:
- auto __ptr = _Alloc_traits::allocate(__alloc, __len + 1);
- _M_destroy(_M_allocated_capacity);
+ pointer __ptr;
+ __try {
+ __ptr = _Alloc_traits::allocate(_M_get_allocator(),
+ __len + 1);
+ } __catch (...) {
+ std::__alloc_on_copy(_M_get_allocator(), __backup_alloc);
+ __throw_exception_again;
+ }
+ _Alloc_traits::deallocate(__backup_alloc, _M_data(),
+ _M_allocated_capacity + 1);
_M_data(__ptr);
_M_capacity(__len);
_M_set_length(__len);
}
}
- std::__alloc_on_copy(_M_get_allocator(), __str._M_get_allocator());
+ else
+ std::__alloc_on_copy(_M_get_allocator(),
+ __str._M_get_allocator());
}
#endif
this->_M_assign(__str);
This makes the code much worse, and slower, and still has a copy (the
__backup_alloc) variable.
next prev parent reply other threads:[~2023-03-28 16:35 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
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 [this message]
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-OJdOS8S4Dx@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).