Skip to content
Snippets Groups Projects
  1. Nov 02, 2010
  2. Nov 01, 2010
  3. Oct 29, 2010
  4. Oct 28, 2010
    • Yunqing Wang's avatar
      Save XMM registers in asm functions · 6614563b
      Yunqing Wang authored
      XMM6/7 are used in these functions, and need to be saved.
      
      Change-Id: I3dfaddaf2a69cd4bf8e8735c7064b17bac5a14e5
      6614563b
    • Yunqing Wang's avatar
    • John Koleszar's avatar
      Merge branch 'aylesbury' · 9d93dabe
      John Koleszar authored
      9d93dabe
    • Yunqing Wang's avatar
      Fix full-search SAD function crash in Visual Studio · 7e3a1e73
      Yunqing Wang authored
      Unlike GCC, Visual Studio compiler doesn't allocate SAD output
      array 16-byte aligned, which causes crash in visual studio.
      
      Change-Id: Ia755cf5a807f12929bda8db94032bb3c9d0c2362
      7e3a1e73
    • John Koleszar's avatar
      CHANGELOG: correct date · cad21649
      John Koleszar authored
      Change-Id: I146a7f241efad4f0684cf8613c7fa42bd5cf42f3
      cad21649
    • John Koleszar's avatar
      Update CHANGELOG for v0.9.5 (Aylesbury) release · 686b217e
      John Koleszar authored
      Change-Id: Ic9f05dbbe90480d5b172233c87eaf1d4e2f1b48e
      686b217e
    • Timothy B. Terriberry's avatar
      Eliminate more warnings. · 97b766a4
      Timothy B. Terriberry authored
      This eliminates a large set of warnings exposed by the Mozilla build
       system (Use of C++ comments in ISO C90 source, commas at the end of
       enum lists, a couple incomplete initializers, and signed/unsigned
       comparisons).
      It also eliminates many (but not all) of the warnings expose by newer
       GCC versions and _FORTIFY_SOURCE (e.g., calling fread and fwrite
       without checking the return values).
      There are a few spurious warnings left on my system:
      
      ../vp8/encoder/encodemb.c:274:9: warning: 'sz' may be used
       uninitialized in this function
      gcc seems to be unable to figure out that the value shortcut doesn't
       change between the two if blocks that test it here.
      
      ../vp8/encoder/onyx_if.c:5314:5: warning: comparison of unsigned
       expression >= 0 is always true
      ../vp8/encoder/onyx_if.c:5319:5: warning: comparison of unsigned
       expression >= 0 is always true
      This is true, so far as it goes, but it's comparing against an enum,
       and the C standard does not mandate that enums be unsigned, so the
       checks can't be removed.
      
      Change-Id: Iead6cd561a2afaa3d801fd63f1d8d58953da7426
      97b766a4
    • Fritz Koenig's avatar
      postproc: Tweaks to line drawing and blending. · 6fda7668
      Fritz Koenig authored
      Turned down the blending level to make colored blocks obscure
      the video less.
      Not blending the entire block to give distinction to macro
      block edges.
      Added configuration so that macro block blending function can
      be optimized.
      Change to constrain line as to when dx and dy are computed.
      Now draw two lines to form an arrow.
      
      Change-Id: I986784e6abff65ea3e0d1437dfca7d06d44ede71
      6fda7668
    • Frank Galligan's avatar
      Output the PSNR for the entire file. · 483ce403
      Frank Galligan authored
      If --psnr option is enabled vpxenc will output PSNR values for the
      entire file. Added a \n before final output to make sure the output
      is on its own line. Overall and Avg psnr matches the values written
      to opsnr.stt file.
      
      Change-Id: Ibac5fa9baf8d5a626ea0d6ba161b484e6e8427ee
      483ce403
    • Timothy B. Terriberry's avatar
      Eliminate more warnings. · c4d7e5e6
      Timothy B. Terriberry authored
      This eliminates a large set of warnings exposed by the Mozilla build
       system (Use of C++ comments in ISO C90 source, commas at the end of
       enum lists, a couple incomplete initializers, and signed/unsigned
       comparisons).
      It also eliminates many (but not all) of the warnings expose by newer
       GCC versions and _FORTIFY_SOURCE (e.g., calling fread and fwrite
       without checking the return values).
      There are a few spurious warnings left on my system:
      
      ../vp8/encoder/encodemb.c:274:9: warning: 'sz' may be used
       uninitialized in this function
      gcc seems to be unable to figure out that the value shortcut doesn't
       change between the two if blocks that test it here.
      
      ../vp8/encoder/onyx_if.c:5314:5: warning: comparison of unsigned
       expression >= 0 is always true
      ../vp8/encoder/onyx_if.c:5319:5: warning: comparison of unsigned
       expression >= 0 is always true
      This is true, so far as it goes, but it's comparing against an enum, and the C
       standard does not mandate that enums be unsigned, so the checks can't be
       removed.
      
      Change-Id: Iaf689ae3e3d0ddc5ade00faa474debe73b8d3395
      c4d7e5e6
  5. Oct 27, 2010
  6. Oct 26, 2010
Loading