63bff6b94b
After the latest fix (https://crrev.com/c/4118547), it could happen that we stop execution even though the stored "max steps" counter did not reach zero. This was previously not possible because we did always subtract 1, and only terminated once we reached zero. Not we sometimes subtract bigger numbers, and terminate if the counter is smaller than the number we want to subtract. This CL fixes this by first subtracting, and then checking if the counter ran negative. R=thibaudm@chromium.org Bug: chromium:1405322 Change-Id: I19d7be263b000eb0a6319aaeb8838d11b8c5a3b2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4165602 Reviewed-by: Thibaud Michaud <thibaudm@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Cr-Commit-Position: refs/heads/main@{#85317} |
||
|---|---|---|
| .. | ||
| README.md | ||
| regress-1115431.wasm | ||
| regress-1405322.wasm | ||
| regression-761784.wasm | ||
| valid.wasm | ||
All files in this directory are used by the trybots to check that the fuzzer executes correctly, see https://github.com/v8/v8/blob/master/test/fuzzer/README.md. There should be at least one file in this directory, e.g. this README file.