commit | daa4b000f48a2e283ef4a1977d945a988f78a590 | [log] [tgz] |
---|---|---|
author | Marco Paniconi <marpan@google.com> | Thu Jul 24 17:56:37 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jul 24 17:56:37 2025 |
tree | d2cf83cace4c5230dd70a6276e8f4cccfa4477b5 | |
parent | f6670ad889aa2794617f8da95cf0527e448d6019 [diff] |
Roll src/third_party/libaom/source/libaom/ a48eee7fd..f6055d0dc (8 commits) https://aomedia.googlesource.com/aom.git/+log/a48eee7fd280..f6055d0dc007 $ git log a48eee7fd..f6055d0dc --date=short --no-merges --format='%ad %ae %s' 2025-07-22 jianj Cosmetic: Fix clang-tidy warnings 2025-07-22 marpan rtc: Restrict usage of src_sad_blk_64x64 to single spatial layer 2025-07-22 juliobbv Enable screen detection mode 2 for image-focused tunings 2025-07-22 wtc DatarateTestPsnr: Fix CONFIG_INTERNAL_STATS check 2025-07-22 yunqingwang Add two shorts files for end-to-end tests 2025-01-09 phancke Allow per-frame calculation of PSNR 2025-07-22 jianj Remove tools/auto_refactor 2025-07-18 juliobbv Misc code review feedback follow-up Created with: roll-dep src/third_party/libaom/source/libaom R=jzern@google.coom Bug: b:307414544, b:432035817, b:433046392, webrtc:388070060 Change-Id: Ia68d6ff9fc38d5341b59fdb86198fff8c4e7e529 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6781964 Commit-Queue: Marco Paniconi <marpan@google.com> Reviewed-by: Wan-Teh Chang <wtc@google.com> Reviewed-by: James Zern <jzern@google.com> Cr-Commit-Position: refs/heads/main@{#1491583}
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.