1. 07 Apr, 2016 1 commit
  2. 14 Dec, 2015 1 commit
    • Janne Grunau's avatar
      arm: add a cpu flag for the VFPv2 vector mode · e2710e79
      Janne Grunau authored
      The vector mode was deprecated in ARMv7-A/VFPv3 and various cpu
      implementations do not support it in hardware. Vector mode code will
      depending the OS either be emulated in software or result in an illegal
      instruction on cpus which does not support it. This was not really
      problem in practice since NEON implementations of the same functions are
      preferred. It will however become a problem for checkasm which tests
      every cpu flag separately.
      
      Since this is a cpu feature newer cpu do not support anymore the
      behaviour of this flag differs from the other flags. It can be only
      activated by runtime cpu feature selection.
      e2710e79
  3. 31 May, 2015 1 commit
  4. 19 Apr, 2015 1 commit
  5. 13 Aug, 2014 1 commit
  6. 03 Aug, 2014 2 commits
    • Janne Grunau's avatar
      cpu-test: test av_cpu_count · caf5ef85
      Janne Grunau authored
      Add CPU count and number threads as informative values for fate.
      caf5ef85
    • Janne Grunau's avatar
      fate: add informative cpu test · 07d8fa58
      Janne Grunau authored
      libavutil/cpu-test prints raw and effective cpu flags to STDERR. Detected
      cpu flags can be useful for debugging fate errors.
      
      No comparison of the result against a expected result since that would
      require fate config specific references.
      07d8fa58
  7. 06 Apr, 2014 1 commit
  8. 23 Feb, 2014 2 commits
  9. 15 Jan, 2014 1 commit
    • Janne Grunau's avatar
      aarch64: add cpuflags support for NEON and VFP · b7b17ed6
      Janne Grunau authored
      NEON and VFP are currently mandatory for all ARMv8 profiles. Both are
      handled as extensions as far as cpuflags are concerned. This is
      consistent with handling x86_64 which always has SSE2, but still
      handles it as an extension.
      b7b17ed6
  10. 23 Nov, 2013 1 commit
  11. 25 Oct, 2013 1 commit
  12. 28 Aug, 2013 1 commit
  13. 02 Jun, 2013 1 commit
  14. 24 May, 2013 2 commits
  15. 04 Dec, 2012 1 commit
  16. 04 Sep, 2012 2 commits
  17. 03 Aug, 2012 1 commit
    • 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
  18. 23 Jun, 2012 1 commit
  19. 25 Apr, 2012 2 commits
  20. 22 Apr, 2012 1 commit
  21. 12 Mar, 2012 1 commit
    • Janne Grunau's avatar
      remove iwmmxt optimizations · 363bd1c6
      Janne Grunau authored
      The were broken since August of 2010 without anyone noticing until
      three weeks ago. Nobody cares about it anymore and hopefully Marvell
      will support NEON like in the PXA978 from now on.
      363bd1c6
  22. 06 Mar, 2012 2 commits
  23. 26 Sep, 2011 1 commit
  24. 30 Jun, 2011 1 commit
  25. 22 Mar, 2011 1 commit
    • Justin Ruggles's avatar
      Add a CPU flag for the Atom processor. · eba586b0
      Justin Ruggles authored
      The Atom has SSSE3 support, which is useful in many cases, but sometimes the
      SSSE3 version is slower than the SSE2 equivalent on the Atom, but is generally
      faster on other processors supporting SSSE3. This flag allows for selectively
      disabling certain SSSE3 functions on the Atom.
      eba586b0
  26. 19 Mar, 2011 1 commit
  27. 20 Feb, 2011 1 commit
  28. 18 Jan, 2011 1 commit
  29. 07 Dec, 2010 1 commit
  30. 09 Sep, 2010 2 commits
  31. 08 Sep, 2010 1 commit