| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
seems to work properly
|
|
|
|
| |
can compress multiple files into stdout
|
|\
| |
| | |
added command -BI for "Independent Blocks"
|
|/
|
|
|
|
|
|
| |
This is the reverse of `-BD`, and the current default.
This command can be useful to reverse a previous `-BD` command.
It may in the future be more important
if `lz4` switches to generating dependent blocks by default.
|
|
|
|
| |
with --favor-decSpeed
|
|
|
|
| |
as this is a very frequent source of confusion for new users.
|
|\
| |
| | |
Dictionary compression
|
| | |
|
|\ \
| |/
| | |
introduce LZ4_DISTANCE_MAX build macro
|
|/
|
|
|
|
|
|
|
|
| |
make it possible to generate LZ4-compressed block
with a controlled maximum offset (necessarily <= 65535).
This could be useful for compatibility with decoders
using a very limited memory budget (<64 KB).
Answer #154
|
|
|
|
| |
aka distance from end of block for the last match.
|
|\
| |
| | |
made LZ4F_getHeaderSize() public
|
| | |
|
|/ |
|
|\
| |
| | |
LZ4_resetStream*_fast()
|
| |
| |
| |
| |
| | |
by making a full initialization
instead of a fast reset.
|
| |
| |
| |
| | |
towards deprecation, but still available and fully supported
|
| |
| |
| |
| |
| | |
it is now a pure initializer, for statically allocated states.
It can initialize any memory area, and because of this, requires size.
|
| |
| |
| |
| | |
ensure it's not NULL.
|
| |
| |
| |
| |
| |
| |
| | |
it fails on x86 32-bit mode :
Visual reports an alignment of 8-bytes (even with alignof())
but actually only align LZ4_stream_t on 4 bytes.
The alignment check then fails, resulting in missed initialization.
|
| |
| |
| |
| | |
not liked by mingw
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
level down 5->4
size down 6G->5G
|
| | |
|
| |
| |
| |
| | |
updated associated documentation
|
| |
| |
| |
| | |
as suggested by @felixhandte
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- promoted LZ4_resetStream_fast() to stable
- moved LZ4_resetStream() into deprecate, but without triggering a compiler warning
- update all sources to no longer rely on LZ4_resetStream()
note : LZ4_initStream() proposal is slightly different :
it's able to initialize any buffer, provided that it's large enough.
To this end, it accepts a void*, and returns an LZ4_stream_t*.
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
| |
- promoted LZ4_resetStreamHC_fast() to stable
- moved LZ4_resetStreamHC() to deprecated (but do not generate a warning yet)
- Updated doc, to highlight difference between init and reset
- switched all invocations of LZ4_resetStreamHC() onto LZ4_initStreamHC()
- misc: ensure `make all` also builds /tests
|
|\
| |
| | |
Deprecated LZ4_decompres_fast*() functions
|
| |
| |
| |
| | |
updated modification
|
|/ |
|
|\
| |
| | |
moved _destSize() into "stable API" status
|
| |
| |
| |
| |
| |
| |
| | |
which remained undetected so far,
as it requires a fairly large number of conditions to be triggered,
starting with enabling Block checksum, which is disabled by default,
and which usage is known to be extremely rare.
|
| |
| |
| |
| | |
and bumped version number fo v1.9.0
|
|/
|
|
| |
as requested in #642
|
|\
| |
| | |
LZ4_FAST_DEC_LOOP macros
|
| | |
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Allow installation of lz4 for Windows 10 with MSYS2
|
| | |
|
|\ \
| | |
| | | |
Optimize decompress generic
|
| | |
| | |
| | |
| | |
| | | |
New fastpath currently shows a regression on qualcomm
arm chips. Restrict it to x86 for now
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For small offsets of size 1, 2, 4 and 8, we can set a single uint64_t,
and then use it to do a memset() variation. In particular, this makes
the somewhat-common RLE (offset 1) about 2-4x faster than the previous
implementation - we avoid not only the load blocked by store, but also
avoid the loads entirely.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Generally we want our wildcopy loops to look like the
memcpy loops from our libc, but without the final byte copy checks.
We can unroll a bit to make long copies even faster.
The only catch is that this affects the value of FASTLOOP_SAFE_DISTANCE.
|