-
Clemens Backes authored
Import wrappers were only logged if logging was enabled during compilation. If the profiler is enabled later, and regular wasm code is logged via {NativeModule::LogWasmCodes}, the import wrappers were missing. This CL fixes the long-standing TODO, and adds tests which triggered that code path. Those tests were hanging before because the expected functions did never appear in the profile. Drive-by: If {WasmEngine::LogOutstandingCodesForIsolate} detects that code logging is disabled by now, it should still clear the {code_to_log} vector. R=thibaudm@chromium.org Bug: chromium:1125986, chromium:1141787 Change-Id: I2566ef369bb61a09488f2d932b6c10d92e4cb12f Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2574696Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#71645}
a22e8a70
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
benchmarks | ||
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 |