| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Fix out-of-bound read in LZ4_decompress_fast()
|
| | |
|
| |
| |
| |
| |
| | |
the program exit(),
so there is no need to track and dealloc every buffer.
|
| | |
|
| |
| |
| |
| | |
was disabled for tests
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
and deprecate LZ4_decompress_fast(),
with deprecation warnings enabled by default.
Note that, as a consequence of the fix,
LZ4_decompress_fast is now __slower__ than LZ4_decompress_safe().
That's because, since it doesn't know the input buffer size,
it must progress more cautiously into the input buffer
to ensure to out-of-bound read.
|
|/ |
|
|\
| |
| | |
Fix
|
| |\
|/ / |
|
|/ |
|
| |
|
|
|
|
| |
was using wrong memory timing
|
|
|
|
| |
as suggested by @sloutsky in #671
|
|
|
|
| |
for msys2
|
| |
|
|\
| |
| | |
Fix lz4frame inefficiency
|
| | |
|
| | |
|
| |\
| |/
|/| |
|
| |
| |
| |
| |
| | |
which is unable to understand that the variable is necessarily initialized
in spite of an assert just before.
|
| |
| |
| |
| |
| |
| | |
context is no longer dirty after a failed compressed block.
Actually, all indexes are fine.
It remains compatible with continued streaming, and reset*_fast().
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
between lz4.c and lz4hc.c .
was left in a strange state after the "amalgamation" patch.
Now only 3 directives remain,
same name across both implementations,
single definition place.
Might allow some light simplification due to reduced nb of states possible.
|
| |\
| |/
|/| |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
they are classified as deprecated in the API documentation (lz4.h)
but do not yet trigger a warning,
to give time to existing applications to move away.
Also, the _fast() variants are still ~5% faster than the _safe() ones
after Dave's patch.
|
|/
|
|
|
|
|
| |
when one block was not compressible,
it would tag the context as `dirty`,
resulting in compression automatically bailing out of all future blocks,
making the rest of the frame uncompressible.
|
|
|
|
| |
was a false positive, but better remove it anyway
|
|
|
|
| |
ensure canary remains within buffer limits
|
|
|
|
|
|
| |
One test could write a canary value out of bound
in exceptional conditions involving multiple flushes
triggered by -s3421 -t462948.
|
|\ |
|
| |\
| | |
| | | |
Fix some Visual conversion warnings
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
yet some overly cautious overflow risk flag,
while it's actually impossible, due to previous test just one line above.
Changing the cast position, just to be please the thing.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
since Visual 2017,
worries about potential overflow, which are actually impossible.
Replaced (c * a) by (c ? a : 0).
Will likely replaced a * by a cmov.
Probably harmless for performance.
|
|/ /
| |
| |
| | |
output can use the full length of output buffer
|
| | |
|
|\ \
| |/
| | |
Fix combination -m -c
|
| |
| |
| |
| | |
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.
|