[llvm-dev] Overlapping memcpy
Maciej Adamczyk via llvm-dev
llvm-dev at lists.llvm.org
Mon Dec 7 22:32:59 PST 2015
> +1. Why would one care about the performance of decompressing a
> stream? As soon as a stream is identified as corrupted, you want to
> of decompression without writing additional data. Otherwise you are
> 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.
More information about the llvm-dev