1. 14 Mar, 2017 1 commit
    • Diego Biurrun's avatar
      x86util: Port all macros to cpuflags · 994c4bc1
      Diego Biurrun authored
      Also do some small cosmetic changes: Drop pointless _MMX suffix from ABSD2
      macro name, drop pointless check for MMX support, we always assume MMX is
      available in our SIMD code, fix spelling.
      994c4bc1
  2. 12 Mar, 2017 3 commits
    • Anton Khirnov's avatar
      h264_cavlc: check the value of run_before · 522d850e
      Anton Khirnov authored
      Section 9.2.3.2 of the spec implies that run_before must not be larger
      than zeros_left.
      
      Fixes invalid reads with corrupted files.
      
      CC: libav-stable@libav.org
      Bug-Id: 1000
      Found-By: Kamil Frankowicz
      522d850e
    • Anton Khirnov's avatar
      h2645_parse: use the bytestream2 API for packet splitting · 83b2b34d
      Anton Khirnov authored
      The code does some nontrivial jumping around in the buffer, so it is
      safer to use a checked API rather than do everything manually.
      
      Fixes a bug in nalff parsing, where the length field is currently not
      counted in the buffer size check, resulting in possible overreads with
      invalid files.
      
      CC: libav-stable@libav.org
      Bug-Id: 1002
      Found-By: Kamil Frankowicz
      83b2b34d
    • Anton Khirnov's avatar
      h264dec: initialize field_started to 0 on each decode call · b76f6a76
      Anton Khirnov authored
      It might be incorrectly set to 1 if the previous call exited with an
      error.
      
      Bug-Id: 1019
      CC: libav-stable@libav.org
      b76f6a76
  3. 11 Mar, 2017 2 commits
  4. 09 Mar, 2017 4 commits
  5. 07 Mar, 2017 13 commits
  6. 06 Mar, 2017 1 commit
    • Vittorio Giovara's avatar
      pixlet: Fix architecture-dependent code and values · b44bd7ee
      Vittorio Giovara authored
      The constants used in the decoder used floating point precision,
      and this caused different values to be generated on different
      architectures. Additionally on big endian machines, the fate test
      would output bytes in native order, which is different from the one
      hardcoded in the test.
      
      So, eradicate floating point numbers and use fixed point (32.32)
      arithmetics everywhere, replacing constants with precomputed integer
      values, and force the pixel format output to be the same in the fate
      test.
      Signed-off-by: 's avatarVittorio Giovara <vittorio.giovara@gmail.com>
      b44bd7ee
  7. 05 Mar, 2017 2 commits
  8. 04 Mar, 2017 1 commit
  9. 01 Mar, 2017 13 commits