Related articles |
---|
Efficient bytecode design and interpretation mg169780@zodiac.mimuw.edu.pl (Michal Gajda) (2001-05-22) |
Re: Efficient bytecode design and interpretation anton@mips.complang.tuwien.ac.at (2001-05-29) |
Re: Efficient bytecode design and interpretation jonm@fishwife.cis.upenn.edu (2001-05-30) |
Re: Efficient bytecode design and interpretation loewis@informatik.hu-berlin.de (Martin von Loewis) (2001-05-30) |
Re: Efficient bytecode design and interpretation eugene@datapower.com (Eugene Kuznetsov) (2001-05-30) |
Re: Efficient bytecode design and interpretation korek@icm.edu.pl (2001-05-31) |
Re: Efficient bytecode design and interpretation usenet.2001-05-30@bagley.org (Doug Bagley) (2001-05-31) |
Re: Efficient bytecode design and interpretation anton@mips.complang.tuwien.ac.at (2001-06-03) |
Re: Efficient bytecode design and interpretation anton@mips.complang.tuwien.ac.at (2001-06-03) |
From: | Doug Bagley <usenet.2001-05-30@bagley.org> |
Newsgroups: | comp.compilers |
Date: | 31 May 2001 02:46:02 -0400 |
Organization: | Jump.Net, Inc. |
References: | 01-05-068 |
Keywords: | performance, architecture |
Posted-Date: | 31 May 2001 02:46:02 EDT |
Michal Gajda <mg169780@zodiac.mimuw.edu.pl> writes:
> [For example - why GForth VM, with all vmgen'ed optimizations, performs so
> badly at "Programming Language Shootout" page? Note, that I chosen 0
> weights for all test that were _not_ implemented for Forth, and regarded
> only bytecode implementations-of which OCaml clearly shines]
I see Anton has already replied, but I kind of feel like my shootout
site is being misleading here, so I will make a quick comment.
Not all Gforth solutions have been optimized on my site yet. In
particular the solutions where other languages use optimized hash
tables, Gforth uses wordlists, and would probably do better if
rewritten with a custom hash table implementation.
I find that Gforth is astonishingly fast at other tests, like the
Sieve.
My shootout page is still quite flawed (as all benchmarks are :-) I
advise all my readers to please read the caveats on the methodology
page, and be very careful about trying to make generalizations.
Cheers,
Doug
Return to the
comp.compilers page.
Search the
comp.compilers archives again.