This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch] libstdc++/66742 use allocators correctly in list::sort()
- From: Jonathan Wakely <jwakely at redhat dot com>
- To: Daniel Krügler <daniel dot kruegler at gmail dot com>
- Cc: libstdc++ <libstdc++ at gcc dot gnu dot org>, gcc-patches List <gcc-patches at gcc dot gnu dot org>
- Date: Fri, 3 Jul 2015 18:37:57 +0100
- Subject: Re: [patch] libstdc++/66742 use allocators correctly in list::sort()
- Authentication-results: sourceware.org; auth=none
- References: <20150703155115 dot GK18520 at redhat dot com> <CAGNvRgDo4Ja6H-6_MHAF8c9N03paWiyqNd3eVpj7Qsa4+w-22Q at mail dot gmail dot com>
On 03/07/15 18:56 +0200, Daniel Krügler wrote:
- Isn't it necessary to cope with possibly final allocators when
unconditionally forming the derived member class
struct _Impl : allocator_type
If the allocator was final we couldn't even instantiate std::list
because of this in _List_base:
struct _List_impl
: public _Node_alloc_type
{
This is https://gcc.gnu.org/PR60921 and I'm going to fix it
everywhere, so I'm not concerned about this one place yet.