Signed-off-by: James Almer
---
doc/Doxyfile | 1 +
libavutil/arm/bswap.h| 4 ++--
libavutil/arm/intreadwrite.h | 4 ++--
libavutil/attributes.h | 2 ++
libavutil/x86/bswap.h| 8
5 files changed, 11 insertions(+), 8 deletions(-)
diff --git a/doc/Doxy
Signed-off-by: James Almer
---
tests/checkasm/Makefile | 1 +
tests/checkasm/checkasm.c| 3 ++
tests/checkasm/checkasm.h| 1 +
tests/checkasm/jpeg2000dsp.c | 71
4 files changed, 76 insertions(+)
create mode 100644 tests/checkasm/jpeg2
Signed-off-by: James Almer
---
Unbenched as i lack the hardware to do so.
libavcodec/x86/vp9dsp_init_16bpp_template.c | 22 ++
libavcodec/x86/vp9mc_16bpp.asm | 6 ++
2 files changed, 28 insertions(+)
diff --git a/libavcodec/x86/vp9dsp_init_16bpp_template.c
On 9/17/2015 5:43 AM, Henrik Gramner wrote:
> On Thu, Sep 17, 2015 at 12:02 AM, James Almer wrote:
>> +#define randomize_buffers()\
>> +do { \
>> +uint32_t r;\
>> +int
On Thu, Sep 17, 2015 at 08:11:39AM -0400, Ganesh Ajjanagadde wrote:
> This should fix warning reported by fate client:
> http://fate.ffmpeg.org/report.cgi?time=20150917113121&slot=x86_32-linux-gnu-gcc-4.5.1-have_6regs.
> Untested.
>
> Signed-off-by: Ganesh Ajjanagadde
> ---
> libavutil/log.c | 2
The randomize_buffer() implementation assures that "most of the time",
we'll do a good mix of wide16/wide8/hev/regular/no filters for complete
code coverage. However, this is not mathematically assured because that
would make the code either much more complex, or much less random.
---
tests/checka
Le jour de la Vertu, an CCXXIII, Paul B Mahol a écrit :
> So, is this patchset ready for pushing or there is something
> else that needs to be done?
I believe it is, but I am still in the rush after the end of vacations. I
expect to have contiguous time to re-test and push it during next week.
Re
On 9/16/2015 7:47 AM, Michael Niedermayer wrote:
> On Wed, Sep 16, 2015 at 01:53:10AM -0300, James Almer wrote:
>> Signed-off-by: James Almer
>> ---
>> All the casts to int64_t for these fields in assorted files can be removed in
>> a separate patch. I left those out so this patch was clean and ea
On Thu, Sep 17, 2015 at 9:15 AM, Paul B Mahol wrote:
> On 9/17/15, Ganesh Ajjanagadde wrote:
>> When compiled with --disable-pthreads, e.g
>> http://fate.ffmpeg.org/report.cgi?time=20150917015044&slot=alpha-debian-qemu-gcc-4.7,
>> a bunch of -Wunused-functions are reported.
>> This patch should s
On 9/17/15, Ganesh Ajjanagadde wrote:
> This should fix errors on a number of fate clients with the latest texinfo,
> e.g:
> http://fate.ffmpeg.org/report.cgi?time=20150917122742&slot=x86_64-darwin-clang-3.7-O3.
>
> Signed-off-by: Ganesh Ajjanagadde
> ---
> doc/filters.texi | 4 ++--
> 1 file ch
On 9/17/15, Ganesh Ajjanagadde wrote:
> When compiled with --disable-pthreads, e.g
> http://fate.ffmpeg.org/report.cgi?time=20150917015044&slot=alpha-debian-qemu-gcc-4.7,
> a bunch of -Wunused-functions are reported.
> This patch should silence such warnings.
>
> Signed-off-by: Ganesh Ajjanagadde
This should fix errors on a number of fate clients with the latest texinfo, e.g:
http://fate.ffmpeg.org/report.cgi?time=20150917122742&slot=x86_64-darwin-clang-3.7-O3.
Signed-off-by: Ganesh Ajjanagadde
---
doc/filters.texi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/d
On Thu, Sep 17, 2015 at 7:51 AM, Michael Niedermayer wrote:
> On Thu, Sep 17, 2015 at 06:54:37AM -0400, Ganesh Ajjanagadde wrote:
>> On Thu, Sep 17, 2015 at 6:17 AM, Michael Niedermayer
>> wrote:
>> > On Wed, Sep 16, 2015 at 10:22:27PM -0400, Ganesh Ajjanagadde wrote:
>> >> When compiled with --
When compiled with --disable-pthreads, e.g
http://fate.ffmpeg.org/report.cgi?time=20150917015044&slot=alpha-debian-qemu-gcc-4.7,
a bunch of -Wunused-functions are reported.
This patch should silence such warnings.
Signed-off-by: Ganesh Ajjanagadde
---
libavcodec/alac.c | 2 +-
libavcode
Commit 7404f3bdb switched bitrate to 64 bits.
This triggers -Wabsolute-value on clang, e.g
http://fate.ffmpeg.org/log.cgi?time=20150917122742&log=compile&slot=x86_64-darwin-clang-3.7-O3.
Therefore, usage of abs is changed to llabs, which is available on all of the
platforms.
Have not tested whethe
On 8/26/15, Nicolas George wrote:
> Do not assume that ff_request_frame() returning success
> implies a frame has arrived in the FIFO.
> Instead, just loop until a frame is in the FIFO.
> It does not change anything since the same loop is present
> in ff_request_frame(), confirmed by an assertion.
This should fix warning reported by fate client:
http://fate.ffmpeg.org/report.cgi?time=20150917113121&slot=x86_32-linux-gnu-gcc-4.5.1-have_6regs.
Untested.
Signed-off-by: Ganesh Ajjanagadde
---
libavutil/log.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/libavutil/log.c b
Suppose a sequence in h264 is IBB*P*BBPB*B[*P]BBP
How can I extract the previous (in the display order)
AV_PICTURE_TYPE_P frame of the current slice from the DPB list? how about
extracting both next and previous (in the display order) of a
AV_PICTURE_TYPE_B slice?
for example, for the input of
On Thu, Sep 17, 2015 at 06:54:37AM -0400, Ganesh Ajjanagadde wrote:
> On Thu, Sep 17, 2015 at 6:17 AM, Michael Niedermayer wrote:
> > On Wed, Sep 16, 2015 at 10:22:27PM -0400, Ganesh Ajjanagadde wrote:
> >> When compiled with --disable-pthreads, e.g
> >> http://fate.ffmpeg.org/report.cgi?time=2015
On Thu, Sep 17, 2015 at 6:15 AM, Hendrik Leppkes wrote:
> On Thu, Sep 17, 2015 at 12:19 AM, Ganesh Ajjanagadde
> wrote:
>> This patch moves the pointer validity check outside the macro,
>> and silences the -Waddress observed with GCC 5.2.
>>
>> Signed-off-by: Ganesh Ajjanagadde
>> ---
>> libavc
On Thu, Sep 17, 2015 at 6:17 AM, Michael Niedermayer wrote:
> On Wed, Sep 16, 2015 at 10:22:27PM -0400, Ganesh Ajjanagadde wrote:
>> When compiled with --disable-pthreads, e.g
>> http://fate.ffmpeg.org/report.cgi?time=20150917015044&slot=alpha-debian-qemu-gcc-4.7,
>> a bunch of -Wunused-functions
On Thu, Sep 17, 2015 at 4:54 AM, Clément Bœsch wrote:
> On Wed, Sep 16, 2015 at 06:55:39PM -0400, Ganesh Ajjanagadde wrote:
>> Glibc 2.20 onwards generates a deprecation warning for usage of _BSD_SOURCE
>> and _SVID_SOURCE.
>> The solution from man feature_test_macros is to define both _DEFAULT_S
On Wed, Sep 16, 2015 at 10:22:27PM -0400, Ganesh Ajjanagadde wrote:
> When compiled with --disable-pthreads, e.g
> http://fate.ffmpeg.org/report.cgi?time=20150917015044&slot=alpha-debian-qemu-gcc-4.7,
> a bunch of -Wunused-functions are reported due to missing header guards
> around threading relat
On Thu, Sep 17, 2015 at 12:19 AM, Ganesh Ajjanagadde
wrote:
> This patch moves the pointer validity check outside the macro,
> and silences the -Waddress observed with GCC 5.2.
>
> Signed-off-by: Ganesh Ajjanagadde
> ---
> libavcodec/libx264.c | 8 +---
> 1 file changed, 5 insertions(+), 3 d
On Thu, Sep 17, 2015 at 12:19 AM, Ganesh Ajjanagadde
wrote:
> This patch moves the pointer validity check outside the macro,
> and silences the -Waddress observed with GCC 5.2.
>
What kind of bogus warnings is GCC going to invent next?
This is a simple macro, and all use of this variable is prope
Signed-off-by: Paul B Mahol
---
doc/filters.texi | 48 +
libavfilter/Makefile | 1 +
libavfilter/af_agate.c | 253 +++
libavfilter/allfilters.c | 1 +
4 files changed, 303 insertions(+)
create mode 100644 libavfilter/af_agate
On Wed, Sep 16, 2015 at 06:55:39PM -0400, Ganesh Ajjanagadde wrote:
> Glibc 2.20 onwards generates a deprecation warning for usage of _BSD_SOURCE
> and _SVID_SOURCE.
> The solution from man feature_test_macros is to define both _DEFAULT_SOURCE
> and the old macros.
> This change is done in config
On Thu, Sep 17, 2015 at 12:02 AM, James Almer wrote:
> +#define randomize_buffers()\
> +do { \
> +uint32_t r;\
> +int i, j; \
> +
28 matches
Mail list logo
