Re: Perl 5 Optimizing Compiler, Part 2

[dave_the_m]

As regards RPython: using this would entail rewriting the entire perl runtime in rpython: somewhere between about 30-100K lines of C, depending on what bits are required. This would be very hard and time-consuming, and at the end, there's no guarantee that it would be any faster.

You're basically replacing mature, tightly honed C code with python, then hoping that the tracing JIT will not only bring the python code back up to the speed of the original C, but past that point and even faster.

You'd have to deal with impedance mismatches. For example, if python-style arrays and hashes provide a superset of the semantics of perl arrays and hashes then you may be able to use them directly; if not, you'd have to implement perlish hashes in python!

Also, you'd have to say goodbye to XS. It's not clear to me whether the existing perl regex engine could still be used, but if it could, it wouldn't benefit from JIT.

Etc etc.

Dave.

[Will_the_Chill]

Dave, you're right, I was confused about this. We don't need to re-implement the Perl 5 interpreter VM into RPython, we only need to compile the Perl 5 applications into RPython. I will write more about this soon in my further postings.