[async-iteration] add support for for-await-of loops in Async Functions

src/interpreter/interpreter-intrinsics.cc

Index: src/interpreter/interpreter-intrinsics.cc
diff --git a/src/interpreter/interpreter-intrinsics.cc b/src/interpreter/interpreter-intrinsics.cc
index a2820fb1286aeb49f52f0ced856fee705929e3af..49eb8b0c01cff1c412bc1781ede2f2de9990bbf6 100644
--- a/src/interpreter/interpreter-intrinsics.cc
+++ b/src/interpreter/interpreter-intrinsics.cc
@@ -398,6 +398,16 @@ void IntrinsicsHelper::AbortIfArgCountMismatch(int expected, Node* actual) {
   __ Bind(&match);
 }
 
+Node* IntrinsicsHelper::CreateAsyncFromSyncIterator(Node* args_reg,
+                                                    Node* arg_count,
+                                                    Node* context) {
+  // TODO(caitp): split AsyncFromSyncIterator functionality out of
+  //              https://codereview.chromium.org/2622833002
+  __ CallRuntime(Runtime::kAbort, __ SmiConstant(kGetIterator),
+                 __ NoContextConstant());

[rmcilroy, 2017/01/20 10:34:01]

Could we avoid adding this as an intrinsic that just calls a runtime call and
just call the runtime function itself?

[neis, 2017/01/20 14:38:15]

If this will be implemented in a separate CL, please note that in the
description of this CL.

[caitp, 2017/01/20 20:17:19]

I would have thought the TODO() indicated this. I think, for now, I'll leave the
interpreter intrinsics untouched and just call the runtime directly from
bytecode-generator, as rmcilroy is asking

[neis, 2017/01/24 12:55:45]

Sure, but many people read the CL description while only a few read the code.

+  return __ UndefinedConstant();
+}
+
 }  // namespace interpreter
 }  // namespace internal
 }  // namespace v8