| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| | |
|
|\ \ |
|
| |\ \
| | | |
| | | | |
Migrate CircleCI tests from 1.0 towards 2.0
|
| | |\ \
| | | |/ |
|
| |\ \ \
| | |_|/
| |/| | |
Introduced constants LZ4F_INIT_*
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
to simplify initialization of lz4frame.h structures.
Partially in response to #546.
|
| | | | |
|
| | | |
| | | |
| | | |
| | | | |
and removed one blind copy, since there is no more guarantee that at least 4 bytes are still available in output buffer
|
| | | | |
|
| |_|/
|/| | |
|
|/ / |
|
|\ \
| |/
|/| |
updated documentation for dictionary compression
|
| |
| |
| |
| |
| |
| | |
following suggestion from @stbrumme (#558)
Also : bumped version number, regenerated man page and html doc
|
| |
| |
| |
| | |
which is not correct when using LZ4_HC with dictionary and starting from a low address (<0x10000).
|
|/
|
|
|
|
|
| |
it was a fairly complex scenario,
involving source files > 64K
and some extraordinary conditions related to specific layout of ranges of zeroes.
and only on level 9.
|
| |
|
|\
| |
| | |
Add --fast command to cli
|
| |
| |
| |
| | |
negative compresion level
|
|/
|
|
| |
Fixes #549.
|
|\
| |
| | |
allow to override uname when cross-compiling
|
| |
| |
| |
| |
| |
| | |
When cross-compiling for example from Darwin to Linux it might be
useful to override uname output to force Linux and create Linux
libraries instead of Darwin libraries.
|
| | |
|
| | |
|
| | |
|
|/ |
|
|
|
|
| |
lz4 1.8.2 works fine on Haiku and passes all tests.
|
|\
| |
| | |
Speed optimization for optimal parser
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
which measurably improves speed
on levels 9+
|
| |
| |
| |
| |
| |
| | |
also :
reserved PA for levels 9+ (instead of 8+).
In most cases, speed is lower, and compression benefit is not worth.
|
| |
| |
| |
| |
| | |
the trade off is not good for regular HC parser :
compression is a little bit better, but speed cost is too large in comparison.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Only enabled when searching forward.
note : it slighly improves compression ratio,
but measurably decreases speed.
Trade-off to analyse.
|
| |
| |
| |
| | |
when combining both PA and CS optimizations
|
| |
| |
| |
| |
| |
| |
| | |
slower than expected
Pattern analyzer and Chain Swapper
work slower when both activated.
Reasons unclear.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
greatly improves speed compared to non-accelerated,
especially for slower files.
On my laptop, -b12 :
```
calgary.tar : 4.3 MB/s => 9.0 MB/s
enwik7 : 10.2 MB/s => 13.3 MB/s
silesia.tar : 4.0 MB/s => 8.7 MB/s
```
Note : this is the simplified version,
without handling dictionaries, external buffer, nor pattern analyzer.
Current `dev` branch on these samples gives :
```
calgary.tar : 4.2 MB/s
enwik7 : 9.7 MB/s
silesia.tar : 3.5 MB/s
```
interestingly, it's slower,
presumably due to handling of dictionaries.
|