Related articles |
---|
Made compiler/now how to make interpreter faster? swoo@pobox.com (1997-12-10) |
Re: Made compiler/now how to make interpreter faster? marlet@irisa.fr (1997-12-12) |
Re: Made compiler/now how to make interpreter faster? johncrow@mindspring.com (1997-12-12) |
Re: Made compiler/now how to make interpreter faster? dlmoore@ix.netcom.com (David L Moore) (1997-12-12) |
Re: Made compiler/now how to make interpreter faster? anton@mips.complang.tuwien.ac.at (1997-12-12) |
From: | marlet@irisa.fr (Renaud Marlet) |
Newsgroups: | comp.compilers |
Date: | 12 Dec 1997 14:43:58 -0500 |
Organization: | IRISA, Campus de Beaulieu, 35042 Rennes Cedex, FRANCE |
References: | 97-12-064 |
Keywords: | performance, interpreter |
> 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.
Renaud Marlet
--
Return to the
comp.compilers page.
Search the
comp.compilers archives again.