[x264-devel] Some valgrind warnings on uninitialized variables in me.c

[Mathieu Monnier]

> Well, you know, except for the part where they are?
> 
> #define DIA1_ITER( mx, my )\
> {\
>     omx = mx; omy = my;\
>     COST_MV_X4( 0,-1, 0,1, -1,0, 1,0 );\
> }

That in itself doesn't prove anything. Valgrind wouldn't report an error 
here if mx or my weren't initialized, but will report an error when a 
conditionnal jump is done using those uninitialized values.

ie :

Int a;
Int b = a; // fine
Int c = b; // fine
if (c)     // error for valgrind
    ...