memcpy overlap: quickly detect, diagnose, work around

[Gregory Maxwell]

On Mon, Nov 29, 2010 at 6:35 PM, John Reiser <jreiser at bitwagon.com> wrote:
> While the details of inlining are subject
> to change, copying in ascending address order is the order that is
> assumed by all violators of the no-overlap requirement.

All violators? Citation needed.

I'm sure lurking somewhere there are ovelap copies which have no
'assumption' at all— some bad luck with arithmetic makes it ovelap
during some rare alignment of the stars... though cases like that
aren't going to be the ones that get inlined by GCC.