Skip to content

Commit

Permalink
[wasm] Enable dynamic tiering by default
Browse files Browse the repository at this point in the history
This enabled dynamic tiering by default in V8. Chromium overwrites the
default, so this CL by itself has no effect on Chrome users, but a
similar CL will land in the chromium repo.

[email protected]

Bug: v8:12281
Change-Id: Iaa6d77dc80063f3c4e1d005c371573fc70c698aa
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3568449
Reviewed-by: Maya Lekova <[email protected]>
Commit-Queue: Clemens Backes <[email protected]>
Cr-Commit-Position: refs/heads/main@{#79804}
  • Loading branch information
backes authored and V8 LUCI CQ committed Apr 6, 2022
1 parent 4c99c01 commit bfe1280
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions src/flags/flag-definitions.h
Original file line number Diff line number Diff line change
Expand Up @@ -983,10 +983,9 @@ DEFINE_UINT(wasm_max_code_space, v8::internal::kMaxWasmCodeMB,
DEFINE_BOOL(wasm_tier_up, true,
"enable tier up to the optimizing compiler (requires --liftoff to "
"have an effect)")
DEFINE_BOOL(wasm_dynamic_tiering, false,
DEFINE_BOOL(wasm_dynamic_tiering, true,
"enable dynamic tier up to the optimizing compiler")
DEFINE_NEG_NEG_IMPLICATION(liftoff, wasm_dynamic_tiering)
DEFINE_WEAK_IMPLICATION(future, wasm_dynamic_tiering)
DEFINE_INT(wasm_tiering_budget, 1800000,
"budget for dynamic tiering (rough approximation of bytes executed")
DEFINE_INT(
Expand Down

0 comments on commit bfe1280

Please sign in to comment.