ensure conformance with custom LZ4_DISTANCE_MAX
authorYann Collet <cyan@fb.com>
Mon, 15 Jul 2019 19:11:34 +0000 (12:11 -0700)
committerYann Collet <cyan@fb.com>
Mon, 15 Jul 2019 19:11:34 +0000 (12:11 -0700)
commit6654c2cd3bd49dfc6b6bb3447bcc01799ea35ac3
treecc41ddbff1fe2aaf4d35fe12516f5a697f99fd7a
parenta23541463d924f11dfc0843f4ddb10a1e777e405
ensure conformance with custom LZ4_DISTANCE_MAX

It's now possible to select a custom LZ4_DISTANCE_MAX at compile time,
provided it's <= 65535.

However, in some cases (when compressing in byU16 mode),
the new distance wasn't respected,
as it used to implied that it was necessarily within range.

Added a distance check for this case.
Also : added a new TravisCI test which ensures that
custom LZ4_DISTANCE_MAX compiles correctly
and compresses correctly (relying on `assert()` to find outsized offsets).
.travis.yml
lib/README.md
lib/lz4.c
tests/Makefile
tests/frametest.c