| commit | 48e8e0c1fdf5a2dbd9df614db7863ad768cdace3 | [log] [tgz] |
|---|---|---|
| author | Daniel Lehmann <dlehmann@chromium.org> | Mon May 19 13:00:29 2025 |
| committer | V8 LUCI CQ <v8-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon May 19 14:12:47 2025 |
| tree | ced0d702aa26019f523804900499d31feb8348da | |
| parent | 37d6fa3f39e17bf46d1cdf340e666cbd3ff976b3 [diff] |
[wasm] Cleanup implications for call_indirect inlining Now that https://crrev.com/c/6431682 enables call_indirect inlining by default, we no longer need an implication from --future. Thus also revert the changes in tests introduced when we added this implication in https://crrev.com/c/5929031. Also, the implication from --wasm-inlining-call-indirect to --wasm-inlining makes it inconvenient to disable inlining altogether (because it will cause an incompatible flag implications error without explicitly specifying --no-wasm-inlining-call-indirect too.) Use a neg-neg implication instead. This came up in the context of https://chromium-review.googlesource.com/c/v8/v8/+/6541895/comment/35743e3d_14d8daf6/ Bug: 335082212 Change-Id: I2c97263f2e1e1b6174c27e8b79da34198efb6619 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6564464 Reviewed-by: Matthias Liedtke <mliedtke@chromium.org> Commit-Queue: Daniel Lehmann <dlehmann@chromium.org> Cr-Commit-Position: refs/heads/main@{#100350}
V8 is Google's open source JavaScript engine.
V8 implements ECMAScript as specified in ECMA-262.
V8 is written in C++ and is used in Google Chrome, the open source browser from Google.
V8 can run standalone, or can be embedded into any C++ application.
V8 Project page: https://v8.dev/docs
Checkout depot tools, and run
fetch v8
This will checkout V8 into the directory v8 and fetch all of its dependencies. To stay up to date, run
git pull origin
gclient sync
For fetching all branches, add the following into your remote configuration in .git/config:
fetch = +refs/branch-heads/*:refs/remotes/branch-heads/*
fetch = +refs/tags/*:refs/tags/*
Please follow the instructions mentioned at v8.dev/docs/contribute.