On Thu, Oct 22, 2015 at 2:50 PM, Ganesh Ajjanagadde <gajja...@mit.edu> wrote:
> On Thu, Oct 22, 2015 at 2:45 PM, Hendrik Leppkes <h.lepp...@gmail.com> wrote:
>> On Thu, Oct 22, 2015 at 8:40 PM, Ganesh Ajjanagadde
>> <gajjanaga...@gmail.com> wrote:
>>> GCC (and Clang) have this useful warning that is not enabled by -Wall or
>>> -Wextra. This will ensure that issues like those fixed in
>>> 4da52e3630343e8d3a79aef2cafcb6bf0b71e8da
>>> will trigger warnings.
>>>
>>
>> I did get this warning on GCC 5.2, which is how I found it in the
>> first place. :)
>> Seems to be enabled by default here at least.
>
> Strange, I also run GCC 5.2 and it is not enabled by default, or even
> with "-Wall -Wextra -pedantic".
>
>>
>> Otherwise probably OK if its not enabled on other compilers that
>> understand such a flag.
>
> Will wait to see if there are issues with some less-used compilers.

In the absence of comments, and low probability of breakage
(check_cflags enables only when available), pushed.

>
>>
>> - Hendrik
>> _______________________________________________
>> 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

Reply via email to