DS>>The problem in stack overflow.
DS>>We will see how this can be fixed without performance lost.
I think it might be time to go easier on stack - maybe consider to make
specialized fixed-size allocators for frequently used structures to avoid
performance hits - it seems that PHP uses a lot of
Dmitry Stogov wrote:
> Do you use x86 (non x86-64)?
> What is your ./configure options?
Intel(R) Pentium(R) M Processor 1500MHz / 1024 KB Cache / 512 MB RAM
Linux 2.6.11-gentoo-r11
CFLAGS="-march=pentium-m -O2 -pipe"
./configure --disable-cgi --disable-all
--
Sebastian Bergmann
> Sent: Monday, June 13, 2005 12:49 AM
> To: internals@lists.php.net
> Subject: [PHP-DEV] CALL and SWITCH executors segfault
>
>
> Tonight I wanted to do some benchmarks with PHP 4.3.11, PHP
> 5.0.4, and the three (CALL, GOTO, SWITCH) executors of PHP
> 5.1 with both GCC
Sebastian Bergmann wrote:
> Tonight I wanted to do some benchmarks with PHP 4.3.11, PHP 5.0.4, and
> the three (CALL, GOTO, SWITCH) executors of PHP 5.1 with both GCC 3.4.4
> and GCC 4.0.1 to get a feeling for the improvements in the VM for
> PHP 5.1.
Initial results are here [1].
> Both the CAL
Tonight I wanted to do some benchmarks with PHP 4.3.11, PHP 5.0.4, and
the three (CALL, GOTO, SWITCH) executors of PHP 5.1 with both GCC 3.4.4
and GCC 4.0.1 to get a feeling for the improvements in the VM for
PHP 5.1.
Both the CALL and SWITCH executors segfault for me on my Linux system
when
