|Made compiler/now how to make interpreter faster? firstname.lastname@example.org (1997-12-10)|
|Re: Made compiler/now how to make interpreter faster? email@example.com (1997-12-12)|
|Re: Made compiler/now how to make interpreter faster? firstname.lastname@example.org (1997-12-12)|
|Re: Made compiler/now how to make interpreter faster? email@example.com (David L Moore) (1997-12-12)|
|Re: Made compiler/now how to make interpreter faster? firstname.lastname@example.org (1997-12-12)|
|From:||email@example.com (Renaud Marlet)|
|Date:||12 Dec 1997 14:43:58 -0500|
|Organization:||IRISA, Campus de Beaulieu, 35042 Rennes Cedex, FRANCE|
> I have used lex and yacc to create a parser which spits out an
> bytecode file. The bytecode file is read by the interpreter at a
> later time and executed. What are good sources for information on how
> to change the bytecode stream/interpreter/compiler for the fastest
> executing code?
You might also consider using partial evaluation techniques.
Programs that contains interpretation layers are the ideal
targets for program specializers. Please visit our web pages
for more information: http://www.irisa.fr/compose
> Compared to plain C code the interpreter is much much
> slower, about 50-100x for a repeated loop, which seems pretty poor.
Tempo, our partial evaluator for C programs, has obtained
speedups from 10 to 100 on various interpreters. I should
be publicly available at the beginning of April.
Return to the
Search the comp.compilers archives again.