Re: Use __restrict for __relocate_object_a

2019-04-27 Thread Jonathan Wakely
On 27/04/19 12:03 +0200, Marc Glisse wrote: Hello, this small patch feels safe: we are moving an existing object to an uninitialized location so the 2 locations can't overlap. And it helps with std::vector> where it lets the compiler get rid of the branches "if(...) delete ..." when moving el

Use __restrict for __relocate_object_a

2019-04-27 Thread Marc Glisse
Hello, this small patch feels safe: we are moving an existing object to an uninitialized location so the 2 locations can't overlap. And it helps with std::vector> where it lets the compiler get rid of the branches "if(...) delete ..." when moving elements around, for instance in reserve(). We