fa3cd68a3f
The WasmEngine is shared across the whole process, so there is no need to store it in every Isolate. Instead, we can just get it from everywhere on any thread using {wasm::GetWasmEngine()}, which is a simple read of a global. R=jkummerow@chromium.org Bug: v8:11879 Change-Id: I13afb8ca3d116aa14bfaec5a4bbd6d71faa9aa17 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2969825 Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#75265} |
||
---|---|---|
.. | ||
BUILD.gn | ||
callbacks.cc | ||
DEPS | ||
finalize.cc | ||
globals.cc | ||
hostref.cc | ||
memory.cc | ||
multi-return.cc | ||
reflect.cc | ||
run-all-wasm-api-tests.cc | ||
serialize.cc | ||
startup-errors.cc | ||
table.cc | ||
testcfg.py | ||
threads.cc | ||
traps.cc | ||
wasm-api-test.h | ||
wasm-api-tests.status |