Land chromium-side work to clean up handling of v8_target_cpu in the GN build.

build/toolchain/linux/BUILD.gn

Index: build/toolchain/linux/BUILD.gn
diff --git a/build/toolchain/linux/BUILD.gn b/build/toolchain/linux/BUILD.gn
index 1fe3c7d526962c62faaaf30aec73387e15c1f62a..51e26cfce4d635a1317ee029503ccb2d44042b6a 100644
--- a/build/toolchain/linux/BUILD.gn
+++ b/build/toolchain/linux/BUILD.gn
@@ -38,6 +38,12 @@ clang_toolchain("clang_x86") {
   toolchain_os = "linux"
 }
 
+clang_toolchain("clang_x86_v8_arm") {

[Michael Achenbach, 2016/07/07 07:24:23]

Should we add here the other combinations we use in v8, too? E.g. x86_v8_mipsel,
etc. Or can we make our own toolchain definitions in the v8 standalone configs?

[Dirk Pranke, 2016/07/07 17:28:12]

You can do either as you like. It might be easier to do them here for now.

[michaelbai, 2016/07/07 18:41:26]

Yes, We need define x86_v8_mipsel and x64_v8_mips64el now since you already use
them in v8 side.

+  toolchain_cpu = "x86"
+  v8_toolchain_cpu = "arm"
+  toolchain_os = "linux"
+}
+
 gcc_toolchain("x86") {
   cc = "gcc"
   cxx = "g++"
@@ -57,6 +63,12 @@ clang_toolchain("clang_x64") {
   toolchain_os = "linux"
 }
 
+clang_toolchain("clang_x64_v8_arm64") {
+  toolchain_cpu = "x64"
+  v8_toolchain_cpu = "arm64"
+  toolchain_os = "linux"
+}
+
 gcc_toolchain("x64") {
   cc = "gcc"
   cxx = "g++"