-
Clemens Backes authored
This extends the existing wasm profiling test to also check that wasm-to-js and js-to-wasm wrappers appear in the profiles as expected. It thus serves as a regression test for the status quo. R=bmeurer@chromium.org Bug: chromium:1054386 Change-Id: I5d4d8e6a252c6eb266b910621fca43a6ff0837bd Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2066970Reviewed-by: Benedikt Meurer <bmeurer@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/master@{#66401}
78defee4
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
benchmarks | ||
cctest | ||
common | ||
debugger | ||
debugging | ||
fuzzer | ||
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 |