git.libav.org Git - libav.git/rss log

Libav master git repository

http://git.libav.org/?p=libav.git;a=summary

Les articles publiés sur le site

  • configure : Add missing dxva2 dependency for dxva2_lib

    11 décembre 2016, par Diego Biurrun
    configure: Add missing dxva2 dependency for dxva2_lib
    
    • [DBH] configure
  • hevc : ppc : Add HEVC 4x4 IDCT for PowerPC

    11 décembre 2016, par Alexandra Hajkova
    hevc: ppc: Add HEVC 4x4 IDCT for PowerPC
    
    Signed-off-by: Diego Biurrun <diego@biurrun.de>
    
    • [DBH] libavcodec/hevcdsp.c
    • [DBH] libavcodec/hevcdsp.h
    • [DBH] libavcodec/ppc/Makefile
    • [DBH] libavcodec/ppc/hevcdsp.c
    • [DBH] libavcodec/ppc/hevcdsp_template.c
  • configure : Fix _libs vs. _extralibs oversight

    10 décembre 2016, par Diego Biurrun
    configure: Fix _libs vs. _extralibs oversight
    
    • [DBH] configure
  • pthread_frame : use better memory orders for frame progress

    9 décembre 2016, par Wan-Teh Chang
    pthread_frame: use better memory orders for frame progress
    
    This improves commit 59c70227405c214b29971e6272f3a3ff6fcce3d0.
    
    In ff_thread_report_progress(), the fast code path can load
    progress[field] with the relaxed memory order, and the slow code path
    can store progress[field] with the release memory order. These changes
    are mainly intended to avoid confusion when one inspects the source code.
    They are unlikely to have measurable performance improvement.
    
    ff_thread_report_progress() and ff_thread_await_progress() form a pair.
    ff_thread_await_progress() reads progress[field] with the acquire memory
    order (in the fast code path). Therefore, one expects to see
    ff_thread_report_progress() write progress[field] with the matching
    release memory order.
    
    In the fast code path in ff_thread_report_progress(), the atomic load of
    progress[field] doesn't need the acquire memory order because the
    calling thread is trying to make the data it just decoded visible to the
    other threads, rather than trying to read the data decoded by other
    threads.
    
    In ff_thread_get_buffer(), initialize progress[0] and progress[1] using
    atomic_init().
    
    Signed-off-by: Wan-Teh Chang <wtc@google.com>
    Signed-off-by: Anton Khirnov <anton@khirnov.net>
    
    • [DBH] libavcodec/pthread_frame.c
  • build : Add -D_XOPEN_SOURCE=600 to CPPFLAGS on Cygwin

    9 décembre 2016, par Diego Biurrun
    build: Add -D_XOPEN_SOURCE=600 to CPPFLAGS on Cygwin
    
    This is required to make certain math defines visible on modern Cygwin.
    
    • [DBH] configure