> Yeah, it looks like the memcpy is sometimes unnecessary because res and
> ptr point to the same place. It might be worth cleaning up just to
> avoid the valgrind warning, but I doubt it would save any noticeable
> number of cycles.
I assume valgrind is warning about it because memcpy's behaviour is
undefined if the blocks overlap. I'm having trouble imagining an
implementation that would fail if they're precisely the same pointer
though.
--
greg
