|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 (John Crow)|
|Date:||12 Dec 1997 14:45:39 -0500|
|Organization:||Zippo News Service [http://www.zippo.com]|
On 10 Dec 1997 00:37:54 -0500, firstname.lastname@example.org wrote:
>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
There is extensive literature on the subject of interpreter
optimization in the Forth community --- you might want to start
looking at www.forth.org. I seem to recall having read some fairly
informative papers on the subject by Anton Ertl and Bernd Paysan
dealing with various threading techniques. Forth, in general, is of
particular interest to interpreter designers because (properly
implemented) it is among the fastest of interpreted languages.
>Compared to plain C code the interpreter is much much
>slower, about 50-100x for a repeated loop, which seems pretty poor.
That is pretty poor. How are you implementing your loops?
Return to the
Search the comp.compilers archives again.