The value is used to calculate output LSP curve and a division by zero
and out of array accesses would occur.

CVE-2013-0894

CC: libav-stable@libav.org
Reported-by: Dale Curtis <dalecurtis@chromium.org>
Found-by: inferno@chromium.org
Signed-off-by: Michael Niedermayer <michaelni@gmx.at>
Signed-off-by: Luca Barbato <lu_zero@gentoo.org>

This cuts some lines from the script as well as the output and
simplifies maintenance.
Signed-off-by: Mans Rullgard <mans@mansr.com>

Signed-off-by: Mans Rullgard <mans@mansr.com>

Avoids an option name conflict with libavcodec, which is needed in order
to work properly with avconv.

Damaged frames can lead to a mismatch, which can cause a segfault
due to using an incorrect channel mapping.

CC:libav-stable@libav.org

The enabled hwaccels are listed later anyway.
Signed-off-by: Mans Rullgard <mans@mansr.com>

While we do not use Automake in libav, this allows our config to be
used more globally without introducing unwanted breakage.

The init functions marked as av_cold have to be executed in any case,
so there is no gain from trying to mark paths leading to such functions
as unlikely.

This also allows libx264 to modify its i_qfactor value
when using the "-tune" setting. Previously it had a static
value of 1.25
Signed-off-by: Anton Khirnov <anton@khirnov.net>

CC:libav-stable@libav.org

Avoids crashes with corrupted files.

CC:libav-stable@libav.org

CC:libav-stable@libav.org

CC:libav-stable@libav.org

When byte_run is 0, pixel_countdown is not touched and the loop will run
forever.

CC:libav-stable@libav.org

CC:libav-stable@libav.org

range == 0 happens with corrupted files

CC:libav-stable@libav.org

CC:libav-stable@libav.org

CC:libav-stable@libav.org

This fixes crashes in chromium on win64 on machines with AVX
(crashes that apparently aren't triggered by fate).
Signed-off-by: Martin Storsjö <martin@martin.st>

Signed-off-by: Diego Biurrun <diego@biurrun.de>

This gets rid of a number of warnings about casts discarding
qualifiers from the pointer target, present since 7ebfb466.
Signed-off-by: Martin Storsjö <martin@martin.st>

Instead, only extend edges on-demand when the motion vector actually
crosses the visible decoded area using ff_emulated_edge_mc(). This
changes decoding time for cathedral from 8.722sec to 8.706sec, i.e.
0.2% faster overall. More generally (VP8 uses this also), low-motion
content gets significant speed improvements, whereas high-motion content
tends to decode in approximately the same time.
Signed-off-by: Martin Storsjö <martin@martin.st>