- 18 7月, 2016 1 次提交
-
-
由 Martin Storsjö 提交于
These bits are set by exceptions in NEON instructions. Also print the differing bits when FPSCR is clobbered, and use bic instead of lsl, for clearing the topmost bits. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 17 7月, 2016 2 次提交
-
-
由 Janne Grunau 提交于
Fixes AS error on non NEON builds introduced in 71a04721. Also set the fpu directly to vfp in checkasm.S to cause build errors on NEON builds.
-
由 Martin Storsjö 提交于
Each const block needs to be terminated by one endconst invocation so either call endconst after each, or just declare plain labels to the later strings. This fixes errors such as this, on some binutils versions: checkasm.S:38: Error: Macro `endconst' was already defined Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 16 7月, 2016 4 次提交
-
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
They are internal symbols that should not be exported. based on a patch by Andreas Cadhalpun <Andreas.Cadhalpun@googlemail.com> Signed-off-by: NDiego Biurrun <diego@biurrun.de>
-
由 Andreas Cadhalpun 提交于
It is an internal swscale symbol and thus should not be exported. Signed-off-by: NAndreas Cadhalpun <Andreas.Cadhalpun@googlemail.com> Signed-off-by: NDiego Biurrun <diego@biurrun.de>
-
由 Janne Grunau 提交于
-
- 15 7月, 2016 13 次提交
-
-
由 Hendrik Leppkes 提交于
Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
由 Anton Khirnov 提交于
-
由 Anton Khirnov 提交于
-
由 Anton Khirnov 提交于
Since we only know whether a NAL unit corresponds to a new field after parsing the slice header, this requires reorganizing the calls to slice parsing, per-slice/field/frame init and actual decoding. In the previous code, the function for slice header decoding also immediately started a new field/frame as necessary, so any slices already queued for decoding would no longer be decodable. After this patch, we first parse the slice header, and if we determine that a new field needs to be started we decode all the queued slices.
-
由 Anton Khirnov 提交于
This function's purpose is not very well defined. Currently it does two (only marginally related) things: selecting the next output frame and calling ff_thread_finish_setup() for frame threading. The first of those more properly belongs under field_start(), while the second can be called directly from decode_nal_units().
-
由 Anton Khirnov 提交于
-
由 Anton Khirnov 提交于
-
由 Anton Khirnov 提交于
-
由 Martin Storsjö 提交于
Also set FF_CODEC_CAP_INIT_THREADSAFE while adding internal capabilities. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Previously they returned the default AVERROR_UNKNOWN. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Matthieu Bouron 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 14 7月, 2016 7 次提交
-
-
由 Vittorio Giovara 提交于
The input packet is already unref'd by the calling function.
-
由 Vittorio Giovara 提交于
See 17c99b61. Signed-off-by: NVittorio Giovara <vittorio.giovara@gmail.com>
-
由 Vittorio Giovara 提交于
-
由 Vittorio Giovara 提交于
-
由 Janne Grunau 提交于
The stack used by checkasm_checked_call_vfp was a multiple of 4 when the checked function is called. AAPCS requires a double word (8 byte) aligned stack public interfaces. Since both calls are public interfaces the stack is misaligned when the checked is called. Might fix the SIGBUS error in the armv7-linux-clang-3.7 fate config.
-
由 Janne Grunau 提交于
Fixes "Use of uninitialised value" valgrind warnings in checkasm.
-
由 Janne Grunau 提交于
Fixes a regression in ca2f19b9 with some mov/mp4 files. The files have several NAL units in the supposed single NAL unit after the size field. Annex B start code prefixes are used to separate them. The first NAL unit is correctly parsed but the buffer does not point to the next size field. Instead semi random data (it seems to be the rbsp_stop_one_bit and the start code prefix) is then parsed as length and will exceed the remaining length of the buffer. Patch based on the code in h264's decode_nal_units() and a similar patch by Hendrik Leppkes in FFmpeg (a9bb4cf8). Bug-Id: ffmpeg/trac5529 Reported-By: Vittorio Giovara
-
- 11 7月, 2016 2 次提交
-
-
由 Anton Khirnov 提交于
Currently, SPS.mb_height is actually what the spec calls PicHeightInMapUnits, which is half the frame height when interlacing is allowed. Calling this 'mb_height' is quite confusing, and there are at least two associated bugs where this field is treated as the actual frame height - in the h264 parser and in the code computing maximum reordering buffer size for a given level. Fix those issues (and avoid possible future ones) by exporting the real frame height in this field.
-
由 Steve Lhomme 提交于
also fixes a deadlock found by Денис Кулаков <kudesnik33ra@gmail.com> Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
- 10 7月, 2016 6 次提交
-
-
由 Martin Storsjö 提交于
This comment isn't true, the height can be different from the width for these functions (which is why the height is passed as a parameter to them). Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Janne Grunau 提交于
Should fix the SIGBUS in the armv7-linux-clang-3.7 fate target.
-
由 Janne Grunau 提交于
-
由 Janne Grunau 提交于
GNU as evaluates true as '-1' while Apple's variant and llvm's internal assembler evaluate it as '1'. The best way to avoid this madness is to eliminate boolean expressions instead of trying to fix it with preprocessor directives. Use a direct formula to calculate the required temporary space on the stack in ff_put_vp8_{epel,bilin}{4,8,16}_h[246]v[246]_armv6(). Fixes a checkasm segfault in vp8dsp.mc when using llvm's internal assembler for a non-Apple target.
-
由 Janne Grunau 提交于
Unescaped literal left braces are deprecated and a warning was added in Perl 5.22.
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 08 7月, 2016 2 次提交
-
-
由 Martin Storsjö 提交于
When writing a fragmented file, we by default write an index pointing to all the fragments at the end of the file. This causes constantly increasing memory usage during the muxing. For live streams, the index might not be useful at all. A similar fragment index is written (but at the start of the file) if the global_sidx flag is set. If ism_lookahead is set, we need to keep data about the last ism_lookahead+1 fragments. If no fragment index is to be written, we don't need to store information about all fragments, avoiding increasing the memory consumption linearly with the muxing runtime. This fixes out of memory situations with long live mp4 streams. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
The tests are inspired by similar tests for vp9 by Ronald Bultje. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 07 7月, 2016 2 次提交
-
-
由 Martin Storsjö 提交于
Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Index 0 is w=16, 1 is wd=8, 2 is wd=4. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 03 7月, 2016 1 次提交
-
-
由 Anton Khirnov 提交于
The allocated frame size may be larger than the coded dimensions.
-