On 21/07/15 11:43 PM, Ganesh Ajjanagadde wrote: > or try to work upstream with GCC to remove these spurious warnings.
If it can be fixed upstream then that's certainly the best option. For all we know new code we add in the future may trigger this bug again. _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
