Ken Fox writes:
> pipeline stalls, cache misses and a whole bunch of interesting things. One
> of the reasons Perl performed well is that it spent a lot of time in what
> they called native code, i.e. not decoding and dispatching ops.

One thing we could do is look at the op paths produced by perl5 code
and work out which sequences of ops occur so often that they deserve
to be encapsulated in their own op.  This might give us new ideas on
how to design the ops.

Nat

Reply via email to