|more useful options|
Re^2: Perl 5 Optimizing Compiler, Part 2by Will_the_Chill (Pilgrim)
|on Aug 18, 2012 at 02:14 UTC||Need Help??|
A tracing & optimizing JIT that is Perl-specific, such as what would be created by RPython, should provide some amount of "magical fairy dust" in that it should make Perl 5 run faster. Please correct me on this particular point.
"As fast as C" may be a bit tongue-in-cheek, we can stick with my original phrasing of "within an order of magnitude as fast as optimized C". This should have a very specific meaning to anyone running performance benchmarks. Write some code in C, then write the same code in Perl, then run them for comparison.
I fully agree about the issue of making sure a VM is a suitable target for a particular language.
RPython would generate a Perl-specific JIT. No multi-octopus wrestling match there.
Ingy's C'Dent and Perl5i are supposed to be generating XS code, so no new VM there, and no multi-octopus wrestling match that I can see.
Reini's B system seems closely tied to the existing Perl 5 interpreter VM, so no multi-octopus wrestling match there, either.
So what am I actually wrong about?