[wasm] Ship far jump tables
This flips the --wasm-far-jump-table flag. It will allow for more than 128MB of code space per wasm module on arm64, and will increase the limit on the number of modules per process on x64 (was ~1000 before, because we reserved 1GB for the code space per module). R=mstarzinger@chromium.org Bug: v8:9477 Change-Id: I870ec616f4812e38ef1e3fccf0629854a247bb4f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1815247 Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Commit-Queue: Clemens Backes [né Hammacher] <clemensh@chromium.org> Cr-Commit-Position: refs/heads/master@{#63967}
This commit is contained in:
parent
6d5e9b798e
commit
35ca0abdc5
@ -763,10 +763,9 @@ DEFINE_BOOL(wasm_code_gc, true, "enable garbage collection of wasm code")
|
||||
DEFINE_BOOL(trace_wasm_code_gc, false, "trace garbage collection of wasm code")
|
||||
DEFINE_BOOL(stress_wasm_code_gc, false,
|
||||
"stress test garbage collection of wasm code")
|
||||
DEFINE_BOOL(wasm_far_jump_table, false,
|
||||
DEFINE_BOOL(wasm_far_jump_table, true,
|
||||
"use multiple separate code spaces that might require far jumps "
|
||||
"between them")
|
||||
DEFINE_IMPLICATION(future, wasm_far_jump_table)
|
||||
DEFINE_INT(wasm_max_initial_code_space_reservation, 0,
|
||||
"maximum size of the initial wasm code space reservation (in MB)")
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user