From 12b22b51985508dddbcb94c05268f0e11a54f26c Mon Sep 17 00:00:00 2001
From: Georg Neis <neis@chromium.org>
Date: Tue, 1 Oct 2019 13:26:55 +0200
Subject: [PATCH] Disable --instruction-scheduling for mksnapshot

This is an experiment to see the memory/performance impact.

Bug: v8:9775
Change-Id: I2ae61ae8bb5c6c1c55436e96c4b2d8201cbf4739
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/1832177
Reviewed-by: Michael Stanton <mvstanton@chromium.org>
Commit-Queue: Georg Neis <neis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#64062}
---
 BUILD.gn | 1 -
 1 file changed, 1 deletion(-)

diff --git a/BUILD.gn b/BUILD.gn
index ee1b5b218f..8d2d540905 100644
--- a/BUILD.gn
+++ b/BUILD.gn
@@ -1223,7 +1223,6 @@ template("run_mksnapshot") {
       "./" + rebase_path(get_label_info(":mksnapshot($v8_snapshot_toolchain)",
                                         "root_out_dir") + "/mksnapshot",
                          root_build_dir),
-      "--turbo_instruction_scheduling",
 
       # In cross builds, the snapshot may be generated for both the host and
       # target toolchains.  The same host binary is used to generate both, so