From: Yann Collet Date: Fri, 22 Jul 2016 17:32:07 +0000 (+0200) Subject: made accuracy limits "hard" instead of "recommended" X-Git-Tag: v0.8.0^2~55 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9d6e9492acc6fdf6ab700ea2ab279de6201544a5;p=thirdparty%2Fzstd.git made accuracy limits "hard" instead of "recommended" --- diff --git a/zstd_compression_format.md b/zstd_compression_format.md index 5dbc41a26..42fe3e0c4 100644 --- a/zstd_compression_format.md +++ b/zstd_compression_format.md @@ -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. `AccuracyLog = low4bits + 5;` -In theory, it can define a scale from 5 to 20. -In practice, decoders are allowed to limit the maximum supported `AccuracyLog`. -Recommended maximum are `9` for literal and match lengthes, and `8` for offsets. -The reference decoder uses these limits. +Note that maximum `AccuracyLog` for literal and match lengthes is `9`, +and for offsets it is `8`. Higher values are considered errors. Then follow each symbol value, from `0` to last present one. The nb of bits used by each field is variable.