VV8 LUCI CQ[heap] Pass Isolate to metadata accessors
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
[maglev] Fix visiting stack in StackGuard call The RegisterInput (NewTarget) was not correctly visited by the GC. This: - Creates a sentinel safepoint to indicate that the stack is not fully created (we are in the stack guard call). - Generalises RegisterInputs (we assumed only NewTarget before) and save them in the graph. - Pass the register input count via tagged_register_indexes in this case. Fixed: chromium:1407606 Bug: v8:7700 Change-Id: I8f599f8c1a992ee6fd886eec1e289454649dfec8 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/4171626 Auto-Submit: Victor Gomes <victorgomes@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#85331} | 3 年前 | |
[wasm] Rename kWasmInstanceOffset frame constants Use kWasmInstanceDataOffset for wasm frames, and kWasmInstanceObjectOffset for interpreter (drumbrake) frames. R=jkummerow@chromium.org Bug: 354408144 Change-Id: I6f0d535439fd88a3dfad80510edf380af5cded10 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/5803203 Reviewed-by: Matthias Liedtke <mliedtke@chromium.org> Commit-Queue: Clemens Backes <clemensb@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Cr-Commit-Position: refs/heads/main@{#95782} | 1 年前 | |
[heap] Pass Isolate to metadata accessors Removes the implicit Isolate::Current() when looking up page metadata from a HeapObject or address, and either uses an available Isolate* or makes the Isolate::Current() explicit. There is still a MemoryChunk::Metadata() accessor which implicitly calls Isolate: :Current() -- this can be fixed in followup work. Change-Id: Ia64f1a38750f4c9c7279c631480b3ee9aadd8917 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6906859 Reviewed-by: Michael Lippautz <mlippautz@chromium.org> Auto-Submit: Leszek Swirski <leszeks@chromium.org> Commit-Queue: Leszek Swirski <leszeks@chromium.org> Cr-Commit-Position: refs/heads/main@{#102184} | 9 个月前 | |
[wasm][growable-stacks] Increase stack limit margin Wasm stack parameters can take up to about 16KB of additional stack space (a thousand SIMD parameters, minus the register parameters) that are not taken into account by stack checks. Increase the stack limit margin to 20KB (16KB + 4KB of additional safety space) to allow pushing outgoing parameters without overflowing the hard stack limit. Drive-by: fix an error in the calculation of the frame size when the stack grows. R=clemensb@chromium.org Bug: 42204615 Change-Id: I8c957b44746d701b1f3639a2bd4f317f8aa8a5ad Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/6519077 Reviewed-by: Clemens Backes <clemensb@chromium.org> Reviewed-by: Jakob Kummerow <jkummerow@chromium.org> Commit-Queue: Thibaud Michaud <thibaudm@chromium.org> Cr-Commit-Position: refs/heads/main@{#100120} | 1 年前 |