This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Use __builtin_memmove for trivially copy assignable types
- From: Ville Voutilainen <ville dot voutilainen at gmail dot com>
- To: "libstdc++" <libstdc++ at gcc dot gnu dot org>
- Cc: Glen Fernandes <glen dot fernandes at gmail dot com>, gcc-patches List <gcc-patches at gcc dot gnu dot org>, Jonathan Wakely <jwakely at redhat dot com>
- Date: Tue, 19 Jun 2018 01:12:33 +0300
- Subject: Re: [PATCH] Use __builtin_memmove for trivially copy assignable types
- References: <CAHVPgz=BsNLPv-Q=uvbF2L8qw1hG3mhJFpU1uudYURddxpxP-Q@mail.gmail.com> <alpine.DEB.2.21.1806161703210.4013@stedding.saclay.inria.fr>
On 16 June 2018 at 18:05, Marc Glisse <marc.glisse@inria.fr> wrote:
> On Sat, 16 Jun 2018, Glen Fernandes wrote:
>
>> Use __builtin_memmove for trivially copy assignable types
>>
>> 2018-06-14 Glen Joseph Fernandes <glenjofe@gmail.com>
>>
>> * include/bits/stl_algobase.h
>> (__is_simple_copy_move): Defined helper.
>> (__copy_move_a): Used helper.
>> (__copy_move_backward_a): Likewise.
>> * testsuite/25_algorithms/copy/58982.cc: Updated tests.
>> * testsuite/25_algorithms/copy_n/58982.cc: Likewise.
>>
>> Tested x86_64-pc-linux-gnu.
>
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68350 looks related but for a
> different function. Hopefully the issues discussed there don't apply here...
I would certainly prefer this sort of patches to check via tests that
uninitialized_{copy,move} is unaffected.