commit | dadf81e237ab0d1a5cf405ad90d8dd66c19a91b5 | [log] [tgz] |
---|---|---|
author | Wan-Teh Chang <wtc@google.com> | Fri Dec 27 02:18:01 2024 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Dec 27 02:18:01 2024 |
tree | 6db7998bcaf92f222c7e52e35f7fa1047ce26393 | |
parent | f902413955d211b83ea1cff963e19bd1f2d23b20 [diff] |
Roll src/third_party/dav1d/libdav1d/ d242c47b4..2ba57aa53 (4 commits) https://chromium.googlesource.com/external/github.com/videolan/dav1d.git/+log/d242c47b437c..2ba57aa53589 $ git log d242c47b4..2ba57aa53 --date=short --no-merges --format='%ad %ae %s' 2024-12-16 martin arm32: looprestoration: Rewrite the wiener functions 2024-12-12 martin looprestoration: Use only 6 row buffer for wiener, like NEON/x86 2024-12-14 martin looprestoration: Make the C wiener h filter more optimizable for the compiler 2024-12-12 martin looprestoration: Rewrite the C version of the wiener filter Created with: roll-dep src/third_party/dav1d/libdav1d R=eugene@chromium.org Change-Id: Ice4bff8272c1fd941ac643374e7a03a05cd538a9 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6125309 Auto-Submit: Wan-Teh Chang <wtc@google.com> Commit-Queue: Wan-Teh Chang <wtc@google.com> Reviewed-by: Eugene Zemtsov <eugene@chromium.org> Commit-Queue: Eugene Zemtsov <eugene@chromium.org> Cr-Commit-Position: refs/heads/main@{#1400405}
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.