|Do you know where your variables are?|
For example, every Perl 5 op has to check if its operands are tied or have other magic attached. That's at least one if clause in every op (but I repeat myself).
Compiling Perl 5 with clang won't help that at all because the types of the operands aren't known until you run a Perl 5 program.
If, instead, the internals had separate types of variables depending on the attached magic such that the code to get a value from a tied scalar were a part of the tied scalar and not in every op, a lot of code could go away. A lot of conditionals could go away, especially for the common case where most scalars aren't tied scalars.
(Doing that in C like Parrot does doesn't really help much, because even a good optimizing C compiler can't optimize the trailer park polymorphic dispatch you have to write by hand to get something remotely like an object system in C. Chip had the right idea with Topaz, except that cross-platform C++ was awfully hard to support then.)
You can speed up op dispatch all you want, but the slow part of Perl 5 is the part that manages data.
In reply to Re^6: Perl 5 Optimizing Compiler, Part 7: Video Chat w/ Ingy & Reini, Today 9/18 8pm Central Time