Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • JIT can help, if you have a tracing scheme (or a sufficiently simple language). One of the most important realizations is you must distinguish between heap and stack allocations [perl.org] -- making allocation as cheap as possible.

    If you have a good tracing scheme, and if you can inline calls and branches cheaply, and if you have a parameter passing scheme which has as few memory copies as possible (go registers!), and if you have a sufficiently clever register allocation scheme which works across basic blocks, a JIT can go very, very fast.

    Without those, a JIT can sometimes go faster.