Eagerly disable optimization of %_GeneratorThrow, %_GeneratorNext

src/ast-numbering.cc

Index: src/ast-numbering.cc
diff --git a/src/ast-numbering.cc b/src/ast-numbering.cc
index 784e605d747822f7814a993478d9868884e0c51f..3eae35e511bf0d23417972036c3a5172c4227674 100644
--- a/src/ast-numbering.cc
+++ b/src/ast-numbering.cc
@@ -296,6 +296,19 @@ void AstNumberingVisitor::VisitCallRuntime(CallRuntime* node) {
     // Don't try to optimize JS runtime calls because we bailout on them.
     DisableCrankshaft(kCallToAJavaScriptRuntimeFunction);
   }
+  const Runtime::Function* function = node->function();
+  if (function != NULL && function->intrinsic_type == Runtime::INLINE) {

[Michael Starzinger (Google), 2015/01/14 20:42:22]

OMG, pretty please don't. Is this known to fix the problem mentioned in the
issue or is it more a "stab in the dark"?

+    switch (function->function_id) {
+      case Runtime::kInlineGeneratorNext:
+        DisableCrankshaft(kInlinedRuntimeFunctionGeneratorNext);
+        break;
+      case Runtime::kInlineGeneratorThrow:
+        DisableCrankshaft(kInlinedRuntimeFunctionGeneratorThrow);
+        break;
+      default:
+        break;
+    }
+  }
   node->set_base_id(ReserveIdRange(CallRuntime::num_ids()));
   VisitArguments(node->arguments());
 }