Google Git
Sign in
fuchsia/third_party/libyuv/refs/heads/main
commit
4afb9654162e142b52d349471823815f4c60bc3d
[log]
author
Frank Barchard <fbarchard@google.com>
Wed Apr 22 15:20:00 2026 -0700
committer
libyuv-scoped@luci-project-accounts.iam.gserviceaccount.com <libyuv-scoped@luci-project-accounts.iam.gserviceaccount.com>
Wed Apr 22 16:56:46 2026 -0700
tree
9d689407c8b78e3e3c56983b746420916b69dd47
parent
bd2c4c76ec4e5986e87429874139e07454bbd49c [diff]
RAWToARGB use AVX512BW

Bug: libyuv:42280902
Change-Id: I7a80fd64d97b6d411316819df0fd917d609a173b
Reviewed-on: https://chromium-review.googlesource.com/c/libyuv/libyuv/+/7787163
Reviewed-by: richard winterton <rrwinterton@gmail.com>
Commit-Queue: Frank Barchard <fbarchard@google.com>
7 files changed
tree: 9d689407c8b78e3e3c56983b746420916b69dd47
  1. build_overrides/
  2. docs/
  3. include/
  4. infra/
  5. riscv_script/
  6. source/
  7. tools_libyuv/
  8. unit_test/
  9. util/
  10. .clang-format
  11. .gitignore
  12. .gn
  13. .vpython3
  14. Android.bp
  15. Android.mk
  16. AUTHORS
  17. BUILD.bazel
  18. BUILD.gn
  19. CM_linux_packages.cmake
  20. CMakeLists.txt
  21. codereview.settings
  22. DEPS
  23. DIR_METADATA
  24. download_vs_toolchain.py
  25. libyuv.bzl
  26. libyuv.gni
  27. libyuv.gyp
  28. libyuv.gypi
  29. LICENSE
  30. linux.mk
  31. OWNERS
  32. PATENTS
  33. PRESUBMIT.py
  34. public.mk
  35. pylintrc
  36. README.chromium
  37. README.md
  38. winarm.mk
  39. WORKSPACE.bazel
README.md

libyuv is an open source project that includes YUV scaling and conversion functionality.

  • Scale YUV to prepare content for compression, with point, bilinear or box filter.
  • Convert to YUV from webcam formats for compression.
  • Convert to RGB formats for rendering/effects.
  • Rotate by 90/180/270 degrees to adjust for mobile devices in portrait mode.
  • Optimized for SSSE3/AVX2 on x86/x64.
  • Optimized for Neon/SVE2/SME on Arm.
  • Optimized for MSA on Mips.
  • Optimized for RVV on RISC-V.

Development

See Getting started for instructions on how to get started developing.

You can also browse the docs directory for more documentation.