Disable lazy parsing inside eval (see bug).

test/mjsunit/regress/regress-5736.js

Index: test/mjsunit/regress/regress-5736.js
diff --git a/test/mjsunit/regress/regress-5736.js b/test/mjsunit/regress/regress-5736.js
new file mode 100644
index 0000000000000000000000000000000000000000..6dcc0de7f47edd7e8387a63897db02593b1727a9
--- /dev/null
+++ b/test/mjsunit/regress/regress-5736.js
@@ -0,0 +1,23 @@
+// Copyright 2016 the V8 project authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+var my_global = 0;
+
+// The problem was that we allowed lazy functions inside evals, but did not
+// force context allocation on the eval scope. Thus, foo was not context
+// allocated since we didn't realize that a lazy function referred to it.
+eval(`let foo = 1;
+      let maybe_lazy = function() { foo = 2; }
+      maybe_lazy();
+      my_global = foo;`);
+assertEquals(2, my_global);
+
+(function TestVarInStrictEval() {
+  "use strict";
+  eval(`var foo = 3;
+        let maybe_lazy = function() { foo = 4; }
+        maybe_lazy();
+        my_global = foo;`);
+  assertEquals(4, my_global);
+})();