65893d84e5
Some types of supported low-level write barrier only requires passing a slot, which may not be even part of a heap object but stack. This complicates the situation, as even with caged heap, there's no way to distinguish a stack and heap slot. Solve this by passing an optional callback that can lazy be used to get the heap. This can be used by the embedder to retrieve the heap from e.g. TLS if needed. This aligns the barrier with Oilpan in Blink. Bug: chromium:1056170 Change-Id: I1e5d022ab17a2614a67b6ef39ed12691bcbd0ac6 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2675924 Reviewed-by: Ulan Degenbaev <ulan@chromium.org> Reviewed-by: Omer Katz <omerkatz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/master@{#72550}
11 lines
302 B
Python
11 lines
302 B
Python
include_rules = [
|
|
# v8-inspector-protocol.h depends on generated files under include/inspector.
|
|
"+inspector",
|
|
"+cppgc/common.h",
|
|
# Used by v8-cppgc.h to bridge to cppgc.
|
|
"+cppgc/custom-space.h",
|
|
"+cppgc/internal/process-heap.h",
|
|
"+cppgc/internal/write-barrier.h",
|
|
"+cppgc/visitor.h",
|
|
]
|