| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |
|
|
| |
memcpy() on NULL is UB, even if length is 0.
|
| | |
|
| |\ |
|
| | |
| |
| |
| | |
to v1.9.3
|
| |/
|
|
|
| |
detected by scan-build, cppcheck and advanved compilation flags
fix #786
|
| |\
| |
| | |
fix efficiency of LZ4_compress_HC_destSize()
|
| | |
| |
| |
| |
| |
| | |
applying new more accurate formula from LZ4_compress_HC_destSize()
also : fix some minor display issue in tests/frametest
|
| | |
| |
| |
| | |
must respect MFLIMIT distance from oend
|
| | |
| |
| |
| | |
after truncation of last sequence
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
LZ4_compress_HC_destSize() had a tendency
to discard its last match when this match overflowed specified dstBuffer limit.
The impact is generally moderate,
but occasionally huge,
typically when this last match is very large
(such as compressing a bunch of zeroes).
Issue #784 fixed for both Chain and Opt implementations.
Added a unit test suggested by @remittor checking this topic.
|
| |\ \
| | |
| | | |
fix compressing into NULL
|
| | |/
| |
| |
| |
| | |
fails properly
bug discovered by oss-fuzz
|
| |/ |
|
| |
|
|
| |
following investigation in #859
|
| |
|
|
| |
properly track history
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
LZ4_decompress_safe_partial()
now also supports a scenario where
nb_bytes_to_generate is <= block_decompressed_size
And
nb_bytes_to_read is >= block_compressed_size.
Previously, the only supported scenario was
nb_bytes_to_read == block_compress_size.
Pay attention that,
if nb_bytes_to_read is > block_compressed_size,
then, necessarily, it requires that
nb_bytes_to_generate is <= block_decompress_size.
If both are larger, it will generate corrupted data.
|
| |\ |
|
| | |
| |
| |
| |
| | |
Also : added memory-frugal software byte count for big endian 64-bit cpus.
Disabled by default.
|
| | |\
| | |
| | | |
rejigger bit counting intrinsics
|
| | | |
| | |
| | | |
MSVC debug mode complains
|
| | | |
| | |
| | |
| | |
| | | |
Fix lz4/lz4#867
Optimize software fallback routines.
Delete some faulty (and dead?) MSVC big endian code.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
which serves no more purpose.
The comment implies that the simple presence of this unused function was affecting performance,
and that's the reason why it was not removed earlier.
This is likely another side effect of instruction alignment.
It's obviously unreliable to rely on it in this way,
meaning that the impact will be different, positive of negative,
with any minor code change, and any minor compiler version change, even parameter change.
|
| |\ \ \
| |/ / |
|
| | |\ \
| | | |
| | | | |
added target lz4-wlib
|
| | | |/
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
variant of lz4 linking to liblz4 dynamic library
requires the dynamic library to expose static-only symbols (experimental API)
Example for #888
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
EndMark, the 4-bytes value indicating the end of frame,
must be `0x00000000`.
Previously, it was just mentioned as a `0-size` block.
But such definition could encompass uncompressed blocks of size 0,
with a header of value `0x80000000`.
But the intention was to also support uncompressed empty blocks.
They could be used as a keep-alive signal.
Note that compressed empty blocks are already supported,
it's just that they have a size 1 instead of 0 (for the `0` token).
Unfortunately, the decoder implementation was also wrong,
and would also interpret a `0x80000000` block header as an endMark.
This issue evaded detection so far simply because
this situation never happens, as LZ4Frame always issues
a clean 0x00000000 value as a endMark.
It also does not flush empty blocks.
This is fixed in this PR.
The decoder can now deal with empty uncompressed blocks,
and do not confuse them with EndMark.
The specification is also clarified.
Finally, FrameTest is updated to randomly insert empty blocks during fuzzing.
|
| |/
|
| |
* fix issue #783
|
| |\ |
|
| | | |
|
| |\ \
| |/
| | |
fix #832
|
| | |
| |
| |
| | |
does no longer rely on default 0-interpretation when __GNUC__ is not defined
|
| |\ \
| |/
|/| |
Fix #876
|
| | |
| |
| |
| | |
by introducing a max limit acceleration value
|
| |\ \
| |/
|/| |
Remove dirty Flag in LZ4_stream_t
|
| | |
| |
| |
| | |
Fixes `-Wsign-compare` issues.
|
| | | |
|
| | |
| |
| |
| |
| | |
Nothing internally sets dirty anymore. The only way to get that is if you use
an uninitialized context, in which case your warranty is void anyways.
|
| |\ \
| |/
|/| |
Add LZ4FLIB_VISIBILITY for controlling library symbol visibility
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
`LZ4_memcpy()` uses `__builtin_memcpy()` to ensure that clang/gcc
can inline the `memcpy()` calls in freestanding mode.
This is necessary for decompressing the Linux Kernel with LZ4.
Without an analogous patch decompression ran at 77 MB/s, and with
the patch it ran at 884 MB/s.
|
| |\ \
| | |
| | | |
Avoid old-style function definitions
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
Define 0-argument functions like foo(void) instead of foo(), in order
to avoid a warning with -Wold-style-definition. This makes it easier
to embed lz4.c in projects that compile with -Werror
-Wold-style-definition.
|
| |\ \ \
| | | |
| | | | |
Reducing stack usage in _t_alignment checks
|
| | | |/
| |/| |
|
| |\ \ \
| | | |
| | | | |
Fix issue #865
|
| | |/ / |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Similar work in the kernel:
https://patchwork.kernel.org/patch/11351499/
UBsan (+clang-10) complains about doing pointer arithmetic (adding 0)
to a nullpointer.
This patch is tested with clang-10+ubsan
|
