Added fast compiler support for calling JS runtime functions....

Added fast compiler support for calling JS runtime functions.

Also added a simple test that invokes a JS runtime function
in top-level code.


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

[fschneider, 2009-11-26 08:34:03]

Here's a small addition to the fast compiler.

Is test-compiler.cc the right place for testing this? Basically I need a way to
invoke a JS runtime in top-level code.

[Lasse Reichstein, 2009-11-26 10:37:44]

LGTM.
You can have an mjsunit test that allows native syntax by adding a comment line
of the form:
// Flags: --allow-natives-syntax
in the file. Check, e.g., array-sort.js

http://codereview.chromium.org/437081/diff/1/4
File src/compiler.cc (left):

http://codereview.chromium.org/437081/diff/1/4#oldcode983
src/compiler.cc:983: if (expr->function() == NULL) BAILOUT("call JS runtime
function");
On general principle, could we put an is_js_runtime_function method on
CallRuntime that tested the function against NULL, instead of having to know the
significance of a NULL function everywhere?
The name probably needs work.

[fschneider, 2009-11-27 00:27:09]

I added a separate mjsunit test now.

http://codereview.chromium.org/437081/diff/1/4
File src/compiler.cc (left):

http://codereview.chromium.org/437081/diff/1/4#oldcode983
src/compiler.cc:983: if (expr->function() == NULL) BAILOUT("call JS runtime
function");
On 2009/11/26 10:37:44, Lasse Reichstein wrote:
> On general principle, could we put an is_js_runtime_function method on
> CallRuntime that tested the function against NULL, instead of having to know
the
> significance of a NULL function everywhere?
> The name probably needs work.

Done.