Google Git
Sign in
fuchsia / third_party / libyuv / HEAD
commit022efdb0b771f7353741dbe360b8bef4e0a874eb[log] [tgz]
authorValentin Haudiquet <valentin.haudiquet@canonical.com>Tue Dec 09 11:20:20 2025 +0100
committerlibyuv LUCI CQ <libyuv-scoped@luci-project-accounts.iam.gserviceaccount.com>Tue Jan 06 11:16:24 2026 -0800
tree96593b578c1a62c0706681479b7bec1de36a557a
parent821b9c5de1cf232f51c26e1eaad4689fc2317949 [diff]
RVV: Enable RVV on GCC

GCC now supports vector segment load and store, which
was previously missing; and the reason why it was disabled.

Change-Id: I923fd8a15476de8dcc2103bb8335d4fcc3ca96a9
Reviewed-on: https://chromium-review.googlesource.com/c/libyuv/libyuv/+/7241606
Reviewed-by: Frank Barchard <fbarchard@chromium.org>
Reviewed-by: Wan-Teh Chang <wtc@google.com>
Commit-Queue: Wan-Teh Chang <wtc@google.com>
2 files changed
tree: 96593b578c1a62c0706681479b7bec1de36a557a
  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.gn
  18. CM_linux_packages.cmake
  19. CMakeLists.txt
  20. codereview.settings
  21. DEPS
  22. DIR_METADATA
  23. download_vs_toolchain.py
  24. libyuv.gni
  25. libyuv.gyp
  26. libyuv.gypi
  27. LICENSE
  28. linux.mk
  29. OWNERS
  30. PATENTS
  31. PRESUBMIT.py
  32. public.mk
  33. pylintrc
  34. README.chromium
  35. README.md
  36. winarm.mk
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.