[libav-devel] [RFC] [PATCH] Drop non-refcounted-frame code on the next version bump

2017-10-21 Thread Diego Biurrun
--- libavcodec/decode.c | 11 +++ libavcodec/version.h | 3 +++ libavfilter/vsrc_movie.c | 5 + 3 files changed, 19 insertions(+) diff --git a/libavcodec/decode.c b/libavcodec/decode.c index b74c163f92..040e1cc08e 100644 --- a/libavcodec/decode.c +++ b/libavcodec/decode.c @

Re: [libav-devel] [libav-commits] lavc: external hardware frame pool initialization

2017-10-21 Thread Diego Biurrun
On Thu, Oct 19, 2017 at 05:25:17PM +0200, wm4 wrote: > Module: libav > Author:wm4 > Committer: Anton Khirnov > Date: Thu Oct 19 16:38:20 2017 +0200 > > lavc: external hardware frame pool initialization > > This adds a new API, which allows the API user to query the required > AVHWFram

Re: [libav-devel] [GASPP PATCH] Conditionally work around an armasm64 bug in the scale operand to fcvtzs/scvtf

2017-10-21 Thread Martin Storsjö
On Sat, 21 Oct 2017, Diego Biurrun wrote: On Sat, Oct 21, 2017 at 12:04:48AM +0300, Martin Storsjo wrote: The operand shouldn't be stored as is, but stored as 64-scale, in the opcode, but armasm64 currently misses to do this. This bug will be fixed in a future release, and a fix for the bug wi

Re: [libav-devel] [GASPP PATCH] Conditionally work around an armasm64 bug in the scale operand to fcvtzs/scvtf

2017-10-21 Thread Diego Biurrun
On Sat, Oct 21, 2017 at 12:04:48AM +0300, Martin Storsjo wrote: > The operand shouldn't be stored as is, but stored as 64-scale, in > the opcode, but armasm64 currently misses to do this. > > This bug will be fixed in a future release, and a fix for the bug > will break the workaround. Therefore,

Re: [libav-devel] [GASPP PATCH] Conditionally work around an armasm64 bug in the scale operand to fcvtzs/scvtf

2017-10-21 Thread Diego Biurrun
On Sat, Oct 21, 2017 at 12:04:48AM +0300, Martin Storsjo wrote: > The operand shouldn't be stored as is, but stored as 64-scale, in > the opcode, but armasm64 currently misses to do this. > > This bug will be fixed in a future release, and a fix for the bug > will break the workaround. Therefore,