d9b0cc3c8e
Client isolates need the incremental marking barrier for objects in the shared heap. The marking barrier for the shared heap can be enabled either with or without incremental marking in the client isolate's local heap. Client isolates get a new marking worklist in the MarkingBarrier class for marking of shared objects. Shared objects will always be pushed into that worklist for tracing. MarkingBarrier can be enabled for shared marking and/or marking of local isolates. Bug: v8:13267 Change-Id: I0b60134432de9af3c76e24620816555ee49da1eb Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4001768 Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Dominik Inführ <dinfuehr@chromium.org> Auto-Submit: Dominik Inführ <dinfuehr@chromium.org> Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#84202} |
||
---|---|---|
.. | ||
benchmarks | ||
bigint | ||
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 |