ca092440f3
The C-API does not support dynamic tiering and still waits for top-tier compilation to finish before serializing code when the explicit serialize() function gets called. This means that serialize() can only finish if the kFinishedTopTierCompilation event was triggered first. With this CL the kFinishedTopTierCompilation event is also triggered after deserialization so that serialize() can work after deserialization. R=clemensb@chromium.org Bug: v8:11024 Change-Id: I3dd14e37087e3cbfbc28cb5625c9f3715f6c236b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3404773 Reviewed-by: Clemens Backes <clemensb@chromium.org> Commit-Queue: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#78719} |
||
---|---|---|
.. | ||
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 |