New mjsunit tests for the new compiler infrastructure. They...

New mjsunit tests for the new compiler infrastructure. They
are in a separate subdirectory called 'compiler' in the mjsunit directory.


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

[Kevin Millikin (Chromium), 2009-10-14 08:29:01]

LGTM, but you may want to 'inline' (as strings passed to eval) the bodies of the
functions in literals-assignment for now.

http://codereview.chromium.org/273039/diff/1/3
File test/mjsunit/compiler/literals-assignment.js (right):

http://codereview.chromium.org/273039/diff/1/3#newcode32
Line 32: assertEquals(8, f1());
This won't hit the initial compiler implementation without evaling a string (the
body of fl).

[fschneider, 2009-10-14 09:19:07]

On 2009/10/14 08:29:01, Kevin Millikin wrote:
> LGTM, but you may want to 'inline' (as strings passed to eval) the bodies of
the
> functions in literals-assignment for now.
>

Done.
 
> http://codereview.chromium.org/273039/diff/1/3
> File test/mjsunit/compiler/literals-assignment.js (right):
> 
> http://codereview.chromium.org/273039/diff/1/3#newcode32
> Line 32: assertEquals(8, f1());
> This won't hit the initial compiler implementation without evaling a string
(the
> body of fl).

For now I changed the test functions to be anonymous functions applied directly.
They pass all tests.