58ebbf3475
The spec specifies that a non-true return values from the trap functions should be treated as error in the strict mode. With the new lazy feedback effort inferring the language mode is expensive and causes regression on these tests. Since the test doesn't actually need to test this, fixing them to return true would help test the performance of calling the trap without the unnecessary overhead of inferring the language mode. Bug: chromium:925289 Change-Id: Ib650c3210ee260296257ae3b56174099a5492675 Reviewed-on: https://chromium-review.googlesource.com/c/1462959 Commit-Queue: Mythri Alle <mythria@chromium.org> Reviewed-by: Maya Lekova <mslekova@chromium.org> Cr-Commit-Position: refs/heads/master@{#59505} |
||
---|---|---|
.. | ||
benchmarks | ||
cctest | ||
common | ||
debugger | ||
fuzzer | ||
inspector | ||
intl | ||
js-perf-test | ||
memory | ||
message | ||
mjsunit | ||
mkgrokdump | ||
mozilla | ||
preparser | ||
test262 | ||
torque | ||
unittests | ||
wasm-js | ||
wasm-spec-tests | ||
webkit | ||
BUILD.gn |