84e470845a
The existing implementation of `serialize` in the C-API is to produce a snapshot of the current state of the `NativeModule`. However, so far all users of `serialize` did not care about the runtime of `serialize`, but cared about `deserialize` starting up fast. With this CL all functions of a module get tiered up to TurboFan before serializing the module. R=clemensb@chromium.org Change-Id: Icaef846e33509d90b38559c0b689f798d35a98db Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4129495 Commit-Queue: Andreas Haas <ahaas@chromium.org> Reviewed-by: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#85052} |
||
---|---|---|
.. | ||
benchmarks | ||
bigint | ||
cctest | ||
common | ||
debugger | ||
debugging | ||
fuzzer | ||
fuzzilli | ||
inspector | ||
intl | ||
js-perf-test | ||
memory | ||
message | ||
mjsunit | ||
mkgrokdump | ||
mozilla | ||
test262 | ||
torque | ||
unittests | ||
wasm-api-tests | ||
wasm-js | ||
wasm-spec-tests | ||
webkit | ||
BUILD.gn | ||
OWNERS |