> Looking at the comment for NOMEMCPY in inflate.c, it's quite possible > it was added precisely to work around this bug.
Only inflate.c issue, replacing with memmove() will be good choice. But the same problem is still remain explode.c so I choose NOMEMCPY. I compared execution time, NOMEMCPY is slightly faster (OpenBSD/amd64 on Pentium G4600 machine). Maybe the result may be different on other architecture. memmove() real 0m0.359s user 0m0.340s sys 0m0.010s -DNOMEMCPY real 0m0.321s user 0m0.290s sys 0m0.000s -- SASANO Takayoshi (JG1UAA) <u...@mx5.nisiq.net>
