|Use inner global object for function lookup|
|Reported by email@example.com, Oct 21 2008||Back to list|
codegen-ia32.cc: VisitCall, for case 'foo(1,2,3)', the global proxy object is used as receiver for both method lookup and invocation. This has performance overhead because method lookup on the proxy object needs security checks. This can be improved by using the JSGlobalObject for method lookup, and pass JSGlobalProxy as 'this' to invocation.
Oct 22 2008,
There's also a 10-15% performance regression on function call intensive benchmarks, because of the indirect way we load the global receiver before calling functions (the split window change added one extra level of indirection). This should be resolved too.
Oct 23 2008,
Oct 27 2008,
Fixed on bleeding_edge branch in revision 607.
Mar 23 2017,
|► Sign in to add a comment|