e84ac8bc3b
In a follow-up CL, the backing stores will, when the sandbox is enabled, be referenced from V8 objects through offsets rather than raw pointers. For that to work, all backing stores must be located inside the virtual memory cage. This CL prepares for that. Bug: chromium:1218005 Change-Id: Ibb989626ed7094bd4f02ca15464539f4e2bda90f Cq-Include-Trybots: luci.v8.try:v8_linux64_heap_sandbox_dbg_ng Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3114136 Commit-Queue: Samuel Groß <saelo@chromium.org> Reviewed-by: Igor Sheludko <ishell@chromium.org> Reviewed-by: Leszek Swirski <leszeks@chromium.org> Reviewed-by: Camillo Bruni <cbruni@chromium.org> Reviewed-by: Andreas Haas <ahaas@chromium.org> Cr-Commit-Position: refs/heads/main@{#76486} |
||
|---|---|---|
| .. | ||
| BUILD.gn | ||
| DEPS | ||
| mkgrokdump.cc | ||
| mkgrokdump.status | ||
| README | ||
| testcfg.py | ||
If you change the heap layout, expect this test to fail (in CQ). You will then need to build x64 release and run `<outdir>/mkgrokdump > tools/v8heapconst.py` to rebaseline.