1. 05 Jul, 2014 2 commits
  2. 03 Jul, 2014 1 commit
  3. 01 Jul, 2014 1 commit
  4. 30 Jun, 2014 1 commit
  5. 26 Jun, 2014 1 commit
  6. 25 Jun, 2014 1 commit
  7. 23 Jun, 2014 2 commits
  8. 22 Jun, 2014 1 commit
  9. 18 Jun, 2014 1 commit
  10. 10 Jun, 2014 1 commit
    • Martin Storsjö's avatar
      x86: h264: Don't keep data in the redzone across function calls on 64 bit unix · 570d4b21
      Martin Storsjö authored
      
      
      We know that the called function (ff_chroma_inter_body_mmxext)
      doesn't touch the redzone, and thus will be kept intact - thus,
      this doesn't fix any bug per se.
      
      However, valgrind's memcheck tool intentionally assumes that the
      redzone is clobbered on every function call and function return
      (see a long comment in valgrind/memcheck/mc_main.c). This avoids
      false positives in that tool, at the cost of an extra stack pointer
      adjustment.
      
      The other alternative would be a valgrind suppression for this issue,
      but that's an extra burden for everybody that wants to run libavcodec
      within valgrind.
      Signed-off-by: default avatarMartin Storsjö <martin@martin.st>
      570d4b21
  11. 29 May, 2014 3 commits
  12. 27 May, 2014 2 commits
  13. 13 Apr, 2014 1 commit
  14. 11 Apr, 2014 2 commits
  15. 04 Apr, 2014 9 commits
  16. 26 Mar, 2014 3 commits
  17. 22 Mar, 2014 5 commits
  18. 20 Mar, 2014 3 commits