Correctly mark functions from our natives files during compilation.
authorager@chromium.org <ager@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 19 Jul 2011 08:19:31 +0000 (08:19 +0000)
committerager@chromium.org <ager@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 19 Jul 2011 08:19:31 +0000 (08:19 +0000)
commit85f5afb717a19a1213782db749563c17a38d750d
tree1c0994af716226a523bd349f1e064624e9501f39
parent645bb1b1ba20ff6e14aae745da00ef922f6df3ed
Correctly mark functions from our natives files during compilation.

When creating a CompilationInfo we always have the script and can
determine if it is a natives script.

Now that all natives functions are recognized as such, many of them
are called with undefined as the receiver. We have to use different
filtering for builtins functions when printing stack traces.

Also, fixed one call of CALL_NON_FUNCTION to be correctly marked as a
method call (with fixed receiver). Now that CALL_NON_FUNCTION is
marked as a native function this caused the receiver to be undefined.

R=svenpanne@chromium.org
BUG=
TEST=

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8680 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/arm/code-stubs-arm.cc
src/compiler.cc
src/compiler.h
src/ia32/code-stubs-ia32.cc
src/messages.js
src/mips/code-stubs-mips.cc
src/runtime.cc
src/x64/code-stubs-x64.cc
test/mjsunit/regress/regress-798.js