Nicolas Cannasse wrote:
Even with such problems, I was thinking that Parrot JIT will be faster than
NekoVM which does not have a JIT yet.
The fib benchmark is mainly function calls only. JIT doesn't really help
here. We will optimize function call performance later.
I don't run sources from Parrot , I have PxPerl installed.
Yes I know. You should install Parrot from SVN and compile it optimized
for benchmarking.
$ ./parrot -j examples/assembly/mops.pasm
I get the following results :
Elapsed time: 3.281000
M op/s: 60.957023
Looks like it means that JIT is not active. How can I activate it ?
Seems that it isn't compiled with JIT support but don't ask me, how it
was disabled in the first place (and why you don't get an error message).
$ ./parrot -C ... # direct threaded CGP core
This one give the following error :
Couldn't find init_func for core 6
And it was obviously configure with --cgoto=0, or compiled with a
microsoft? compiler that doesn't support computed goto.
So parrot have several version of the interpreter/jit embedded ? What are
the current choices ?
There are several "run loops". 'parrot --help' shows various 'Run core
options'. CGoto & CGP depend on compiler support. JIT should always be
available on x86.
Thanks for your answers,
Best,
Nicolas
leo
