| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | minor frame format clarification | Yann Collet | 2022-07-10 | 1 | -2/+1 |
| | | | | | no need to specify that a decoder can "ignore the checksum". | ||||
| * | fix spelling | a1346054 | 2021-08-21 | 1 | -4/+4 |
| | | |||||
| * | updated license & header dates | Yann Collet | 2020-11-25 | 1 | -1/+1 |
| | | |||||
| * | update doc | Yann Collet | 2020-11-15 | 1 | -2/+2 |
| | | |||||
| * | clarify endMark definition | Yann Collet | 2020-08-14 | 1 | -4/+4 |
| | | |||||
| * | Clarifies and fix EndMark | Yann Collet | 2020-08-13 | 1 | -18/+29 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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. | ||||
| * | updated frame format | Yann Collet | 2019-01-02 | 1 | -7/+10 |
| | | | | | | re-wording non-full blocks, for clarity. | ||||
| * | lz4_Frame_format.md: Fix typo HexaBytes -> Exabytes | Niklas Hambüchen | 2018-11-24 | 1 | -1/+1 |
| | | |||||
| * | fix typos as suggested by @psteinb | Yann Collet | 2018-01-31 | 1 | -2/+2 |
| | | |||||
| * | proposed a minor change to LZ4 Frame format specification | Yann Collet | 2018-01-31 | 1 | -4/+12 |
| | | | | | add new terms "LZ4 Frame Header" and "LZ4 Frame Footer" | ||||
| * | added dictID inside LZ4F_frameInfo_t | Yann Collet | 2017-08-09 | 1 | -2/+1 |
| | | | | | | Compressor can set dictID on LZ4F_compressBegin() Decompressor can retrieve it using LZ4F_getFrameInfo() | ||||
| * | updated Frame specification | Yann Collet | 2017-08-08 | 1 | -25/+52 |
| | | | | | | Restored DictID field in Frame header Bumped specification version to v1.6.0 | ||||
| * | [Doc] Fix markdown | Chocobo1 | 2017-05-25 | 1 | -2/+2 |
| | | |||||
| * | documentation moved to doc/ | Przemyslaw Skibinski | 2016-11-03 | 1 | -0/+385 |
 |
index : lz4.git | |
| LZ4 is lossless compression algorithm, providing compression speed > 500 MB/s per core, scalable with multi-cores CPU. It features an extremely fast decoder, with speed in multiple GB/s per core, typically reaching RAM speed limits on multi-core systems. |
| summaryrefslogtreecommitdiffstats |