| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
including 128-bit, like IBM AS-400
|
|\
| |
| | |
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.
|
| |
| |
| |
| |
| |
| | |
simplified match finder
only searching forward and within current buffer,
for easier testing of optimizations.
|
|\ \
| | |
| | | |
Fix frametest error
|
| | |
| | |
| | |
| | |
| | |
| | | |
don't fix dictionaries of size 0.
setting dictEnd == source triggers prefix mode,
thus removing possibility to use CDict.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The error can be reproduced using following command :
./frametest -v -i100000000 -s1659 -t31096808
It's actually a bug in the stream LZ4 API,
when starting a new stream
and providing a first chunk to complete with size < MINMATCH.
In which case, the chunk becomes a dictionary.
No hash was generated and stored,
but the chunk is accessible as default position 0 points to dictStart,
and position 0 is still within MAX_DISTANCE.
Then, next attempt to read 32-bits from position 0 fails.
The issue would have been mitigated by starting from index 64 KB,
effectively eliminating position 0 as too far away.
The proper fix is to eliminate such "dictionary" as too small.
Which is what this patch does.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
* Uninstall didn't remove the pkg-config correctly.
* Fix `mandir`
* Allow overriding either upper- or lower-case location variables, but
always use the lower case variables.
* Add test case that ensures overriding both upper- and lower-case
variables is the same, and that the directory is empty after uninstall.
|