- 12 1月, 2016 4 次提交
-
-
由 Clément Bœsch 提交于
Signed-off-by: NVittorio Giovara <vittorio.giovara@gmail.com>
-
由 Clément Bœsch 提交于
Signed-off-by: NVittorio Giovara <vittorio.giovara@gmail.com>
-
由 Alexandra Hájková 提交于
Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
由 Luca Barbato 提交于
-
- 09 1月, 2016 1 次提交
-
-
由 Martin Storsjö 提交于
This fixes builds with --disable-vfp. Checking for the armv6 cpu flag is incorrect, since vfpv2 isn't armv6 specific. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
- 07 1月, 2016 8 次提交
-
-
由 Martin Storsjö 提交于
This is disabled on iOS, since iOS uses a slightly different ABI for vararg parameters. Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Martin Storsjö 提交于
Use two separate functions, depending on whether VFP/NEON is available. This is set to require armv5te - it uses blx, which is only available since armv5t, but we don't have a separate configure item for that. (It also uses ldrd, which requires armv5te, but this could be avoided if necessary.) Signed-off-by: NMartin Storsjö <martin@martin.st>
-
由 Andreas Cadhalpun 提交于
The previous check only caught sizes from -AV_INPUT_BUFFER_PADDING_SIZE to -1. This fixes ubsan runtime error: signed integer overflow: 2147483647 + 32 cannot be represented in type 'int' Signed-off-by: NAndreas Cadhalpun <Andreas.Cadhalpun@googlemail.com> Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
由 Alexandra Hájková 提交于
Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
由 Andreas Cadhalpun 提交于
Both avio_skip and detect_unknown_subobject use int64_t for the size parameter. This fixes a segmentation fault due to infinite recursion. Signed-off-by: NAndreas Cadhalpun <Andreas.Cadhalpun@googlemail.com> Signed-off-by: NAlexandra Hájková <alexandra.khirnova@gmail.com> Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
由 Andreas Cadhalpun 提交于
Otherwise invalid values are used unchecked in the next run. This can cause NULL pointer dereferencing. Signed-off-by: NAndreas Cadhalpun <Andreas.Cadhalpun@googlemail.com> Signed-off-by: NAlexandra Hájková <alexandra.khirnova@gmail.com> Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
由 Anton Khirnov 提交于
This makes sure all the frames are returned at the end. Found-By: NMaxym Dmytrychenko <maxym.dmytrychenko@intel.com>
-
由 Maxym Dmytrychenko 提交于
Same as what is done in 3b6473b4. Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
- 04 1月, 2016 4 次提交
-
-
由 Luca Barbato 提交于
EAGAIN is already managed in poll_filters(). Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
由 Luca Barbato 提交于
Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
-
- 01 1月, 2016 3 次提交
-
-
由 Maxym Dmytrychenko 提交于
Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
由 Maxym Dmytrychenko 提交于
Use 8 B-frames and modify the GOP size to be a multiple of the B-frame count. Signed-off-by: NAnton Khirnov <anton@khirnov.net>
-
由 Anton Khirnov 提交于
Before 741b494f, when the reference list modification description was invalid, the code would substitute the corresponding reference from the initial ("default") reference list. After that commit, it will just return an error. Since there are apparently invalid samples in the wild that used to play fine with the old code, it is a good idea to re-add some sort of error resilience here. So, when the reference list modification results in a missing frame, substitute a previous reference frame for it. The relevant sample again decodes fine with the same output as previously.
-
- 31 12月, 2015 1 次提交
-
-
由 Alexandra Hájková 提交于
Signed-off-by: NJanne Grunau <janne-libav@jannau.net>
-
- 30 12月, 2015 1 次提交
-
-
由 Janne Grunau 提交于
Intel's Instruction Set Reference (as of September 2015) clearly states that cvtpi2ps switches to MMX state. Actual CPUs do not switch if the source is a memory location. The Instruction Set Reference from 1999 (Order Number 243191) describes this behaviour but all later versions I've seen have make no distinction whether MMX registers or memory is used as source. The documentation for the matching SSE2 instruction to convert to double (cvtpi2pd) was fixed (see the valgrind bug https://bugs.kde.org/show_bug.cgi?id=210264). It will take time to get a clarification and fixes in place. In the meantime it makes sense to change ff_int32_to_float_fmul_scalar_sse to be correct according to the documentation. The vast majority of users will have SSE2 so a change to the SSE version has little effect. Fixes fate-checkasm on x86 valgrind targets. Valgrind 'bug' reported as https://bugs.kde.org/show_bug.cgi?id=357059
-
- 29 12月, 2015 2 次提交
-
-
由 Janne Grunau 提交于
Check the full FPU tag word instead of only the lower half and simplify the comparison. Use upper-case function base name as macro name to instantiate both checked_call variants.
-
由 Janne Grunau 提交于
This reverts commit 5dfe4eda.
-
- 26 12月, 2015 2 次提交
-
-
由 Diego Biurrun 提交于
-
由 Diego Biurrun 提交于
-
- 24 12月, 2015 1 次提交
-
-
由 Alexandra Hájková 提交于
They were superseded with their integer equivalents. Rename integer decode_hf to decode_hf.
-
- 23 12月, 2015 2 次提交
-
-
由 Alexandra Hájková 提交于
The DCA core decoder converts integer coefficients read from the bitstream to floats just after reading them (along with dequantization). All the other steps of the audio reconstruction are done with floats which makes the output for the DTS lossless extension (XLL) actually lossy. This patch changes the DCA core to work with integer coefficients until QMF. At this point the integer coefficients are converted to floats. The coefficients for the LFE channel (lfe_data) are not touched. This is the first step for the really lossless XLL decoding.
-
由 Alexandra Hájková 提交于
They will be used by the integer core decoder.
-
- 22 12月, 2015 5 次提交
-
-
由 Janne Grunau 提交于
-
由 Janne Grunau 提交于
-
由 Janne Grunau 提交于
-
由 Janne Grunau 提交于
-
由 Janne Grunau 提交于
Not every asm routine is expected clear the MMX state after returning. It is however a requisite for testing floating point code in checkasm. Annotate functions requiring cleanup with declare_func_emms() and issue emms after the call. The remaining functions are checked for having a cleared MMX state after return.
-
- 21 12月, 2015 1 次提交
-
-
由 Janne Grunau 提交于
Fix related register order issue in ff_h264_idct_add_neon. Found-by: Nzjh8890 <243186085@qq.com>
-
- 17 12月, 2015 2 次提交
-
-
由 Andreas Cadhalpun 提交于
This macro unconditionally used out[-1], which causes an out of bounds read, if out is the very beginning of the buffer. Signed-off-by: NAndreas Cadhalpun <Andreas.Cadhalpun@googlemail.com> Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
由 Andreas Cadhalpun 提交于
Due to this typo max_center can be too large, causing nlsf to be set to too large values, which in turn can cause nlsf[i - 1] + min_delta[i] to overflow to a negative value, which is not allowed for nlsf and can cause an out of bounds read in silk_lsf2lpc. Signed-off-by: NAndreas Cadhalpun <Andreas.Cadhalpun@googlemail.com> Signed-off-by: NLuca Barbato <lu_zero@gentoo.org>
-
- 14 12月, 2015 3 次提交
-
-
由 Janne Grunau 提交于
Quite a bit faster than int32_to_float_fmul_array8_c calling ff_int32_to_float_fmul_scalar_neon through FmtConvertContext. Number of cycles per int32_to_float_fmul_array8 call while decoding padded.dts on exynos5422: before after change cortex-a7: 1270 951 -25% cortex-a15: 434 285 -34% checkasm --bench cycle counts: cortex-a15 cortex-a7 int32_to_float_fmul_array8_c: 1730.4 4384.5 int32_to_float_fmul_array8_neon_c: 571.5 1694.3 int32_to_float_fmul_array8_neon: 374.0 1448.8 Interesting are the differences between int32_to_float_fmul_array8_neon_c and int32_to_float_fmul_array8_neon. The former is current behaviour of calling ff_int32_to_float_fmul_scalar_neon repeatedly from the c function, The raw numbers differ since checkasm uses different lengths than the dca decoder.
-
由 Janne Grunau 提交于
3% faster dts decoding on a cortex-a57. cortex-a57 cortex-a53 int32_to_float_fmul_array8_c: 1270.9 4475.6 int32_to_float_fmul_array8_neon: 328.6 569.2 int32_to_float_fmul_scalar_c: 928.5 4119.6 int32_to_float_fmul_scalar_neon: 309.1 524.1
-
由 Janne Grunau 提交于
~25% faster dts decoding overall. The checkasm CPU cycles numbers are not that useful since synth_filter_float() calls FFTContext.imdct_half(). cortex-a57 cortex-a53 synth_filter_float_c: 1866.2 3490.9 synth_filter_float_neon: 915.0 1531.5 With fftc.imdct_half forced to imdct_half_neon: cortex-a57 cortex-a53 synth_filter_float_c: 1718.4 3025.3 synth_filter_float_neon: 926.2 1530.1
-