On Tue, Jul 21, 2015 at 10:46 PM, James Almer <jamr...@gmail.com> wrote: > 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.
I have filed a new bugreport for the issue in libavcodec/dca_xll.c: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66974 > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-devel _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-devel