-
Michael Lippautz authored
The marking verifier used to run on a different stack than the marker which could lead to it finding more objects than the marker. Fix this by recording a stack end from which the verification starts. This ensures that the verifier only finds a subset of the objects that the actual stack scan finds. Bug: v8:11709 Change-Id: I44fe7b247e56e75deded45b64c25379f1ad9e381 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2859848 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Omer Katz <omerkatz@chromium.org> Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#74320}
995f122e
Name |
Last commit
|
Last update |
---|---|---|
.. | ||
benchmarks | ||
cctest | ||
common | ||
debugger | ||
debugging | ||
fuzzer | ||
fuzzilli | ||
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 |