Gitiles
Code Review Sign In
android-review.linaro.org / platform / external / libyuv / acb14ffaa4a780e352435dd268ebdf96c3e8317d
commitacb14ffaa4a780e352435dd268ebdf96c3e8317d[log] [tgz]
authorFrank Barchard <fbarchard@google.com>Tue Aug 01 13:27:37 2023 -0700
committerlibyuv LUCI CQ <libyuv-scoped@luci-project-accounts.iam.gserviceaccount.com>Wed Aug 02 08:19:02 2023 +0000
tree30cf15f4f01873a075c2c74b53102650e7582ece
parentcbd28db64b6a53d6c315e374134f2e24a5fd241c [diff]
cpu_test show __riscv_v_intrinsic quals to 11000 (v0.11) or 1000000 (v1.0).

Bug: libyuv:965
Change-Id: Ic983cc036b0b628a82dd2f4bb5eb649af4bfaa08
Reviewed-on: https://chromium-review.googlesource.com/c/libyuv/libyuv/+/4739822
Commit-Queue: Frank Barchard <fbarchard@chromium.org>
Reviewed-by: Mirko Bonadei <mbonadei@chromium.org>
1 file changed
tree: 30cf15f4f01873a075c2c74b53102650e7582ece
  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. .vpython
  14. .vpython3
  15. Android.bp
  16. Android.mk
  17. AUTHORS
  18. BUILD.gn
  19. cleanup_links.py
  20. CM_linux_packages.cmake
  21. CMakeLists.txt
  22. codereview.settings
  23. DEPS
  24. DIR_METADATA
  25. download_vs_toolchain.py
  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
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 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.