9554743a0b
The stack object is primarily used for conservative stack scanning, both by the V8 and C++ garbage collectors. This CL introduces the notion of a "stack context", which comprises of the current stack marker (the lowest address on the stack that may contain interesting pointers) and the values of the saved registers. It simplifies the way in which iteration through the stack is invoked: the context must have previously been saved and iteration always uses the stack marker. Bug: v8:13257 Bug: v8:13493 Change-Id: Ia99ef702eb6ac67a3bcd006f0edf5e57d9975ab2 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4017512 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Reviewed-by: Omer Katz <omerkatz@chromium.org> Commit-Queue: Nikolaos Papaspyrou <nikolaos@chromium.org> Cr-Commit-Position: refs/heads/main@{#84303} |
||
---|---|---|
.. | ||
access-check-unittest.cc | ||
accessor-unittest.cc | ||
api-icu-unittest.cc | ||
api-wasm-unittest.cc | ||
context-unittest.cc | ||
deserialize-unittest.cc | ||
exception-unittest.cc | ||
gc-callbacks-unittest.cc | ||
interceptor-unittest.cc | ||
isolate-unittest.cc | ||
remote-object-unittest.cc | ||
resource-constraints-unittest.cc | ||
v8-maybe-unittest.cc | ||
v8-object-unittest.cc | ||
v8-script-unittest.cc |