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: | Derick Rethans | Date: | Tue, 05 Oct 2004 17:23:34 +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 | Groups: | php.cvs |
| Request: | Send a blank email to php-cvs+get-28903@lists.php.net to get a copy of this message | ||
On Tue, 5 Oct 2004, Nuno Lopes wrote:
> > Yes, 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 as opposed to
> > the 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.
Derick
--
Derick Rethans
http://derickrethans.nl | http://ez.no | http://xdebug.org