Changeset 36514 in webkit for trunk/JavaScriptCore/VM/Machine.h

Timestamp:

Sep 16, 2008, 10:40:01 AM (17 years ago)

Author:

[email protected]

Message:

2008-09-16 Gavin Barraclough <​[email protected]>

Reviewed by Geoff Garen.

CTI code generation for op_ret. The majority of the work
(updating variables on the stack & on exec) can be performed
directly in generated code.

We still need to check, & to call out to C-code to handle
activation records, profiling, and full scope chains.

+1.5% Sunspider, +5/6% v8 tests.

• VM/CTI.cpp: (JSC::CTI::emitPutCTIParam): (JSC::CTI::compileOpCall): (JSC::CTI::privateCompileMainPass):
• VM/CTI.h:
• VM/Machine.cpp: (JSC::Machine::cti_op_ret_activation): (JSC::Machine::cti_op_ret_profiler): (JSC::Machine::cti_op_ret_scopeChain):
• VM/Machine.h:

File:

• trunk/JavaScriptCore/VM/Machine.h (modified) (1 diff)

trunk/JavaScriptCore/VM/Machine.h

@@ -161 +161 @@
         static void* SFX_CALL cti_op_call_JSFunction(CTI_ARGS);
         static JSValue* SFX_CALL cti_op_call_NotJSFunction(CTI_ARGS);
-        static JSValue* SFX_CALL cti_op_ret(CTI_ARGS);
+        static void SFX_CALL cti_op_ret_activation(CTI_ARGS);
+        static void SFX_CALL cti_op_ret_profiler(CTI_ARGS);
+        static void SFX_CALL cti_op_ret_scopeChain(CTI_ARGS);
         static JSValue* SFX_CALL cti_op_new_array(CTI_ARGS);
         static JSValue* SFX_CALL cti_op_resolve(CTI_ARGS);