Disregard this patch, turns out the parser needlessly warns. The whole
function simply checks if the parse offsets are sane but warns in case they
aren't even though it will continue scanning for other possible parse codes.
On 20 January 2016 at 11:37, Rostislav Pehlivanov <atomnu...@gmail.com>
wrote:
> The specifications use uint32_t and this fixes a number of warnings
> about invalid offsets of some files.
>
> Signed-off-by: Rostislav Pehlivanov <atomnu...@gmail.com>
> ---
> libavcodec/dirac_parser.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/libavcodec/dirac_parser.c b/libavcodec/dirac_parser.c
> index 1ca7e31..446299c 100644
> --- a/libavcodec/dirac_parser.c
> +++ b/libavcodec/dirac_parser.c
> @@ -92,8 +92,8 @@ static int find_frame_end(DiracParseContext *pc,
> }
>
> typedef struct DiracParseUnit {
> - int next_pu_offset;
> - int prev_pu_offset;
> + uint32_t next_pu_offset;
> + uint32_t prev_pu_offset;
> uint8_t pu_type;
> } DiracParseUnit;
>
> --
> 2.7.0.rc3.207.g0ac5344
>
>
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
http://ffmpeg.org/mailman/listinfo/ffmpeg-devel
