[gin] Use new command line feature for Wasm inlining https://crrev.com/c/4335553 added --experimental-wasm-inlining as the new source of truth for enabling Wasm inlining. Hence the finch trial should use that flag. We can then remove the previous (now redundant) --wasm-inlining and --wasm-speculative-inlining flags. R=leszeks@chromium.org CC=jkummerow@chromium.org Bug: 1424350 Change-Id: I518165ac9dd92bb1e89e9a32ce96d060326817ae Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4344272 Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#1119279}
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.