I.e. input options to output files or vice versa.

Not all gcc configurations have an implementation of all the atomic
operations, and some gcc configurations have some atomic builtins
implemented but not all.

Thus check for the most essential function, whose presence should
indicate that all others are present as well, since it can be used
to implement all the other ones.
Signed-off-by: Martin Storsjö <martin@martin.st>

Signed-off-by: Anton Khirnov <anton@khirnov.net>

This makes them pass standalone compilation tests. Previously,
they included atomic.h which included themselves again, leading to
double definitions.
Signed-off-by: Martin Storsjö <martin@martin.st>

Fixes build without threads after
759001c5.

Signed-off-by: Martin Storsjö <martin@martin.st>

CC:libav-stable@libav.org

Returning 0 may result in an infinite loop in valid calling programs. A
decoder should never return 0 without producing any output.

CC:libav-stable@libav.org

Avoids an infinite loop in the calling programs with decoder not
consuming any input and not returning output.

CC:libav-stable@libav.org

Avoids an infinite loop in the calling programs with decoder not
consuming any input and not returning output.

CC:libav-stable@libav.org

CC:libav-stable@libav.org

When there is just 1 byte remanining in the buffer, nothing will be read
and the loop will continue forever. Check that there are at least 8
bytes, which are always read at the beginning.

CC:libav-stable@libav.org

The loop a few lines below the xan_unpack() call accesses up to
dec_size * 2 bytes into y_buffer, so dec_size must be limited to
buffer_size / 2.

CC:libav-stable@libav.org

The container does not store any timestamps and is CFR-only.

This allows us to test the slice threading code.

It got broken in 0f13cd31.

CC:libav-stable@libav.org

CC:libav-stable@libav.org

Its replacement is still not ready.

It is not used inside lavc anywhere and now it makes no sense to export
it.

Remove now unused cmdutils get_buffer() implementation.

It has been broken for over a year without anyone complaining or
noticing, thus proving that nobody ever uses it.

This should ensure that a valid channel layout is always set on a frame,
until a better solution is implemented.

This is the most that can be represented with the current channel layout
system. This limit should be raised/removed when a better system is
implemented.

This misfeature is most likely completely useless and conflicts with
removing the mpegvideo-specific fields from AVFrame. In the improbable
case it is actually useful, it should be reimplemented in a better way.

Deprecate AVFilterBuffer/AVFilterBufferRef and everything related to it
and use AVFrame instead.

Add AVBuffer-based reference counting API to it.

This field is private and should not be present in a public struct. It
is only used in DXVA with mpegvideo-based decoders currently.

This will allow us to avoid copying the packets in many cases.

This breaks ABI.