On 04/27/2013 03:10 PM, Diego Biurrun wrote:
> libavcodec/h264_refs.c:788:15: warning: 'i' may be used uninitialized in this
> function [-Wuninitialized]
> ---
> libavcodec/h264_refs.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/libavcodec/h264_refs.c b/libavcodec/h264_refs.c
> index c965033..360cef4 100644
> --- a/libavcodec/h264_refs.c
> +++ b/libavcodec/h264_refs.c
> @@ -782,9 +782,9 @@ int ff_h264_decode_ref_pic_marking(H264Context *h,
> GetBitContext *gb,
>
> if (first_slice && mmco_index != -1) {
> h->mmco_index = mmco_index;
> - } else if (!first_slice && mmco_index >= 0 &&
> - (mmco_index != h->mmco_index ||
> - (i = check_opcodes(h->mmco, mmco_temp, mmco_index)))) {
> + } else if ((i = check_opcodes(h->mmco, mmco_temp, mmco_index)) ||
> + !first_slice && mmco_index >= 0 &&
> + mmco_index != h->mmco_index) {
> av_log(h->avctx, AV_LOG_ERROR,
> "Inconsistent MMCO state between slices [%d, %d, %d]\n",
> mmco_index, h->mmco_index, i);
what happens to check_opcodes when mmc_index is negative?
lu
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
