Jason Gloudon wrote:
On Mon, Nov 04, 2002 at 09:21:06PM +0000, Nicholas Clark wrote:
It turns out the optimization does make a difference for gcc at least, but for a strange reason. It seems that without optimization gcc allocates a *lot* more space on the stack for cg_core. I suspect this is because gcc does not coalesce the stack space used for temporary values unless optimization is enabled.
I never figured out, where this stack space was used. Anyway my last patch should improve the unoptimized case due to faster trace_system_stack by putting lo_var_ptr beyond this jump table.
(gcc with no optimization) M op/s: 14.783200(gcc -O2) M op/s: 6.642035
Numbers reversed? leo
