On Wed, Jul 22, 2015 at 10:56 PM, Ganesh Ajjanagadde <gajja...@mit.edu> wrote: > 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
Ticket above looks dead, and given their high bug volume, I doubt any one will be investigating it soon. Since there are only 2 instances remaining, both silencable with one line changes, I will submit patches for them unless someone objects. > >> _______________________________________________ >> 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