- 20 Oct, 2021 2 commits
-
-
Shu-yu Guo authored
--no-stress-flush-bytecode doesn't exist and should be --no-stress-flush-code. Not supressing it means a tester could pass --stress-flush-code and --no-flush-bytecode, which are contradictory and will assert. Bug: v8:12331 Cq-Include-Trybots: luci.v8.try:v8_numfuzz_dbg_ng,v8_numfuzz_ng Change-Id: I6490271bcb11f5ea925eb8b65fbe0455c2dafeaf Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3233952Reviewed-by:
Zhi An Ng <zhin@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Auto-Submit: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#77483}
-
Shu-yu Guo authored
These tests depend on predictable optimize/deoptimize movements. --no-stress-flush-bytecode and --no-flush-bytecode ensure the feedback vector is not flushed, causing unexpected deoptimizations. Bug: v8:12328, v8:12311 Change-Id: I2eb7575e8c943a92c907831d4d66d2b0c9716869 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3232825Reviewed-by:
Leszek Swirski <leszeks@chromium.org> Commit-Queue: Shu-yu Guo <syg@chromium.org> Cr-Commit-Position: refs/heads/main@{#77478}
-
- 22 Jul, 2021 1 commit
-
-
Ross McIlroy authored
And use it to remove the set of TurboProp test skips. BUG=v8:9684,v8:12013 Change-Id: I878e2b9c595449c954735290959d3b38eead5a5b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3043963 Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Reviewed-by:
Mythri Alle <mythria@chromium.org> Cr-Commit-Position: refs/heads/master@{#75865}
-
- 07 Jun, 2021 1 commit
-
-
Paolo Severini authored
The tests are not compatible with the --stress-background-compile flag. Bug: v8:11821 Change-Id: Iecef6a2838109fddc9f0ecc145a9f8971bc9bc3c Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2918214Reviewed-by:
Georg Neis <neis@chromium.org> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Cr-Commit-Position: refs/heads/master@{#74959}
-
- 25 May, 2021 1 commit
-
-
Paolo Severini authored
Fixes an issue with tests mjsunit/compiler/call-with-arraylike-or-spread* that fail when run with the fuzzer. Bug: v8:11821 Change-Id: I6b75c065397d66062a7f552198ca92d151d89a4b Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2917814Reviewed-by:
Georg Neis <neis@chromium.org> Reviewed-by:
Michael Achenbach <machenbach@chromium.org> Commit-Queue: Paolo Severini <paolosev@microsoft.com> Cr-Commit-Position: refs/heads/master@{#74764}
-
- 24 May, 2021 1 commit
-
-
Paolo Severini authored
CallWithArrayLike was optimized in TF only for 'arguments' in inlined functions. Here we add logic to optimize also in non inlined functions, enabling the rewriting of Function.prototype.apply(f, [1, 2, 3]) as f(1, 2, 3). Bug: v8:9974 Change-Id: Icc9ccfc2276f75d06755176b55e7a02ddfdb04ed Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2805623 Commit-Queue: Paolo Severini <paolosev@microsoft.com> Reviewed-by:
Georg Neis <neis@chromium.org> Cr-Commit-Position: refs/heads/master@{#74723}
-