facebook
/
zstd
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

correction on offset history (swap when llCode==0)

dev
Yann Collet 2016-07-30 13:12:34 +02:00
parent f714f59c16
commit f34035ecfb
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
zstd_compression_format.md
View File

@ -1081,9 +1081,9 @@ As seen in [Offset Codes], the first 3 values define a repeated offset.
They are sorted in recency order, with 1 meaning "most recent one". They are sorted in recency order, with 1 meaning "most recent one".
There is an exception though, when current sequence's literal length is `0`. There is an exception though, when current sequence's literal length is `0`.
In which case, 1 would just make previous match longer. In which case, the first 2 values are swapped,
Therefore, in such case, 1 means in fact 2, and 2 is impossible. meaning `2` refers to the most recent offset,
Meaning of 3 is unmodified. while `1` refers to the second most recent offset,
Repeat offsets start with the following values : 1, 4 and 8 (in order). Repeat offsets start with the following values : 1, 4 and 8 (in order).