From: "François Dumont" <frs.dumont@gmail.com>
To: Jonathan Wakely <jwakely@redhat.com>
Cc: "libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Avoid allocator operator== in _Safe_container
Date: Mon, 9 Aug 2021 14:08:11 +0200 [thread overview]
Message-ID: <7097b577-337f-b488-5f48-5fe97f4a9718@gmail.com> (raw)
In-Reply-To: <e8238cb4-1faa-7618-e5e3-8805921d5b08@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1393 bytes --]
On 09/08/21 1:52 pm, François Dumont wrote:
> On 09/08/21 12:45 pm, Jonathan Wakely wrote:
>> On Mon, 9 Aug 2021 at 11:34, Jonathan Wakely wrote:
>>> On Mon, 9 Aug 2021 at 11:33, Jonathan Wakely wrote:
>>>> On Mon, 9 Aug 2021 at 11:26, François Dumont via Libstdc++
>>>> <libstdc++@gcc.gnu.org> wrote:
>>>>> Some newly introduced tests in
>>>>> 23_containers/unordered_map/cons/default.cc revealed that we are
>>>>> forcing
>>>>> the allocator type to have a operator==.
>>>> All allocators are required to have operator== so that should not be a
>>>> problem. What is the error?
>>> OK, I see it. I just forgot to define operator== and operator!= for
>>> the custom allocator in that new test, and that should be added.
>> Fixed like this instead. Tested x86_64-linux with -D_GLIBCXX_DEBUG.
>> Pushed to trunk.
>
> Ok, I thought my change was better because we have many allocator
> types in tests without operator ==/!= (see
> 23_containers/*/cons/noexcept_default_construct.cc). But of course the
> tests are not making any use of it for the moment, no big deal.
>
> So this patch is just an optimization, may I still commit it ? Unless
> you like the fact that Debug mode is checking that those operators are
> provided when allocator-aware move constructor is being used.
>
>
A simpler version, using _Safe_container move constructor when allocator
instances are always equals.
[-- Attachment #2: safe_container.patch --]
[-- Type: text/x-patch, Size: 1084 bytes --]
diff --git a/libstdc++-v3/include/debug/safe_container.h b/libstdc++-v3/include/debug/safe_container.h
index d9636c29e9b..97c47167fe8 100644
--- a/libstdc++-v3/include/debug/safe_container.h
+++ b/libstdc++-v3/include/debug/safe_container.h
@@ -57,7 +57,12 @@ namespace __gnu_debug
_Safe_container(const _Safe_container&) = default;
_Safe_container(_Safe_container&&) = default;
- _Safe_container(_Safe_container&& __x, const _Alloc& __a)
+ private:
+ _Safe_container(_Safe_container&& __x, const _Alloc&, std::true_type)
+ : _Safe_container(std::move(__x))
+ { }
+
+ _Safe_container(_Safe_container&& __x, const _Alloc& __a, std::false_type)
: _Safe_container()
{
if (__x._M_cont().get_allocator() == __a)
@@ -65,6 +70,12 @@ namespace __gnu_debug
else
__x._M_invalidate_all();
}
+
+ protected:
+ _Safe_container(_Safe_container&& __x, const _Alloc& __a)
+ : _Safe_container(std::move(__x), __a,
+ typename std::allocator_traits<_Alloc>::is_always_equal{})
+ { }
#endif
public:
next prev parent reply other threads:[~2021-08-09 12:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-09 10:23 François Dumont
2021-08-09 10:33 ` Jonathan Wakely
2021-08-09 10:34 ` Jonathan Wakely
2021-08-09 10:45 ` Jonathan Wakely
2021-08-09 11:52 ` François Dumont
2021-08-09 12:08 ` François Dumont [this message]
2021-08-09 14:24 ` Jonathan Wakely
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=7097b577-337f-b488-5f48-5fe97f4a9718@gmail.com \
--to=frs.dumont@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jwakely@redhat.com \
--cc=libstdc++@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).