Sara Golemon wrote:
>> Today I built PHP 4.4.4, PHP 5.0.5, PHP 5.1.6, and current PHP_5_2
>> (the last two each with CALL, GOTO, and SWITCH VMs) with GCC 3.4.6
>> and GCC 4.1.1 with -O{0|1|2|3|s} [1].
>>
> That's a nice trick considering that PHP4 doesn't have a CALL or
> GOTO vm.
Please read the
Today I built PHP 4.4.4, PHP 5.0.5, PHP 5.1.6, and current PHP_5_2 (the
last two each with CALL, GOTO, and SWITCH VMs) with GCC 3.4.6 and
GCC 4.1.1 with -O{0|1|2|3|s} [1].
That's a nice trick considering that PHP4 doesn't have a CALL or GOTO vm...
These results also beg the question how we
Given the tricky nature of enabling different execution modes I'd be
very surprised to see people use non-default values, so to your
answer of how well tested other executors are, I'd say not a whole lot.
On 15-Oct-06, at 9:21 AM, Sebastian Bergmann wrote:
Sebastian Bergmann wrote:
What s
Sebastian Bergmann wrote:
> What strikes me as odd are the segmentation faults when PHP is built
> with -O0 (no optimizations).
Some more information of the segfaults: It looks as if the ackermann
test is responsible for the segfaults.
I uploaded a backtrace from GDB and a logfile from valgrin
Today I built PHP 4.4.4, PHP 5.0.5, PHP 5.1.6, and current PHP_5_2 (the
last two each with CALL, GOTO, and SWITCH VMs) with GCC 3.4.6 and
GCC 4.1.1 with -O{0|1|2|3|s} [1].
CFLAGS: -march=pentium-m -msse3 -O{0|1|2|3|s} -pipe
configure options: --disable-cgi --disable-all
I let each of the re
