- 25 6月, 2017 11 次提交
-
-
由 Michael Niedermayer 提交于
Fixes: runtime error: left shift of 1965559808 by 4 places cannot be represented in type 'int' Fixes: 2333/clusterfuzz-testcase-minimized-5223935677300736 Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpegReviewed-by: NPaul B Mahol <onemda@gmail.com> Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>
-
由 Paul B Mahol 提交于
Its been deprecated for over 3 years. Signed-off-by: NPaul B Mahol <onemda@gmail.com>
-
由 Paul B Mahol 提交于
Signed-off-by: NPaul B Mahol <onemda@gmail.com>
-
由 Paul B Mahol 提交于
Signed-off-by: NPaul B Mahol <onemda@gmail.com>
-
由 Marton Balint 提交于
Buffering more than one packet can be a huge performance improvement for encoding files with small packets (e.g. wav) over SMB/CIFS. Acked-by: NMichael Niedermayer <michael@niedermayer.cc> Signed-off-by: NMarton Balint <cus@passwd.hu>
-
由 Marton Balint 提交于
If flushing is not disabled, then mux.c will signal the end of the packets with an AVIO_DATA_MARKER_FLUSH_POINT, and aviobuf will be able to decide to flush or not based on the preferred minimum packet size set by the used protocol. Reviewed-by: NMichael Niedermayer <michael@niedermayer.cc> Signed-off-by: NMarton Balint <cus@passwd.hu>
-
由 Marton Balint 提交于
Reviewed-by: NMichael Niedermayer <michael@niedermayer.cc> Signed-off-by: NMarton Balint <cus@passwd.hu>
-
由 Marton Balint 提交于
This patch makes aviobuf work more like traditinal file IO, which is how people think about it. For example, in the past, aviobuf only flushed buffers until the current buffer position, even if more data was written to it previously, and a backward seek was used to reposition the IO context. From now, aviobuf will keep track of the written data, so no explicit seek will be required till the end of the buffer, or till the end of file before flushing. This fixes at least one regression, fate-vsynth3-flv was broken if flush_packets option was set to false, an explicit seek was removed in 4e3cc4bd. Also from now on, if a forward seek in the write buffer were to cause a gap between the already written data and the new file position, a flush will happen. The must_flush varable is also removed, which might have caused needless flushes with multiple seeks whithin the write buffer. Since we know the amount of data written to it, we will know when to flush. Signed-off-by: NMarton Balint <cus@passwd.hu>
-
由 Mark Thompson 提交于
(cherry picked from commit 41dda860)
-
由 Mark Thompson 提交于
(cherry picked from commit 0fd91e4b)
-
由 Mark Thompson 提交于
Takes a raw input stream containing frames with correct timestamps but possibly out of order and inserts additional show-existing-frame packets to correct the ordering. (cherry picked from commit 34e051d1) (cherry picked from commit b43b95f4) Also converted from bitstream to get_bits.
-
- 24 6月, 2017 10 次提交
-
-
由 Mark Thompson 提交于
Before this, output bitstream filters would never see EOF and therefore would not be able to flush any delayed packets. (cherry picked from commit f64d1100)
-
由 Michael Niedermayer 提交于
Fixes: runtime error: shift exponent -1 is negative Fixes: 2338/clusterfuzz-testcase-minimized-5153426541379584 Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpegSigned-off-by: NMichael Niedermayer <michael@niedermayer.cc>
-
由 Ronald S. Bultje 提交于
-
由 Paul B Mahol 提交于
Signed-off-by: NPaul B Mahol <onemda@gmail.com>
-
由 James Almer 提交于
<@jamrial> durandal_1707: 04aa09c4 broke fate-lavf-ffm and fate-lavf-mxf <@durandal_1707> how so? <@jamrial> one byte changes <@durandal_1707> jamrial: just update checksums <@jamrial> durandal_1707: but why did they change at all? the commit you reverted didn't affect them <@jamrial> why does reverting it affect these tests? <@jamrial> i don't think updating the checksum without knowing what changed is a good idea <@durandal_1707> jamrial: the lavfi core is in weird state after removal of recursive code <@durandal_1707> jamrial: the change is that older ones would get progressive flag set and new one doesnt <@jamrial> alright
-
由 James Almer 提交于
Fixes compilation with old yasm
-
由 Reino17 提交于
Signed-off-by: NMichael Bradshaw <mjbshaw@google.com>
-
由 James Almer 提交于
-
由 Rostislav Pehlivanov 提交于
c: 1802 decicycles in fft15,16774635 runs, 2581 skips avx: 865 decicycles in fft15,16776378 runs, 838 skips Signed-off-by: NRostislav Pehlivanov <atomnuker@gmail.com>
-
由 James Almer 提交于
If the first assembler to be probed is an old nasm build, X86ASM_DEPFLAGS will be set and remain so after yasm is ultimately used as fallback. This results in yasm being called with said nasm specific flags and failing during actual object assembly but not with configure sanity checks. Regression since 5cae5a1dReviewed-by: NMichael Niedermayer <michael@niedermayer.cc> Signed-off-by: NJames Almer <jamrial@gmail.com>
-
- 23 6月, 2017 9 次提交
-
-
由 Paul B Mahol 提交于
Fixes framesync filters with shortest option enabled. This reverts commit 0ff5567a.
-
由 jerett 提交于
Checks for NULL before using object. Signed-off-by: NRick Kern <kernrj@gmail.com>
-
由 jerett 提交于
Signed-off-by: NRick Kern <kernrj@gmail.com>
-
由 Jun Zhao 提交于
set_ue_golomb just support 2^16 - 2 at most, becase this function call put_bits, and put_bits just support write up to 31 bits, when write 32 bit in put_bits, it's will overwrite the bit buffer, and the default assert level is 0, the av_assert2(n <= 31 && value < (1U << n)) in put_bits can not be trigger runtime. Signed-off-by: NJun Zhao <jun.zhao@intel.com> Signed-off-by: NMichael Niedermayer <michael@niedermayer.cc>
-
由 Michael Niedermayer 提交于
Fixes: runtime error: signed integer overflow: 227511904 + 1964113935 cannot be represented in type 'int' Fixes: 2331/clusterfuzz-testcase-minimized-6182185830711296 Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpegSigned-off-by: NMichael Niedermayer <michael@niedermayer.cc>
-
由 Michael Niedermayer 提交于
Fixes: runtime error: signed integer overflow: 512 + 2147483146 cannot be represented in type 'int' Fixes: 2314/clusterfuzz-testcase-minimized-4519333877252096 Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpegSigned-off-by: NMichael Niedermayer <michael@niedermayer.cc>
-
由 Michael Niedermayer 提交于
Fixes: runtime error: signed integer overflow: 538976288 * 32 cannot be represented in type 'int' Fixes: 2310/clusterfuzz-testcase-minimized-4534784887881728 Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpegSigned-off-by: NMichael Niedermayer <michael@niedermayer.cc>
-
由 Rostislav Pehlivanov 提交于
Signed-off-by: NRostislav Pehlivanov <atomnuker@gmail.com>
-
由 James Almer 提交于
Fixes a NULL pointer derefence when ogg_init() returns a failure and a stream's private data was not yet allocated. This is a regression since 3c5a53cdReviewed-by: NPaul B Mahol <onemda@gmail.com> Signed-off-by: NJames Almer <jamrial@gmail.com>
-
- 22 6月, 2017 10 次提交
-
-
由 Matthieu Bouron 提交于
Avoids overriding the v0 register (which containins the result of the tested function) in checkasm_call_checked.
-
由 Michael Niedermayer 提交于
Fixes: runtime error: shift exponent 32 is too large for 32-bit type 'int' Fixes: 2306/clusterfuzz-testcase-minimized-5002997392211968 Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpegSigned-off-by: NMichael Niedermayer <michael@niedermayer.cc>
-
由 Michael Niedermayer 提交于
Fixes: runtime error: left shift of negative value -1 Fixes: 2303/clusterfuzz-testcase-minimized-5529675273076736 Found-by: continuous fuzzing process https://github.com/google/oss-fuzz/tree/master/projects/ffmpegSigned-off-by: NMichael Niedermayer <michael@niedermayer.cc>
-
由 Diego Biurrun 提交于
This allows for more graceful fallback from NASM to Yasm if the available NASM version is too old. (Cherry-picked from libav commit adfd7892) Signed-off-by: NJames Almer <jamrial@gmail.com>
-
由 Diego Biurrun 提交于
NASM is more actively maintained and permits generating dependency information as a sideeffect of assembling, thus cutting build times in half. (Cherry-picked from libav commit 57b753b4) Signed-off-by: NJames Almer <jamrial@gmail.com>
-
由 James Almer 提交于
"nasm --version" works on nasm since around version 2.11 and as such configure assumed it was yasm. Based on libav commit f54037da by Diego Biurrun. Signed-off-by: NJames Almer <jamrial@gmail.com>
-
由 Diego Biurrun 提交于
Consistently use object format names with "32" suffix and set object format to "win64" on Windows x86_64, which fixes assembling with nasm. (Cherry-picked from libav commit 808ef435) Signed-off-by: NJames Almer <jamrial@gmail.com>
-
由 Diego Biurrun 提交于
(Cherry-picked from libav commit 3c0efbd0) Signed-off-by: NJames Almer <jamrial@gmail.com>
-
由 Diego Biurrun 提交于
None of them are specific to the YASM assembler. (Cherry-picked from libav commit 39e208f4) Signed-off-by: NJames Almer <jamrial@gmail.com>
-
由 Paul B Mahol 提交于
Signed-off-by: NPaul B Mahol <onemda@gmail.com>
-