| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
are changed by the function call
|
|\
| |
| | |
lz4hc.c: change (length >> 8) to (length / 255)
|
| |
| |
| | |
Every 0xff byte in the compressed block corresponds to a length of 255 (not 256) in the input data. For long repeating sequences, using (length >> 8) may generate bad compressed blocks.
|
|/ |
|
|
|
|
|
|
|
| |
Dictionaries don't need to be > 4 bytes, they need to be >= 4 bytes. This test
was overly conservative.
Also removes the test in `LZ4_attach_dictionary()`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes a mismatch in behavior between loading into the context (via
`LZ4_loadDict()`) a very small (<= 4 bytes) non-contiguous dictionary, versus
attaching it with `LZ4_attach_dictionary()`.
Before this patch, this divergence could be reproduced by running
```
make -C tests fuzzer MOREFLAGS="-m32"
tests/fuzzer -v -s1239 -t3146
```
Making sure these two paths behave exactly identically is an easy way to test
the correctness of the attach path, so it's desirable that this remain an
unpolluted, high signal test.
|
|\ |
|
| |\
| | |
| | | |
[amalgamation] lz4frame.c
|
| | | |
|
|/ / |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
This fix cross compilation on linux for Windows
|
|/
|
|
| |
This allow cross-compilation for Windows on Linux
|
| |
|
|\
| |
| | |
Extend Macro to Allow Publishing Experimental LZ4HC Functions in Dynamic Libraries
|
| | |
|
| | |
|
| |
| |
| |
| | |
to clarify #589
|
| | |
|
|\ \
| | |
| | | |
fix LZ4F_compressEnd()
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
following recommendations by @raggi.
The fix is slightly different, but achieves the same goal,
and is backed by a test tool which proves that it works
(generates the error before the patch, no longer after the patch).
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
which actively tries to make it write out of bound.
For this scenario to be possible,
it's necessary to set dstCapacity < LZ4F_compressBound()
When a compression operation fails,
the CCtx context is left in an undefined state,
therefore compression cannot resume.
As a consequence :
- round trip tests must be aborted, since there is nothing valid to decompress
- most users avoid this situation, by ensuring that dstCapacity >= LZ4F_compressBound()
For these reasons, this use case was poorly tested up to now.
|
|/ |
|
|\
| |
| | |
fixed improper hint
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
when LZ4F_decompress() decodes an uncompressed block,
it provides an incorrect hint for next block
when frame checksum is enabled and block checksum is not.
Impact is low : the hint is just an hint,
the decoder works whatever the amount of input provided.
But the assumption that each call to LZ4F_decompress()
would generate just one complete block if input size hint was respected
was broken by this error.
|
|/
|
|
| |
check if full reset is needed.
|
|\
| |
| | |
Support for 128bit pointers like AS400
|
| |
| |
| |
| | |
to reduce memory usage on 128-bits systems
|
| | |
|
| |\ |
|
| | | |
|
| | |
| | |
| | |
| | | |
including 128-bit, like IBM AS-400
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
so "funny" thing with cppcheck
is that no 2 versions give the same list of warnings.
On Mac, I'm using v1.81, which had all warnings fixed.
On Travis CI, it's v1.61, and it complains about a dozen more/different things.
On Linux, it's v1.72, and it finds a completely different list of a half dozen warnings.
Some of these seems to be bugs/limitations in cppcheck itself.
The TravisCI version v1.61 seems unable to understand %zu correctly, and seems to assume it means %u.
|
| | | |
|
| |/
|/| |
|
|\ \
| |/
|/| |
unpublish static-only functions
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
these functions are now unpublished in dll by default.
One needs to opt-in, using macro LZ4_PUBLISH_STATIC_FUNCTIONS.
used this opportunity to update a bunch of api comments in lz4.h
|
|\ \
| | |
| | | |
avoid final trailing comma for enum lists
|
| |/
| |
| |
| |
| |
| |
| | |
as detected in #485 by @JoachimSchneider.
Refactored the c_standards tests
so that these issues get automatically detected in CI tests.
|
|\ \
| |/
|/| |
FIx pkgconfig file installation on MidnightBSD
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
and separate it from MATCH_SAFEGUARD_DISTANCE.
While both constants have same value,
they do not seve same purpose, hence should not be confused.
|
| |
| |
| |
| | |
added a few more comments and assert()
|
| |
| |
| |
| | |
to counter possible (offset==0)
|
| | |
|