b0209cc1ee
This speeds up the check by ~10x. This was tested by writing a simple test that compares a for-loop and array.every(): for (var i = 0; i < kMemSize; i++) { assertEquals(0, array[i]); } assertTrue(array.every((e => e == 0))); The for-loop takes ~180s, every() takes ~19s. Numbers above are for arm.debug build (simulator). On x64.debug builds we can see a similar 10x improvement, from ~6s to ~400ms. Bug: v8:7783 Bug: v8:9396 Change-Id: I83d46c7ec4a634612032c1d79585339cadb8b641 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1793904 Commit-Queue: Zhi An Ng <zhin@chromium.org> Reviewed-by: Clemens Hammacher <clemensh@chromium.org> Reviewed-by: Michael Starzinger <mstarzinger@chromium.org> Cr-Commit-Position: refs/heads/master@{#63691} |
||
---|---|---|
.. | ||
benchmarks | ||
cctest | ||
common | ||
debugger | ||
fuzzer | ||
inspector | ||
intl | ||
js-perf-test | ||
memory | ||
message | ||
mjsunit | ||
mkgrokdump | ||
mozilla | ||
preparser | ||
test262 | ||
torque | ||
unittests | ||
wasm-api-tests | ||
wasm-js | ||
wasm-spec-tests | ||
webkit | ||
BUILD.gn | ||
OWNERS |