Yes, we can do that, we can also try to go in and out from the computed goto core if available.
Daniel Grunblatt. On Tue, 30 Jul 2002, Dan Sugalski wrote: > At 10:34 PM -0300 7/29/02, Daniel Grunblatt wrote: > >On Mon, 29 Jul 2002, Nicholas Clark wrote: > > > As you can see from the patch all it does is implement the end > >and noop ops. > >> Everything else is being called. Interestingly, JITing like this is slower > >> than computed goto: > > > >Yes, function calls are generally slower than computing a goto. > > Yup. There's the function preamble and postamble that get executed, > which can slow things down relative to computed goto, which doesn't > have to execute them. > > This brings up an interesting point. Should we consider making at > least some of the smaller utility functions JITtable? Not the opcode > functions, but things in string.c or pmc.c perhaps. (Or maybe getting > them inlined would be sufficient for us) > -- > Dan > > --------------------------------------"it's like this"------------------- > Dan Sugalski even samurai > [EMAIL PROTECTED] have teddy bears and even > teddy bears get drunk >
