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

[191919]

So there are another 2 places where uninitialized values are used?

I am not sure about where because I am using valgrind on Leopard.

2009/3/4 Jason Garrett-Glaser <darkshikari at gmail.com>

> 2009/3/3 191919 <191919 at gmail.com>:
> > ==493== Conditional jump or move depends on uninitialised value(s)
> > ==493==    at 0x47AA07: x264_me_search_ref (in /usr/local/bin/ffmpeg)
> > ==493==
> > ==493== Conditional jump or move depends on uninitialised value(s)
> > ==493==    at 0x47B3E1: x264_me_search_ref (in /usr/local/bin/ffmpeg)
> >
> >  164     int omx, omy, pmx, pmy;
> > ...
> >  239             if( (bmx == omx) & (bmy == omy) )
> >  240                 break;
> >
> > omx and omy are not initialized.
>
> 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 );\
> }
>
> Dark Shikari
> _______________________________________________
> x264-devel mailing list
> x264-devel at videolan.org
> http://mailman.videolan.org/listinfo/x264-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x264-devel/attachments/20090304/273d2035/attachment.htm>