This is an automated email from the git hooks/post-receive script.

Git pushed a change to branch master
in repository ffmpeg.

    from c51a420b59 doc/examples/hw_decode: check fopen return value for output 
file
     new 5230624619 swscale/graph: allocate output buffers after adding all 
passes
     new 18962a3764 swscale/ops: loop over copied list instead of original 
(cosmetic)
     new 91e76dc766 swscale/ops_dispatch: remove slice_align hack
     new 800c3a71e9 swscale/ops_dispatch: properly handle negative strides
     new 039b492019 swscale/ops_dispatch: correctly round tail size
     new 3310fe95ae swscale/ops_dispatch: also print ops list after optimizing
     new ef114cedef swscale/ops_chain: refactor setup() signature
     new 9c6638b179 swscale/ops_chain: add SwsOpTable to SwsImplParams
     new 3aef0213e7 swscale/ops_chain: add SwsContext to SwsImplParams
     new 8e3eacd7ad swscale/ops_chain: allow implementations to expose 
over_read/write
     new a8606aba8e swscale/x86/ops: move over_read/write determination to 
setup func
     new 70537ec8e6 swscale/x86/ops: cosmetic

The 12 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 libswscale/graph.c          | 11 +++---
 libswscale/graph.h          |  8 +++--
 libswscale/ops.c            |  6 ++--
 libswscale/ops_backend.c    |  6 ++--
 libswscale/ops_backend.h    | 13 +++----
 libswscale/ops_chain.c      | 70 +++++++++++++++++++++---------------
 libswscale/ops_chain.h      | 43 +++++++++++++++-------
 libswscale/ops_dispatch.c   | 31 ++++++++++------
 libswscale/ops_tmpl_float.c | 21 ++++++-----
 libswscale/x86/ops.c        | 87 ++++++++++++++++++++++++++-------------------
 10 files changed, 180 insertions(+), 116 deletions(-)

_______________________________________________
ffmpeg-cvslog mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to