<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im"><br></div>
However, it requires that the JIT compiler knows about a lot of<br>
optimisations. PyPy's JIT is full of those. It's not the fact that it has a<br>
JIT compiler at all that makes it fast and not the fact that they compile<br>
Python to machine code, it's the fact that they came up with a huge bunch<br>
of specialisations that makes lots of code patterns fast once it detected<br>
them. LLVM (or any other low-level JIT compiler) won't help at all with that.<br>
<span class="HOEnZb"><font color="#888888"><br>
Stefan<br>
</font></span><div class="HOEnZb"><div class="h5"></div></div></blockquote><div><br></div><div>Very good point Stefan</div><div><br></div><div>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.</div>
<div><br></div><div>Cheers,</div><div>fijal</div></div>