1. 24 Jul, 2006 2 commits
  2. 23 Jul, 2006 2 commits
  3. 20 Jul, 2006 1 commit
  4. 10 Jul, 2006 1 commit
  5. 01 Jul, 2006 1 commit
  6. 30 Jun, 2006 1 commit
  7. 09 Jun, 2006 1 commit
  8. 05 Jun, 2006 1 commit
  9. 02 Jun, 2006 1 commit
  10. 07 May, 2006 1 commit
  11. 06 May, 2006 1 commit
    • michael's avatar
      removing esp usage · 63cdb730
      michael authored
      this is certainly not the most beautifull but it should work without -fomit-frame-pointer and PIC and gcc-4 vomits when ebp is given in a constraint directly even with -fomi-frame-pointer so theres not that much choice ...
      if anyone knows a simpler/cleaner solution, dont hesitate to suggest it ...
      
      
      git-svn-id: file:///var/local/repositories/mplayer/trunk/postproc@18393 b3059339-0415-0410-9bf9-f77b7e298cf2
      63cdb730
  12. 27 Apr, 2006 1 commit
  13. 16 Apr, 2006 1 commit
  14. 15 Apr, 2006 1 commit
  15. 06 Apr, 2006 1 commit
  16. 13 Mar, 2006 1 commit
  17. 24 Feb, 2006 1 commit
  18. 18 Feb, 2006 2 commits
  19. 17 Feb, 2006 1 commit
  20. 16 Feb, 2006 2 commits
  21. 13 Feb, 2006 1 commit
  22. 11 Feb, 2006 3 commits
  23. 09 Feb, 2006 2 commits
    • rathann's avatar
      Patch by Stefan Huehner / stefan % huehner ! org \ · 629e8c38
      rathann authored
      patch replaces '()' for the correct '(void)' in function
      declarations/prototypes which have no parameters. The '()' syntax tell
      thats there is a variable list of arguments, so that the compiler cannot
      check this. The extra CFLAG '-Wstrict-declarations' shows those cases.
      
      Comments about a similar patch applied to ffmpeg:
      
      That in C++ these mean the same, but in ANSI C the semantics are
      different; function() is an (obsolete) K&R C style forward declaration,
      it basically means that the function can have any number and any types
      of parameters, effectively completely preventing the compiler from doing
      any sort of type checking. -- Erik Slagter
      
      Defining functions with unspecified arguments is allowed but bad.
      With arguments unspecified the compiler can't report an error/warning
      if the function is called with incorrect arguments. -- Måns Rullgård
      
      
      git-svn-id: file:///var/local/repositories/mplayer/trunk/postproc@17567 b3059339-0415-0410-9bf9-f77b7e298cf2
      629e8c38
    • diego's avatar
      Correct RGB vs. BGR confusion, the macros vec_mstrgb24 and vec_mstbgr24 each · bd258d8a
      diego authored
      do the opposite of what they say.
      The vec_mstrgb24 and vec_mstbgr24 macros should be opposites and not perform
      the same things.
      patch by Alan Curry, pacman_at_world_dot_std_dot_com
      
      
      git-svn-id: file:///var/local/repositories/mplayer/trunk/postproc@17564 b3059339-0415-0410-9bf9-f77b7e298cf2
      bd258d8a
  24. 08 Feb, 2006 3 commits
  25. 04 Feb, 2006 1 commit
  26. 27 Jan, 2006 1 commit
  27. 13 Jan, 2006 1 commit
  28. 14 Nov, 2005 1 commit
  29. 17 Oct, 2005 1 commit
  30. 12 Oct, 2005 1 commit
  31. 06 Sep, 2005 1 commit