RetroSearch Browse

Wed Jul 18 11:10:32 CEST 2012 · https://mail.python.org/pipermail/python-dev/2012-July/121026.html

>
>
> However, it requires that the JIT compiler knows about a lot of
> optimisations. PyPy's JIT is full of those. It's not the fact that it has a
> JIT compiler at all that makes it fast and not the fact that they compile
> Python to machine code, it's the fact that they came up with a huge bunch
> of specialisations that makes lots of code patterns fast once it detected
> them. LLVM (or any other low-level JIT compiler) won't help at all with
> that.
>
> Stefan
>

Very good point Stefan

I would just like to add that a lot of those also require changes in the
object model which might render changes in CPython C API (like the
introduction of maps). Certainly you can't keep the current C structures,
which will already break some code.

Cheers,
fijal
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/python-dev/attachments/20120718/61d22294/attachment.html>

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://mail.python.org/pipermail/python-dev/2012-July/121026.html below:

[Python-Dev] A new JIT compiler for a faster CPython?