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: Glen Fernandes <glen dot fernandes at gmail dot com>
- To: ville dot voutilainen at gmail dot com
- Cc: libstdc++ at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, jwakely at redhat dot com
- Date: Mon, 18 Jun 2018 21:28:55 -0400
- 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> <CAFk2RUbAjawC2uAYJig=t9CmZ8DyF3-r-8D8M3YUWBDdrH70QA@mail.gmail.com>
On Mon, Jun 18, 2018 at 6:12 PM Ville Voutilainen wrote:
> On 16 June 2018 at 18:05, Marc Glisse 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.
Will do.
Glen