Move CallContext construction into a interpreter instruction

This will allow us to further cut down on function call
overhead. To make this work, introduce a proper distinction
between EvalCode and GlobalCode and use the correct
compilation mode in all places.

Change-Id: I070621142159b7416026347c9239200c5ed7a56b
Reviewed-by: Simon Hausmann <[email protected]>

1 files changed, 0 insertions, 3 deletions

diff --git a/src/qml/jsruntime/qv4function_p.h b/src/qml/jsruntime/qv4function_p.h
index d845eec4d9..c3b21b1685 100644
--- a/src/qml/jsruntime/qv4function_p.h
+++ b/src/qml/jsruntime/qv4function_p.h
@@ -106,9 +106,6 @@ struct Q_QML_EXPORT Function {
 private:
     static ReturnedValue call(CallData *callData, Function *function)
     {
-        if (!function->canUseSimpleCall)
-            callData->context = ExecutionContext::newCallContext(static_cast<Heap::ExecutionContext *>(callData->context.m()), function, callData);
-
         return function->execute(callData);
     }
 };