Support %_CallFunction in optimized code.

Support %_CallFunction in optimized code.

Also, fix a bug identified in the x64 optimizing code generator.  We
failed to restore the context to the fixed context register after the
Function.prototype.apply optimization.


R=fschneider@chromium.org

[Kevin Millikin (Chromium), 2011-04-13 13:56:29]

We already use CallFunction for Hydrogen/Lithium instructions, so I called this
InvokeFunction which reflects its implementation in the backend.

That's kind of annoying.

[Kevin Millikin (Chromium), 2011-04-13 15:23:51]

Ready for you to take a look.

[fschneider, 2011-04-13 16:59:29]

LGTM.

http://codereview.chromium.org/6838018/diff/3020/src/hydrogen.cc
File src/hydrogen.cc (right):

http://codereview.chromium.org/6838018/diff/3020/src/hydrogen.cc#newcode5535
src/hydrogen.cc:5535: ASSERT(arg_count >= 1);  // There's always at least a
receiver.
Can this also be >= 2 (receiver + function)?

[fschneider, 2011-04-15 07:58:55]

I landed this change in r7624.

On 2011/04/13 16:59:29, fschneider wrote:
> LGTM.
> 
> http://codereview.chromium.org/6838018/diff/3020/src/hydrogen.cc
> File src/hydrogen.cc (right):
> 
> http://codereview.chromium.org/6838018/diff/3020/src/hydrogen.cc#newcode5535
> src/hydrogen.cc:5535: ASSERT(arg_count >= 1);  // There's always at least a
> receiver.
> Can this also be >= 2 (receiver + function)?