Nicholas Clark wrote: > I'm not convinced. Compiling the computed goto core with any sort of > optimisation turns on *really* hurts the machine. I think it's over a > minute even a 733 MHz PIII, and it happily pages everything else out while > it's doing it. :-(
Use the "-fno-gcse" option to gcc, to turn off global common subexpression elimination. That may help with the speed issue. GCSE messes up interpreter loops anyway. I found out the hard way on Portable.NET that GCSE makes the code perform worse, not better. The compiler gets too greedy about common code, and starts moving things that should stay inline. GCSE is great in normal code, but not the central interpreter loop. Cheers, Rhys.
