1. 26 Jan, 2013 1 commit
  2. 24 Jan, 2013 1 commit
  3. 23 Jan, 2013 4 commits
  4. 22 Jan, 2013 3 commits
  5. 21 Jan, 2013 1 commit
  6. 20 Jan, 2013 2 commits
  7. 18 Jan, 2013 1 commit
  8. 16 Jan, 2013 1 commit
  9. 20 Dec, 2012 1 commit
  10. 26 Nov, 2012 1 commit
  11. 25 Nov, 2012 2 commits
  12. 16 Nov, 2012 1 commit
  13. 13 Nov, 2012 1 commit
  14. 31 Oct, 2012 3 commits
  15. 30 Oct, 2012 1 commit
  16. 05 Oct, 2012 1 commit
  17. 13 Sep, 2012 1 commit
  18. 12 Sep, 2012 1 commit
  19. 11 Sep, 2012 1 commit
  20. 07 Sep, 2012 3 commits
  21. 06 Sep, 2012 1 commit
  22. 30 Aug, 2012 2 commits
  23. 28 Aug, 2012 1 commit
  24. 08 Aug, 2012 1 commit
  25. 07 Aug, 2012 1 commit
  26. 03 Aug, 2012 2 commits
    • Diego Biurrun's avatar
      x86: build: replace mmx2 by mmxext · 239fdf1b
      Diego Biurrun authored
      Refactoring mmx2/mmxext YASM code with cpuflags will force renames.
      So switching to a consistent naming scheme beforehand is sensible.
      The name "mmxext" is more official and widespread and also the name
      of the CPU flag, as reported e.g. by the Linux kernel.
      239fdf1b
    • Diego Biurrun's avatar
      x86: Use consistent 3dnowext function and macro name suffixes · ca844b7b
      Diego Biurrun authored
      Currently there is a wild mix of 3dn2/3dnow2/3dnowext.  Switching to
      "3dnowext", which is a more common name of the CPU flag, as reported
      e.g. by the Linux kernel, unifies this.
      ca844b7b
  27. 02 Aug, 2012 1 commit