New submission from sera <ser...@bluewin.ch>:

ffmpeg git-cf9af0c, default configuration

As of -O2 gcc use the aliasing rules to optimize. Almost everyone is using -O2.
So this may lead to random runtime behavior on a lot of machines. Here a list of
gcc complaints:

 * libavcodec/dsputil.c:3681: warning: dereferencing type-punned pointer will
break strict-aliasing rules
 * libavcodec/dsputil.c:3746: warning: dereferencing type-punned pointer will
break strict-aliasing rules
 * libavcodec/dsputil.c:3763: warning: dereferencing type-punned pointer will
break strict-aliasing rules
 * libavcodec/dsputil.c:3764: warning: dereferencing type-punned pointer will
break strict-aliasing rules
 * libavcodec/dsputil.c:3789: warning: dereferencing type-punned pointer will
break strict-aliasing rules
 * libavcodec/dsputil.c:3867: warning: dereferencing type-punned pointer will
break strict-aliasing rules
 * libavcodec/eatgq.c:229: warning: dereferencing type-punned pointer will break
strict-aliasing rules
 * libavcodec/h264.c:6215: warning: dereferencing type-punned pointer will break
strict-aliasing rules
 * libavcodec/svq3.c:869: warning: dereferencing type-punned pointer will break
strict-aliasing rules
 * libavcodec/x86/fdct_mmx.c:539: warning: dereferencing type-punned pointer
will break strict-aliasing rules
 * libavcodec/x86/fdct_mmx.c:557: warning: dereferencing type-punned pointer
will break strict-aliasing rules
 * libavcodec/x86/fdct_mmx.c:575: warning: dereferencing type-punned pointer
will break strict-aliasing rules
 * libavcodec/x86/simple_idct_mmx.c:214: warning: dereferencing type-punned
pointer will break strict-aliasing rules


And two other security related gcc complaints:
 * libavformat/mxfenc.c:1409: warning: implicit declaration of function
'ff_interleave_add_packet'
 * libavformat/oggenc.c:225: warning: implicit declaration of function
'ff_interleave_add_packet'

----------
messages: 4178
priority: normal
status: new
substatus: new
title: type-punned pointers
type: bug

____________________________________________________
FFmpeg issue tracker <ffmpeg_iss...@live.polito.it>
<https://roundup.ffmpeg.org/roundup/ffmpeg/issue823>
____________________________________________________

Reply via email to