AuroraMiddleware/zstd
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge pull request #1384 from ulikunitz/dev

Browse Source 
Clarify special case of offset history update
This commit is contained in:
Yann Collet 2018-10-23 14:34:58 -07:00 committed by GitHub
commit 059aa1b8f1
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/zstd_compression_format.md
View File

@ -919,6 +919,10 @@ This means that when `Repeated_Offset1` (most recent) is used, history is unmodi
When `Repeated_Offset2` is used, it's swapped with `Repeated_Offset1`.
If any other offset is used, it becomes `Repeated_Offset1` and the rest are shift back by one.
In the case of an `offset_value` of 3 and the literal length of the current
sequence is zero the value `Repeated_Offset1 - 1_byte` is a new offset,
becoming the lead of the offset history and the first two repeated offsets will
be shifted back.
Skippable Frames
----------------