From: fschneider@chromium.org <fschneider@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Date: Fri, 13 Nov 2009 10:02:32 +0000 (+0000)
Subject: Top-level compiler: Re-allow non-lazily compiled function literals.
X-Git-Tag: upstream/4.7.83~22942
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=1560b89888e6c55e7f34997ac85f56a04da2a344;p=platform%2Fupstream%2Fv8.git

Top-level compiler: Re-allow non-lazily compiled function literals.

This change re-allows non-lazy compiled function literals for top-level compilation.

There was a problem on ARM exposed through this change which was fixed as part of r3289
in fast-codegen-arm.cc (Threading and Threading2 tests failed)

It occurred before r3289 when we allocate a local context at the beginning of a function. The
code for the stack check was split up in an unintended way (load of stack check limit into r2,
and use of r2 in the actual stack check code).

Review URL: http://codereview.chromium.org/385070

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@3300 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
---

diff --git a/src/compiler.cc b/src/compiler.cc
index 0f23992..b98a931 100644
--- a/src/compiler.cc
+++ b/src/compiler.cc
@@ -759,9 +759,7 @@ void CodeGenSelector::VisitDebuggerStatement(DebuggerStatement* stmt) {
 
 
 void CodeGenSelector::VisitFunctionLiteral(FunctionLiteral* expr) {
-  if (!expr->AllowsLazyCompilation()) {
-    BAILOUT("FunctionLiteral does not allow lazy compilation");
-  }
+  // Function literal is supported.
 }