Add the for statement back into the set of things the...

Add the for statement back into the set of things the
non-optimizing compiler can cope with.  By default it bails out
to the old compiler on encountering a for loop (for performance)
but with this change the --always-fast-compiler flag will enable
functions with for loops to be compiled in the non-optimizing
compiler.  Also enables the non-optimizing compiler on functions
that can be lazily compiled (again only with the flag).

Committed: http://code.google.com/p/v8/source/detail?r=3667

[fschneider, 2010-01-20 15:10:43]

LGTM.

http://codereview.chromium.org/552065/diff/1/2
File test/mjsunit/debug-step.js (right):

http://codereview.chromium.org/552065/diff/1/2#newcode82
test/mjsunit/debug-step.js:82: Debug.setListener(null);
This file did not change, right?

[Erik Corry, 2010-01-20 21:25:03]

http://codereview.chromium.org/552065/diff/1/2
File test/mjsunit/debug-step.js (right):

http://codereview.chromium.org/552065/diff/1/2#newcode82
test/mjsunit/debug-step.js:82: Debug.setListener(null);
On 2010/01/20 15:10:43, fschneider wrote:
> This file did not change, right?

There was a missing newline on the last line, which this patch fixes.