commit | d70295a3f75fc182b12eb3fd297b240063418807 | [log] [tgz] |
---|---|---|
author | Marco Paniconi <marpan@google.com> | Wed Jan 22 20:18:14 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 22 20:18:14 2025 |
tree | 89b5250e062e05fc54a71287ac725c9420e204a5 | |
parent | e4f125c1456530ecf6ac8694dc9cf67ec91c9339 [diff] |
Roll src/third_party/libaom/source/libaom/ d737ca3eb..3f94cfa28 (6 commits) https://aomedia.googlesource.com/aom.git/+log/d737ca3ebe92..3f94cfa28295 $ git log d737ca3eb..3f94cfa28 --date=short --no-merges --format='%ad %ae %s' 2024-12-27 marpan rtc-screen: Make sb horiz scroll search window same as vert 2024-12-13 mahesh Match types between refs and coeffs in generic path 2025-01-16 wtc Remove the int16_t * casts for av1_warped_filter 2025-01-16 wtc Remove the int16_t * casts for av1_warped_filter 2025-01-13 jzern README.md: add a note for MSYS2 yasm/nasm binaries 2025-01-13 jerytsai riscv64: Introduce RVV and cpu-detection Created with: roll-dep src/third_party/libaom/source/libaom R=jzern@google.com Bug: b:307414544, b:383306740 Change-Id: I9b1698095d31bf0d3230bdfd12bff3b4c1433dbe Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6191068 Reviewed-by: James Zern <jzern@google.com> Reviewed-by: Wan-Teh Chang <wtc@google.com> Commit-Queue: James Zern <jzern@google.com> Cr-Commit-Position: refs/heads/main@{#1409882}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone
! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure.
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.