From db4903f4e4b553b72059ed407b012aca6769b8ea Mon Sep 17 00:00:00 2001 From: Michael Niedermayer Date: Sat, 13 Oct 2012 01:47:31 +0200 Subject: [PATCH] ffv1: avoid checking a double for equality if 0.0 != 0.0 a out of array read would occur, equal checks with floating point may behave in such odd ways, though this is very unlikely in a real implementation of a compiler Fixes: CID718936 Signed-off-by: Michael Niedermayer (cherry picked from commit 54b2d317ed99622efa07b10aca217e1a083105d9) Signed-off-by: Michael Niedermayer --- libavcodec/ffv1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/libavcodec/ffv1.c b/libavcodec/ffv1.c index c3034d326c..4d3a52887c 100644 --- a/libavcodec/ffv1.c +++ b/libavcodec/ffv1.c @@ -255,7 +255,7 @@ static void find_best_state(uint8_t best_state[256][256], const uint8_t one_stat occ[j]=1.0; for(k=0; k<256; k++){ double newocc[256]={0}; - for(m=0; m<256; m++){ + for(m=1; m<256; m++){ if(occ[m]){ len -=occ[m]*( p *l2tab[ m] + (1-p)*l2tab[256-m]);