On Tue, Feb 11, 2003 at 10:49:14AM +0100, Leopold Toetsch wrote: > Leopold Toetsch wrote: > > >Nicholas Clark wrote: > > >>Inside a cgoto core have 1 extra op - enter JITted section. > > >Or go the other way round: Run from JIT. If there is a sequence of non > >JITable ops, convert these to a CGP section, which returns to JIT when > >finished. This would save a lot of function calls to jit_normal_op.
I failed to follow most of the specific details, and all of the x86 specific stuff. > So we would not have any function call overhead and getting the best > performance by combining the 2 fastest run cores. > > This approach would of course need some architecture/compiler specific > hacks, but JIT is such a hack anyway. OTOH it is almost totally > encapsulated in the architecture jit file, so it *can* be implemented > but there is no need to do so. > > Comments welcome, The idea actually works at all? And it goes faster than the prederef computed goto core? So, in comparison, how fast is Python... Nicholas Clark
