[heap] Several implication rules for third party heap

Bug: v8:11641
Change-Id: I2b7fb85fa4e2890787981af1559f535b76ec8b05
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2849815Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Reviewed-by: Dominik Inführ <dinfuehr@chromium.org>
Commit-Queue: Wenyu Zhao <wenyu.zhao@anu.edu.au>
Cr-Commit-Position: refs/heads/master@{#74216}

BUILD.gn

@@ -384,6 +384,12 @@ if (v8_enable_atomic_object_field_writes == "") {
 if (v8_enable_atomic_marking_state == "") {
   v8_enable_atomic_marking_state = v8_enable_concurrent_marking
 }
+if (v8_enable_third_party_heap) {
+  v8_disable_write_barriers = true
+  v8_enable_single_generation = true
+  v8_enable_shared_ro_heap = false
+  v8_enable_pointer_compression = false
+}
 assert(!v8_enable_concurrent_marking || v8_enable_atomic_object_field_writes,
        "Concurrent marking requires atomic object field writes.")
 assert(!v8_enable_concurrent_marking || v8_enable_atomic_marking_state,

src/flags/flag-definitions.h

@@ -383,6 +383,11 @@ DEFINE_IMPLICATION(lite_mode, optimize_for_size)
 DEFINE_NEG_IMPLICATION(enable_third_party_heap, inline_new)
 DEFINE_NEG_IMPLICATION(enable_third_party_heap, allocation_site_pretenuring)
 DEFINE_NEG_IMPLICATION(enable_third_party_heap, turbo_allocation_folding)
+DEFINE_NEG_IMPLICATION(enable_third_party_heap, concurrent_recompilation)
+DEFINE_NEG_IMPLICATION(enable_third_party_heap, concurrent_inlining)
+DEFINE_NEG_IMPLICATION(enable_third_party_heap,
+                       finalize_streaming_on_background)
+DEFINE_NEG_IMPLICATION(enable_third_party_heap, use_marking_progress_bar)
 
 DEFINE_BOOL_READONLY(enable_third_party_heap, V8_ENABLE_THIRD_PARTY_HEAP_BOOL,
                      "Use third-party heap")