Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-10-11 Thread Ganesh Ajjanagadde
On Wed, Jul 22, 2015 at 10:56 PM, Ganesh Ajjanagadde wrote: > On Tue, Jul 21, 2015 at 10:46 PM, James Almer 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

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-07-22 Thread Ganesh Ajjanagadde
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

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-07-21 Thread Ronald S. Bultje
Hi, On Tue, Jul 21, 2015 at 10:07 PM, Ganesh Ajjanagadde gajja...@mit.edu wrote: On Tue, Jul 21, 2015 at 5:31 PM, Ganesh Ajjanagadde gajja...@mit.edu wrote: On Tue, Jul 21, 2015 at 5:14 PM, Michael Niedermayer mich...@niedermayer.cc wrote: On Thu, Jun 25, 2015 at 01:25:08AM -0300, James

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-07-21 Thread James Almer
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.

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-07-21 Thread Ganesh Ajjanagadde
On Tue, Jul 21, 2015 at 5:31 PM, Ganesh Ajjanagadde gajja...@mit.edu wrote: On Tue, Jul 21, 2015 at 5:14 PM, Michael Niedermayer mich...@niedermayer.cc wrote: On Thu, Jun 25, 2015 at 01:25:08AM -0300, James Almer wrote: On 04/06/15 6:55 PM, Ganesh Ajjanagadde wrote: I have created a small

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-07-21 Thread Ganesh Ajjanagadde
On Tue, Jul 21, 2015 at 5:14 PM, Michael Niedermayer mich...@niedermayer.cc wrote: On Thu, Jun 25, 2015 at 01:25:08AM -0300, James Almer wrote: On 04/06/15 6:55 PM, Ganesh Ajjanagadde wrote: I have created a small test case which gets at the heart of one of these spurious warnings, namely

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-07-21 Thread Michael Niedermayer
On Thu, Jun 25, 2015 at 01:25:08AM -0300, James Almer wrote: On 04/06/15 6:55 PM, Ganesh Ajjanagadde wrote: I have created a small test case which gets at the heart of one of these spurious warnings, namely the one for libavfilter/vf_swapuv.c. Here is the ticket on the GCC Bugzilla:

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-07-21 Thread Ganesh Ajjanagadde
On Tue, Jul 21, 2015 at 10:28 PM, Ronald S. Bultje rsbul...@gmail.com wrote: Hi, On Tue, Jul 21, 2015 at 10:07 PM, Ganesh Ajjanagadde gajja...@mit.edu wrote: On Tue, Jul 21, 2015 at 5:31 PM, Ganesh Ajjanagadde gajja...@mit.edu wrote: On Tue, Jul 21, 2015 at 5:14 PM, Michael Niedermayer

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-06-24 Thread James Almer
On 04/06/15 6:55 PM, Ganesh Ajjanagadde wrote: I have created a small test case which gets at the heart of one of these spurious warnings, namely the one for libavfilter/vf_swapuv.c. Here is the ticket on the GCC Bugzilla: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66422 Note that as

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-06-04 Thread Ganesh Ajjanagadde
I have created a small test case which gets at the heart of one of these spurious warnings, namely the one for libavfilter/vf_swapuv.c. Here is the ticket on the GCC Bugzilla: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66422 Note that as of the moment, -Warray-bounds appears quite broken on

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-06-04 Thread James Almer
On 04/06/15 10:08 AM, Ganesh Ajjanagadde wrote: On Thu, Jun 4, 2015 at 7:00 AM, Michael Niedermayer michae...@gmx.at wrote: On Wed, Jun 03, 2015 at 10:05:54PM -0400, Ganesh Ajjanagadde wrote: While compiling ffmpeg, I noticed a bunch of -Warray-bounds warnings. I think it would be great if

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-06-04 Thread Hendrik Leppkes
On Thu, Jun 4, 2015 at 4:05 AM, Ganesh Ajjanagadde gajja...@mit.edu wrote: While compiling ffmpeg, I noticed a bunch of -Warray-bounds warnings. I think it would be great if ffmpeg could be built warning-free, and -Warray-bounds seems to be one of the biggest culprits. Nevertheless,

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-06-04 Thread Nicolas George
Le quintidi 15 prairial, an CCXXIII, Ganesh Ajjanagadde a écrit : 1. using av_assert0() to ensure that array access remains in bounds in these few cases. This could lead to performance hit. Using av_assert1() or av_assert2() will yield a performance hit, but only when enabled in development

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-06-04 Thread Carl Eugen Hoyos
Ganesh Ajjanagadde gajjanag at mit.edu writes: I think it would be great if ffmpeg could be built warning-free I am sure nobody here is against compiling FFmpeg without warnings but I wonder if it is possible and if it is worth the effort. Which option do the devs here prefer? Not

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-06-04 Thread Michael Niedermayer
On Wed, Jun 03, 2015 at 10:05:54PM -0400, Ganesh Ajjanagadde wrote: While compiling ffmpeg, I noticed a bunch of -Warray-bounds warnings. I think it would be great if ffmpeg could be built warning-free, and -Warray-bounds seems to be one of the biggest culprits. Nevertheless, -Warray-bounds

Re: [FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-06-04 Thread Ganesh Ajjanagadde
On Thu, Jun 4, 2015 at 7:00 AM, Michael Niedermayer michae...@gmx.at wrote: On Wed, Jun 03, 2015 at 10:05:54PM -0400, Ganesh Ajjanagadde wrote: While compiling ffmpeg, I noticed a bunch of -Warray-bounds warnings. I think it would be great if ffmpeg could be built warning-free, and

[FFmpeg-devel] GCC 5.1 warning: -Warray-bounds

2015-06-03 Thread Ganesh Ajjanagadde
While compiling ffmpeg, I noticed a bunch of -Warray-bounds warnings. I think it would be great if ffmpeg could be built warning-free, and -Warray-bounds seems to be one of the biggest culprits. Nevertheless, -Warray-bounds is quite useful in most cases. I currently see 2 possible improvements: 1.