From d8f5dd8ecab790529ee665f4f8a784e9b1b3f687 Mon Sep 17 00:00:00 2001 From: Snappy Team Date: Thu, 20 May 2021 19:29:12 +0000 Subject: 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 --- snappy_unittest.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/snappy_unittest.cc b/snappy_unittest.cc index 7a85635..8782b52 100644 --- a/snappy_unittest.cc +++ b/snappy_unittest.cc @@ -905,7 +905,7 @@ TEST(Snappy, VerifyCharTable) { // COPY_1_BYTE_OFFSET. // // 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 // range [0..2047] -- cgit v1.2.1