Google Git
Sign in
fuchsia / third_party / libyuv / 3902eaaf86bddc32530632c86b0d2e98210e7bcd
commit3902eaaf86bddc32530632c86b0d2e98210e7bcd[log] [tgz]
authorFrank Barchard <fbarchard@google.com>Tue Jul 09 15:32:31 2024 -0700
committerFrank Barchard <fbarchard@google.com>Tue Jul 09 22:51:33 2024 +0000
tree437ae4803b390357840fb229fc15afe6628a9bff
parent899bc483273331429b7297dfe4f34f10334afa11 [diff]
Fix for source/row_neon64.cc:551:12: error: unused variable 'alpha' [-Werror,-Wunused-variable]
  551 |   uint16_t alpha = 0xc000;
      |            ^~~~~
1 error generated.

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