Clemens Backes 95cdb3c573 [wasm] Always use the engine allocator for decoded modules ... As Wasm module can live longer than the isolate that initially created them, it generally makes sense to use the WasmEngine's accounting allocator for the decoded WasmModule. Instead of passing that allocator through many functions, we can just get it directly from the one global WasmEngine when we need it. R=ahaas@chromium.org Change-Id: I552f8e19072f2305a3186b821c2f5b3969eac83f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4071464 Reviewed-by: Andreas Haas <ahaas@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#84611}		2022-12-02 12:22:06 +00:00
..
BUILD.gn	[tools][wasm] Add "wami", the Wasm Module Inspector	2022-07-05 04:45:28 +00:00
code-size-factors.py	[wasm] Tweak constants for estimating code space size	2022-03-15 14:41:13 +00:00
module-inspector.cc	[wasm] Always use the engine allocator for decoded modules	2022-12-02 12:22:06 +00:00
update-wasm-fuzzers.sh
update-wasm-spec-tests.sh	[wasm] Remove SIMD proposal tests	2022-04-28 05:22:59 +00:00
wasm-import-profiler-end.js
wasm-import-profiler.js