Clarify, in a comment, that offset/256 fits in 3 bits. It has to in this context, because the other 5 bits in the byte are used for len-4 and the tag.
PiperOrigin-RevId: 374926553
This commit is contained in:
committed by
Victor Costan
parent
2b63814b15
commit
d8f5dd8eca
@@ -905,7 +905,7 @@ TEST(Snappy, VerifyCharTable) {
|
|||||||
// COPY_1_BYTE_OFFSET.
|
// COPY_1_BYTE_OFFSET.
|
||||||
//
|
//
|
||||||
// The tag byte in the compressed data stores len-4 in 3 bits, and
|
// The tag byte in the compressed data stores len-4 in 3 bits, and
|
||||||
// offset/256 in 5 bits. offset%256 is stored in the next byte.
|
// offset/256 in 3 bits. offset%256 is stored in the next byte.
|
||||||
//
|
//
|
||||||
// This format is used for length in range [4..11] and offset in
|
// This format is used for length in range [4..11] and offset in
|
||||||
// range [0..2047]
|
// range [0..2047]
|
||||||
|
|||||||
Reference in New Issue
Block a user