From: Reimar Döffinger <Reimar.Doeffinger@gmx.de>
Date: Tue, 8 Sep 2009 08:30:56 +0000 (+0000)
Subject: Try to clarify that anyone using get_bits must check for buffer overrun
X-Git-Tag: v0.6~3400
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=17f0c3be8ecbf3555d763007bd51583ad3f63cc0;p=platform%2Fupstream%2Flibav.git

Try to clarify that anyone using get_bits must check for buffer overrun
themselves, get_bits does not do anything in that regard.

Originally committed as revision 19794 to svn://svn.ffmpeg.org/ffmpeg/trunk
---

diff --git a/libavcodec/get_bits.h b/libavcodec/get_bits.h
index 877f909..19333c2 100644
--- a/libavcodec/get_bits.h
+++ b/libavcodec/get_bits.h
@@ -489,6 +489,9 @@ static inline int check_marker(GetBitContext *s, const char *msg)
  * @param buffer bitstream buffer, must be FF_INPUT_BUFFER_PADDING_SIZE bytes larger then the actual read bits
  * because some optimized bitstream readers read 32 or 64 bit at once and could read over the end
  * @param bit_size the size of the buffer in bits
+ *
+ * While GetBitContext stores the buffer size, for performance reasons you are
+ * responsible for checking for the buffer end yourself (take advantage of the padding)!
  */
 static inline void init_get_bits(GetBitContext *s,
                    const uint8_t *buffer, int bit_size)