On Thu, 11 Apr 2002, [latin1] Josef Höök wrote:
>
> How about the JIT engine then.
> When does parrot use it?
> how well does it scale? ( has anyone done some benchmarking )
The JIT engine produce machine code for a given bytecode, but there are
only a few opcodes that are coded in assembly so
Jonathan E. Paton:
# > How about the JIT engine then.
#
# JIT runs on bytecode, producing bytecode.
No, JIT runs on bytecode, producing equivalent machine code.
# > When does parrot use it?
#
# Before executing bytecode.
#
# > how well does it scale? ( has anyone done some benchmarking )
#
# Don
> > How about the JIT engine then.
>
> JIT runs on bytecode, producing bytecode.
>
> > When does parrot use it?
>
> Before executing bytecode.
>
> > how well does it scale? ( has anyone done some benchmarking )
>
> Don't ask me :P If you haven't already, then you'd
> be best looking at the b
How about the JIT engine then.
When does parrot use it?
how well does it scale? ( has anyone done some benchmarking )
On Thu, 11 Apr 2002, [iso-8859-1] Jonathan E. Paton wrote:
> > Where in the parrot code does the actual translation
> > from byte code to binary code occur?
>
> Parrot eq. a
> Where in the parrot code does the actual translation
> from byte code to binary code occur?
Parrot eq. an interpreter, all the byte codes are like
commands to tell it what actions to take... it doesn't
directly take byte codes and turn them into binary code.
Conversion would be compiling, but
