| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Specifically this adds support for the following options:
- LZ4_ALIGN_TEST
- LZ4_STATIC_LINKING_ONLY_DISABLE_MEMORY_ALLOCATION
- LZ4_DISTANCE_MAX
- LZ4_FAST_DEC_LOOP
- LZ4_FORCE_SW_BITCOUNT
- LZ4_FREESTANDING
- LZ4_USER_MEMORY_FUNCTIONS
- compiling ossfuzz targets
- compiling more test targets
- registering some tests
|
|
|
|
| |
also : errors during benchmark mode return an error code.
|
|
|
|
|
|
|
|
|
|
| |
where `--test -m files*.lz4` would create a bunch of `files*` files.
`--test` should not create any file.
It turns out the bug was already fixed when #1164 was filled,
but it also shows that the CI system was blind to such issues when it happened.
The new test was run with `v1.9.3` and triggered an error, as expected.
|
| |
|
|
|
|
| |
https://docs.microsoft.com/en-us/cpp/c-runtime-library/reference/strtoui64-wcstoui64-strtoui64-l-wcstoui64-l
|
|
|
|
|
|
|
|
| |
This patch fixes the following error from "make staticAnalyze"
datagencli.c:106:21: warning: Value stored to 'size' is never read
size=0;
^ ~
|
|
|
|
|
|
|
| |
Suppress the following false positive warnings from MSVC:
- Disable all arithmetic overflow (C26451)
- Suppress C6385: Reading invalid data from 'compressedBuffer'.
- Add ULL suffix to unsigned 64-bits constants.
|
|
|
|
|
|
|
|
|
|
|
| |
MSVC 2022 reports the follwing false positve warnings:
lz4\tests\datagencli.c(110): warning C26451: Arithmetic overflow: Using operator '-' on a 4 byte value and then casting the result to a 8 byte value. Cast the value to the wider type before calling operator '-' to avoid overflow (io.2).
lz4\tests\datagencli.c(134): warning C26451: Arithmetic overflow: Using operator '-' on a 4 byte value and then casting the result to a 8 byte value. Cast the value to the wider type before calling operator '-' to avoid overflow (io.2).
lz4\tests\datagencli.c(146): warning C26451: Arithmetic overflow: Using operator '-' on a 4 byte value and then casting the result to a 8 byte value. Cast the value to the wider type before calling operator '-' to avoid overflow (io.2).
Although they're absolutely compiler's and static analyzer's bug,
it'd always be nice to use the standard library.
|
|
|
|
|
| |
Since test-freestanding is able to be compiled and executed
in specific environment, we should not run it in our standard test.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Also added tests/Makefile entry "test-freestanding".
|
| |
|
|
|
|
|
| |
note : it's unlikely to improve speed, as in most cases I/O is slower than lz4 decompression,
but maybe in extreme scenarios, it might show a difference.
|
| |
|
|
|
|
| |
which disables both frame and block checksums.
|
|
|
|
| |
requires an LZ4 Frame as input
|
|
|
|
|
|
|
| |
for `make -j test`.
note : test-install is no longer part of `make test`
It will have to be run on its own.
|
|\
| |
| | |
Support for Custom Memory managers
|
| | |
|
| |\ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
for compression context only for the time being,
using LZ4F_createCompressionContext_advanced().
Added basic test in frametest.c
|
|\ \ \
| | | |
| | | | |
support skippable frames within pipe
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
fix #977
fseek() doesn't work for pipe,
switch to "read and forget" mode in such case.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
The recently added test decompress-partial-usingDict
tends to fail for unknown reasons,
more frequently under the combination for clang-9 + `-mx32`.
There is a suspicion that the test is using too much stack.
Fixing that, + adding traces, to get more information if it fails again.
|
|/ |
|
| |
|
| |
|
|
|
|
| |
requires liblz4 >= v1.7.5
|
|
|
|
| |
only use current march & default compiler
|
|\
| |
| | |
Add a fuzzer test for LZ4F_uncompressedUpdate() within frametest
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
which was broken up to now.
|
| |
| |
| |
| | |
warning only if -f is selected.
|
|/
|
|
| |
Signed-off-by: Qi Wang <wangqi@linux.alibaba.com>
|
|
|
|
| |
and run it in GA CI
|
|
|
|
|
|
|
| |
ensure that `frametest` works fine with these values,
notably with low LZ4_MEMORY_USAGE (dict test notably)
following suggestions from @t-mat at #1016
|
|\
| |
| | |
Fix list test
|
| | |
|
| | |
|
| | |
|
|/
|
|
| |
fix #1045
|
|\
| |
| | |
fixed bug in optimal parser
|
| |
| |
| |
| | |
discovered by @yoniko.
|
|/
|
|
| |
for --list from stdin
|