[x264-devel] Re: Memory leak detected using Valgrind

[Bill May]

Mathieu Monnier wrote:
>  > I can't figure a way to backtrace - it's most likely in the nasm code.
>  > I tried compiling with out nasm, but it didn't compile - looked for
>  > altivec.h.
> 
> Try to revert to rev 179 ( before the patches converting gcc-inline to 
> nasm ), to see if Valgrind still complains. The half pixel interpolation 
> uses unitialized pixels because results obtained with these pixels will 
> be later replaced by padding, if i'm not mistaken.

Hi, Mathieu,

I just tried that release - it doesn't have the same error.

Bill

-- 
This is the x264-devel mailing-list
To unsubscribe, go to: http://developers.videolan.org/lists.html