[turbofan] Temporary workaround for JSInliner zone.

This is exactly what it looks like. A temporary hack that ensures we
can make forward progress with the JSInliner despite other components
have a hard time picking the correct zone. This hack is a hack!

R=bmeurer@chromium.org,jarin@chromium.org

Review URL: https://codereview.chromium.org/1410963003

Cr-Commit-Position: refs/heads/master@{#31380}

src/compiler/js-inlining.cc

@@ -318,8 +318,12 @@ Reduction JSInliner::ReduceJSCallFunction(Node* node,
     return NoChange();
   }
 
-  Zone zone;
-  ParseInfo parse_info(&zone, function);
+  // TODO(mstarzinger): The correct thing would be to use a local zone here for
+  // the inner graph. This however leads to Zone-Types being allocated in the
+  // wrong zone and makes the engine explode at high speeds. Explosion bad!
+  // Zone zone;
+  // ParseInfo parse_info(&zone, function);
+  ParseInfo parse_info(jsgraph_->zone(), function);
   CompilationInfo info(&parse_info);
   if (info_->is_deoptimization_enabled()) {
     info.MarkAsDeoptimizationEnabled();