Overlapping memcpy

+1. Why would one care about the performance of decompressing a

corrupted
> stream? As soon as a stream is identified as corrupted, you want to bail out
> of decompression without writing additional data. Otherwise you are almost
> surely introducing a security vulnerability.

This is not about performance on corrupted stream. If that was the case, there would be no question. The problem is that is slows down valid streams just as well.

Your point about bailing out is well taken.

Regards,
Maciej Adamczyk