| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
to reduce confusion in traces between dev branch and latest v1.9.3 release.
|
| |
|
|
|
|
| |
to specifically call attention to offset==0 scenario,
which is invalid, and could lead to some form of security issue
if incorrectly dealt with (ignored).
|
| |
|
| |
Mini typo
|
| |\
| |
| | |
make UNAME externally definable
|
| | |
| |
| |
| |
| |
| |
| | |
on top of providing a central definition place, which eases maintenance,
it might also help for #1021.
Also : updated doc
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
| |
and update manuals.
fix #712
|
| |
|
|
| |
to v1.9.3
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
EndMark, the 4-bytes value indicating the end of frame,
must be `0x00000000`.
Previously, it was just mentioned as a `0-size` block.
But such definition could encompass uncompressed blocks of size 0,
with a header of value `0x80000000`.
But the intention was to also support uncompressed empty blocks.
They could be used as a keep-alive signal.
Note that compressed empty blocks are already supported,
it's just that they have a size 1 instead of 0 (for the `0` token).
Unfortunately, the decoder implementation was also wrong,
and would also interpret a `0x80000000` block header as an endMark.
This issue evaded detection so far simply because
this situation never happens, as LZ4Frame always issues
a clean 0x00000000 value as a endMark.
It also does not flush empty blocks.
This is fixed in this PR.
The decoder can now deal with empty uncompressed blocks,
and do not confuse them with EndMark.
The specification is also clarified.
Finally, FrameTest is updated to randomly insert empty blocks during fuzzing.
|
| |
|
|
| |
to reduce risks that future bug reports in `dev` branch report `v1.9.1` as the failing version.
|
| |
|
|
| |
and that such metadata must be provided / sent / saved by the application.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
to v1.9.1
|
| |
|
|
| |
and created target cxx17build
|
| |
|
|
| |
as this is a very frequent source of confusion for new users.
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
it is now a pure initializer, for statically allocated states.
It can initialize any memory area, and because of this, requires size.
|
| |
|
|
|
|
|
|
|
|
| |
- 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*.
|
| |
|
|
| |
updated modification
|
| |
|
|
| |
and bumped version number fo v1.9.0
|
| |
|
|
| |
as requested in #642
|
| |
|
|
|
| |
re-wording non-full blocks,
for clarity.
|
| |
|
|
|
| |
rewording the end of block conditions
for clarity and answering related questions.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| | |
to clarify #589
|
| | |
| |
| |
| | |
to reduce memory usage on 128-bits systems
|
| |\ \
| | |
| | | |
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
|
| |/ /
| |
| |
| |
| |
| |
| | |
as detected in #485 by @JoachimSchneider.
Refactored the c_standards tests
so that these issues get automatically detected in CI tests.
|
| |/
|
|
| |
used for v1.8.2 announcement
|
| | |
|
| |
|
|
|
|
| |
following suggestion from @stbrumme (#558)
Also : bumped version number, regenerated man page and html doc
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
the initial intention was to update lz4f ring buffer strategy,
but lz4f doesn't use ring buffer.
Instead, it uses the destination buffer as much as possible,
and merely copies just what's required to preserve history
into its own buffer, at the end.
Pretty efficient.
This patch just clarifies a few comments and add some assert().
It's built on top of #528.
It also updates doc.
|
| |\
| |
| | |
Faster decoding speed
|
| | |
| |
| |
| |
| |
| |
| | |
also :
- fix a potential malloc error
- proper use of ALLOC macro inside lz4hc
- update html API doc
|
| | |
| |
| |
| | |
clarifying parsing restrictions near end of block.
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It occurred to me that the formula "The last 5 bytes are always
literals", on the list of "assumptions made by the decoder", is
remarkably ambiguous. Suppose the decoder is presented with 5 bytes.
Are they literals? It may seem that the decoder degenerates
to memcpy on short inputs. But of course the answer is no,
so the formula needs some clarification.
Parsing restrictions should be explained as well, otherwise they look
like arbitrary numbers. The 5-byte restriction has been mentioned
recently in connection with the shortcut in LZ4_decompress_generic,
so I add that. The second restriction is left to be explained
by the author.
I also took the liberty to explain that empty inputs "are either
unrepresentable or can be represented with a null byte". This wording
may actually have some merit: it leaves for the implementation,
as opposed to the spec, to decide whether the encoder can compress
empty inputs, and whether the decoder can produce an empty output
(which the implementation should further clarify).
|
| | |
|
