Re: cvs: php-src /ext/session session.c /ext/spl spl_array.c /ext/standard array.c basic_functions.c ZendEngine2 Zend.m4 zend_API.h
zend_compile.c zend_compile.h zend_execute.c zend_exe
| From: | Andi Gutmans | Date: | Tue, 05 Oct 2004 20:02:53 +0000 |
| Subject: | Re: cvs: php-src /ext/session session.c /ext/spl spl_array.c /ext/standard array.c basic_functions.c ZendEngine2 Zend.m4 zend_API.h zend_compile.c zend_compile.h zend_execute.c zend_exe |
||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-28908@lists.php.net to get a copy of this message | ||
At 07:23 PM 10/5/2004 +0200, Derick Rethans wrote:
On Tue, 5 Oct 2004, Nuno Lopes wrote:Yep. AndiYes, I agree with Derickk that it's too soon to document. In general the explanation is: CALL - Uses function handlers for opcodes. SWITCH - Uses switch() statement for opcode dispatchment GOTO - Uses goto for opcode dispatchment (threaded opcodes architecture). GOTO is usually (depends on CPU and compiler) faster than SWITCH which tends to be slightly faster than CALL. CALL is default because it doesn't take very long to compile asopposed tothe other two and in general the speed is quite close to the others.Thanks for the explanation, Andi! For a regular user, with a standard gcc compiler, should he choose the GOTO method or CALL? I would say to just stick to the default until this is benchmarked "for real" with real applications. It's hard to say which one is better at this time.