News for hackers. Stuff that matters.
Re:Memcpy vs. memmove by pkhuong on Monday December 01, 2014 @05:06PM (#8684215)
Aliasing optimisations will fire regardless of how memcpy/memmove are implemented.
Re:Memcpy vs. memmove by pascal_cuoq on Tuesday December 02, 2014 @06:45AM (#8686656)
Replying for masklinn, perhaps what they had in mind was the discovery of optimizations that are not allowed by strict aliasing rules. Consider:

    int *p, *q, x;
    ...
    memmove(p, q, 50 * sizeof(int));
    p[2] = 3;
    q[3] = 4;
    x = p[2];
In the example above, it is illegal (with only the information available) to optimize the last assignment to x = 3. Strict aliasing does not apply because everything is int.

If the call to memmove were a call to memcpy instead, a sufficiently creative compiler author could argue that the optimization of the last statement to x = 3 is legal, because the call to memcpy asserts (among other things) that the int pointed by p+2 does not have any bit in common with the int pointed by q+3.

I don't know how often that would trigger or how useful that would be. But I work on a system in which C programs can be annotated with properties (including non-aliasing properties: see http://blog.frama-c.com/index.php?post/2012/07/25/On-the-red... and http://blog.frama-c.com/index.php?post/2012/07/25/The-restri... ), and that makes me pretty confident that this would be sound and, unlike a joke I made two years ago about the redundancy of restrict in C99, workable.

Re:Memcpy vs. memmove by pkhuong on Tuesday December 02, 2014 @09:10AM (#8687136)
That's exactly the kind of optimisation that I had in mind. What I'm saying is that the static analysis would work the same even if memcpy was implemented by jumping to memmove or some linker trick to make it resolve to memmove.