At 12:00 20/09/2007 -0300, you wrote:
Date: Wed, 19 Sep 2007 20:26:52 +0200
From: Mike Pall <[EMAIL PROTECTED]>
Subject: Re: [ANN] Lua on Parrot 0.4.16
To: Lua list <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=iso-8859-1
Hi,
Fran?ois PERRAD wrote:
> Any comments, suggestions, bug report, test, improvement are welcome on
> Parrot mailing list ([EMAIL PROTECTED]).
Mike,
I can't give you an answer, because in a Parrot point of view,
I'm only a Parrot user, in fact a language implementor (Lua in
this case) in the Parrot terminology. So I am not the guru of internals,
JIT or others optimisation issues.
But someone on [EMAIL PROTECTED] have responses for you.
Thank you for interest, and I am happy to see that the current
implementation allows this kind of test.
I'm interested by the source of yours benchmarks,
for me, it's more test case.
Regards.
François.
Umm, before I make a fool of myself over there ... I've tested
this with a few benchmarks. So, maybe I'm missing something
essential, but why does --jit-core *slow down* things (5%-10%
slower than --computed-goto-core)?
And even if it's only interpreted, 20x-33x *slower* than the Lua
interpreter seems a bit hefty. And comparing (supposedly) JIT
compilers, it's 50x-200x slower than LuaJIT 1.1.
Do I need to disable some debug stuff? I just followed the
standard build instructions ...
Bye,
Mike
