Skip to content

L
libyuv
Switch branch/tag
  1. 03 Mar, 2017 1 commit
    • Henrik Kjellander's avatar
      DEPS: Remove root_dir variable. · 960088ec
      Henrik Kjellander authored 
      Due to legacy reasons, libyuv uses a root_dir variable in the DEPS file.
It was used to make the bots checkout into a 'src' dir instead of 'libyuv',
in order to get some tools working that had hard-coded assumptions on the name
'src' of the top-level directory. This changes all those dirs to be named
'src', which is needed to get tools_libyuv/autoroller/roll_deps.py to work
while keeping the buildbot infrastructure working.

BUG=libyuv:690
TBR=fbarchard@chromium.org

Change-Id: Ia138264d2576e3a9db95efa3de72a14531c92752
Reviewed-on: https://chromium-review.googlesource.com/447913Reviewed-by: 's avatarFrank Barchard <fbarchard@google.com>
      960088ec
  3. 03 Feb, 2017 1 commit
    • Henrik Kjellander's avatar
      Use DEPS for all dependencies + add PRESUBMIT.py · f49fde79
      Henrik Kjellander authored 
      This changes libyuv to use the DEPS file for pulling
down all dependencies (thus no Chromium checkout is needed any more).

Add tools_libyuv directory to contain libyuv-specific tools
(needed to avoid name collision with the now DEPSed tools/ directory
of Chromium, which is needed by the toolchain).
Add tools_libyuv/autoroller/roll_deps.py script to automatically
roll all entries in the DEPS file (copied from WebRTC).

third_party/ is now DEPSed as well, including the gtest configuration
headers that used to live inside the libyuv repo.

Add PRESUBMIT.py with a few simple checks + execution of PyLint and
Python unit tests. For PyLint a pylintrc file was also added.

Valgrind in tools_libyuv/valgrind was updated to make PRESUBMIT.py pass
and remove old tsan suppressions (not used).

Removed util/android/test_runner.py since it's no longer needed.

Buildbot changes in https://chromium-review.googlesource.com/436464 
are needed for the Memcheck bot to go green.

BUG=libyuv:676
NOTRY=True

Change-Id: Ib86fea2905a1656bba2933703ce5a59d29d8db6b
Reviewed-on: https://chromium-review.googlesource.com/436264
Commit-Queue: Henrik Kjellander <kjellander@chromium.org>
Reviewed-by: 's avatarFrank Barchard <fbarchard@google.com>
      f49fde79
  5. 02 Feb, 2017 1 commit
  7. 30 Jan, 2017 1 commit
  9. 26 Jan, 2017 1 commit
  11. 26 Oct, 2016 1 commit
  13. 07 Oct, 2016 1 commit
  15. 04 Oct, 2016 1 commit
  17. 22 Sep, 2016 1 commit
  19. 14 Sep, 2016 1 commit
  21. 08 Aug, 2016 1 commit
  23. 04 Aug, 2016 1 commit
  25. 08 Jun, 2016 1 commit
    • Frank Barchard's avatar
      document cpuid command line behavior · e2611a73
      Frank Barchard authored 
      cpu_info_ is zero for uninitialized state and all bits are off, disabling all cpu optimizations.
the 1 bit indicates cpu_info_ is initialized avoiding calling the detection code again for performance.

MaskCpuFlags initializes the cpu ignoring existing flags, then masks with the supplied flags and stores to cpu_info_.
As a mask, -1 has no effect, enabling all cpu features that were detected, but nothing that wasnt detected.
Setting to 0 will cause the next call to re-initialize the cpu, which is same as enabling all features.
Setting mask to 1 will turn off all cpu features but keep the initialized bit on, so the next detection call wont reinitialize and the cpu features are all disabled.

So normal behavior for command line and programatic masking is:
1 = C
-1 = SIMD

TBR=harryjin@google.com
BUG=libyuv:600
TESTED=out64/Release/bin/run_libyuv_unittest -s libyuv_unittest --verbose --release --gtest_filter=*ARGBExtractAlpha* -a "--libyuv_width=1280 --libyuv_height=720 --libyuv_repeat=9999 --libyuv_flags=1 --libyuv_cpu_info=1"

Review URL: https://codereview.chromium.org/2042933002 .
      e2611a73
  27. 07 Apr, 2016 1 commit
  29. 24 Feb, 2016 1 commit
  31. 19 Feb, 2016 1 commit
  33. 18 Feb, 2016 2 commits
  35. 17 Feb, 2016 1 commit