v8/test/mkgrokdump
Dominik Inführ 34d6823f8b [heap] Rename safepoint scopes
This CL simplifies safepoint scopes, there are now three kinds of
safepoint scopes:

1) IsolateSafepointScope - performs an isolate local safepoint
2) GlobalSafepointScope - a global safepoint across multiple isolates
3) SafepointScope - chooses based on condition between local/global

This CL is not supposed to change current safepointing behavior in
any way. The CL renames the current SafepointScope to
IsolateSafepointScope and changes GlobalSafepointScope to always
perform a global safepoint. It then also introduces the new
SafepointScope and makes use of it for snapshotting and in heap.cc.

Bug: v8:13267
Change-Id: Ie7e1f81b6158c98d3d98552ba735cc73c9b869c5
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/3973310
Reviewed-by: Michael Lippautz <mlippautz@chromium.org>
Commit-Queue: Dominik Inführ <dinfuehr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#83912}
2022-10-25 16:32:55 +00:00
..
BUILD.gn [build] Fold v8_wrappers into v8_libbase 2021-02-25 10:56:20 +00:00
DEPS
mkgrokdump.cc [heap] Rename safepoint scopes 2022-10-25 16:32:55 +00:00
mkgrokdump.status [sandbox] Skip mkgrokdump test in non-sandbox mode 2022-09-08 21:42:16 +00:00
README [sandbox] Update test/mkgrokdump/README 2022-09-14 17:09:49 +00:00
testcfg.py [test] Refactor testrunner (4) 2022-07-18 09:52:24 +00:00

If you change the heap layout, expect this test to fail (in CQ). You will then
need to build x64 release with v8_enable_sandbox=true and run
`<outdir>/mkgrokdump > tools/v8heapconst.py` to rebaseline.
The V8 sandbox has to be manually enabled as it is enabled by default only for
Chromium builds, but not standalone v8 builds.