- 27 Jan, 2016 2 commits
-
-
James Almer authored
AVX2 support was introduced in Yasm 1.2.0 and NASM 2.10, and the oldest versions currently supported are Yasm 0.8.0 and NASM 2.03 Signed-off-by:
James Almer <jamrial@gmail.com> Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
James Almer authored
Needed to declare 32-byte long constants Signed-off-by:
James Almer <jamrial@gmail.com> Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
- 26 Jan, 2016 1 commit
-
-
Luca Barbato authored
Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
- 25 Jan, 2016 11 commits
-
-
Vittorio Giovara authored
-
Vittorio Giovara authored
-
Vittorio Giovara authored
-
Vittorio Giovara authored
-
Vittorio Giovara authored
Missing from be00ec83.
-
Luca Barbato authored
Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
And move the resource deallocation in stream_open failure path. Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
The name was misleading. Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
The structure is not video-specific. Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
It does not belong to the stream setup. Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
Luca Barbato authored
And refactor the code in preparation of the following patches. Signed-off-by:
Luca Barbato <lu_zero@gentoo.org>
-
- 24 Jan, 2016 2 commits
-
-
Anton Khirnov authored
Now all IO should go through the IO callbacks and be interceptable by the caller.
-
Anton Khirnov authored
Some (de)muxers open additional files beyond the main IO context. Currently, they call avio_open() directly, which prevents the caller from using custom IO for such streams. This commit adds callbacks to AVFormatContext that default to avio_open2()/avio_close(), but can be overridden by the caller. All muxers and demuxers using AVIO are switched to using those callbacks instead of calling avio_open()/avio_close() directly. (de)muxers that use the URLProtocol layer directly instead of AVIO remain unconverted for now. This should be fixed in later commits.
-
- 23 Jan, 2016 11 commits
-
-
Anton Khirnov authored
Introduced in 0e6c8532.
-
Geza Lore authored
Some debuggers/profilers use this metadata to determine which function a given instruction is in; without it they get can confused by local labels (if you haven't stripped those). On the other hand, some tools are still confused even with this metadata. e.g. this fixes `gdb`, but not `perf`. Currently only implemented for ELF. Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
Henrik Gramner authored
The REP_RET workaround is only needed on old AMD cpus, and the labels clutter up the symbol table and confuse debugging/profiling tools, so use EQU to create SHN_ABS symbols instead of creating local labels. Furthermore, skip the workaround completely in functions that definitely won't run on such cpus. Note that EQU is just creating a local label when using nasm instead of yasm. This is probably a bug, but at least it doesn't break anything. Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
Henrik Gramner authored
cpuflags is never undefined any more, it's set to 0 instead. Also fix an incorrect comment. Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
Henrik Gramner authored
Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
Henrik Gramner authored
When allocating stack space with a larger alignment than the known stack alignment a temporary register is used for storing the stack pointer. Ensure that this isn't one of the registers used for passing arguments. Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
Henrik Gramner authored
* Correctly handle FMA instructions with memory operands. * Print a warning if FMA instructions are used without the correct cpuflag. * Simplify the instantiation code. * Clarify documentation. Only the last operand in FMA3 instructions can be a memory operand. When converting FMA4 instructions to FMA3 instructions we can utilize the fact that multiply is a commutative operation and reorder operands if necessary to ensure that a memory operand is used only as the last operand. Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
Henrik Gramner authored
Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
Henrik Gramner authored
Makes it possible to use them in arithmetic expressions. Signed-off-by:
Anton Khirnov <anton@khirnov.net>
-
Anton Khirnov authored
The parameters in the docs are currently swapped.
-
Luca Barbato authored
-
- 22 Jan, 2016 1 commit
-
-
Martin Storsjö authored
This fixes crashes since 243df135. Signed-off-by:
Martin Storsjö <martin@martin.st>
-
- 21 Jan, 2016 12 commits
-
-
Vittorio Giovara authored
This option is only used by mpegvideoenc. It is a very codec-specific option, so deprecate the global variant. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This option is only used by mpegvideoenc. It is a very codec-specific options, so deprecate the global variant. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This options is only used by huffyuv, ffvhuv, jpegls, mjpeg, mpegvideoenc, png, utvideo. It is a very codec-specific options, so deprecate the global variant. Set proper limits to the maximum allowed values, and update utvideoenc tests to use the new option name. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
These options are only used by alac and flac. They are very codec-specific options, so deprecate the global variants. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This option is only used by mpegvideoenc and openh264. It is a very codec-specific option, so deprecate the global variant. The openh264 option is dropped altogether since it is just a fallback for -max_nal_size anyway. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This option is only used by mpeg2. It is a very codec-specific option, so deprecate the global variant. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This option is only used by ffv1 and ffvhuff. It is a very codec-specific option, so deprecate the global variant. Improve documentation a little. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This option is only used by mpegvideoenc, and xvid. It is a very codec-specific option, so deprecate the global variant. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This option is only used by mpegvideoenc, x264, xavs, and vpx. It is a very codec-specific option, so deprecate the global variant. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This option is only used by mpegvideoenc, x264, and xavs. It is a very codec-specific option, so deprecate the global variant. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
This option is only used by x264 and xavs. It is a very codec-specific option, so deprecate the global variant. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-
Vittorio Giovara authored
These options are only used by mpegvideoenc and vpx. They are very codec-specific options, so deprecate the global variants. Add an allowed value to the private options for frame_skip_cmp which seems to have been forgotten, but perfectly working. The libvpx frame dropping feature uses one of such option (frame_skip_threshold) without the other three. For this reason rename the option to something more consistent with the other libvpx variables. Signed-off-by:
Vittorio Giovara <vittorio.giovara@gmail.com>
-