Split v8_enable_concurrent_marking into two flags
The new flags are - v8_enable_atomic_object_field_writes that makes field write operations relaxed atomic. - v8_enable_atomic_marking_state that makes the marking state and the write-barrier thread-safe. The motivation is that we want to disable atomic object fields while keeping the marking states thread-safe. This allows us to increase TSAN coverage for background compilation and streaming tasks while keeping the write-barrier used by the tasks thread-safe. Bug: v8:10988 Change-Id: I11d66954dda4bf36d24c5e6f14ee5bc7a0f86094 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2448467Reviewed-by: Georg Neis <neis@chromium.org> Reviewed-by: Michael Achenbach <machenbach@chromium.org> Commit-Queue: Ulan Degenbaev <ulan@chromium.org> Cr-Commit-Position: refs/heads/master@{#70329}
Showing
Please
register
or
sign in
to comment