ddidderr/zstd-rs
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

made accuracy limits "hard" instead of "recommended"

Browse Source
This commit is contained in:
Yann Collet
2016-07-22 19:32:07 +02:00
parent d9cc442a24
commit 9d6e9492ac
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
zstd_compression_format.md
+2 -4
View File
@@ -921,10 +921,8 @@ since it will be discovered and reported by the decoding process.
The bitstream starts by reporting on which scale it operates. The bitstream starts by reporting on which scale it operates.
`AccuracyLog = low4bits + 5;` `AccuracyLog = low4bits + 5;`
In theory, it can define a scale from 5 to 20. Note that maximum `AccuracyLog` for literal and match lengthes is `9`,
In practice, decoders are allowed to limit the maximum supported `AccuracyLog`. and for offsets it is `8`. Higher values are considered errors.
Recommended maximum are `9` for literal and match lengthes, and `8` for offsets.
The reference decoder uses these limits.
Then follow each symbol value, from `0` to last present one. Then follow each symbol value, from `0` to last present one.
The nb of bits used by each field is variable. The nb of bits used by each field is variable.