cvs: ZendEngine2 / README.ZEND_VM

andi Wed Oct 27 14:08:56 2004 EDT Modified files: /ZendEngine2 README.ZEND_VM Log: - Tiny fixes http://cvs.php.net/diff.php/ZendEngine2/README.ZEND_VM?r1=1.3&r2=1.4&ty=u Index: ZendEngine2/README.ZEND_VM diff -u ZendEngine2/README.ZEND_VM:1.3 ZendEngine2/README.ZEND_VM:1.4 --- ZendEngine2/README.ZEND_VM:1.3 Wed Oct 27 13:58:45 2004 +++ ZendEngine2/README.ZEND_VM Wed Oct 27 14:08:56 2004 @@ -3,11 +3,11 @@ ZEND_VM architecture allows specializing opcode handlers according to op_type fields and using different execution methods (call threading, switch threading -and direct threading). As a result ZE2 got more then 20% speedup on raw PHP +and direct threading). As a result ZE2 got more than 20% speedup on raw PHP code execution (with specialized executor and direct threading execution -method). As most in most PHP applications raw execution speed isn't the -limiting factor but system calls and database callls are, your mileage with -this patch will vary. +method). As in most PHP applications raw execution speed isn't the limiting +factor but system calls and database callls are, your mileage with this patch +will vary. Most parts of the old zend_execute.c go into zend_vm_def.h. Here you can find opcode handlers and helpers. The typical opcode handler template looks @@ -40,7 +40,7 @@ return <NAME>(<VAL>, ZEND_OPCODE_HANDLER_ARGS_PASSTHRU) ZEND_VM_CONTINUE() return 0 -ZEND_VM_NEXT_OPCOD() +ZEND_VM_NEXT_OPCODE() NEXT_OPCODE() ZEND_VM_SET_OPCODE(<TARGET> SET_OPCODE(<TARGET>