Get rid of CallData in the ExecutionContext

Part 1, where the callData member is moved to CallContext. We'll
get rid of it there in a subsequent commit.

Change-Id: I6218992802133913f7766ebb3d2f47bd29f33907
Reviewed-by: Erik Verbruggen <erik.verbruggen@qt.io>

1 files changed, 0 insertions, 2 deletions

diff --git a/src/qml/jsruntime/qv4context.cpp b/src/qml/jsruntime/qv4context.cpp
index 96f668f168..fbcfcc3460 100644
--- a/src/qml/jsruntime/qv4context.cpp
+++ b/src/qml/jsruntime/qv4context.cpp
@@ -95,7 +95,6 @@ Heap::ExecutionContext *ExecutionContext::newWithContext(Heap::Object *with)
     c->outer.set(engine(), d());
     c->activation.set(engine(), with);
 
-    c->callData = d()->callData;
     c->v4Function = d()->v4Function;
 
     return c;
@@ -156,7 +155,6 @@ void Heap::CatchContext::init(ExecutionContext *outerContext, String *exceptionV
 {
     Heap::ExecutionContext::init(Heap::ExecutionContext::Type_CatchContext);
     outer.set(internalClass->engine, outerContext);
-    callData = outer->callData;
     v4Function = outer->v4Function;
 
     this->exceptionVarName.set(internalClass->engine, exceptionVarName);