Author: Armin Rigo <[email protected]> Branch: Changeset: r90580:774e328def6e Date: 2017-03-06 17:34 +0100 http://bitbucket.org/pypy/pypy/changeset/774e328def6e/
Log: link to the B3 JIT dropping llvm diff --git a/rpython/doc/faq.rst b/rpython/doc/faq.rst --- a/rpython/doc/faq.rst +++ b/rpython/doc/faq.rst @@ -182,7 +182,11 @@ On the other hand, using LLVM as our JIT backend looks interesting as well --- but again we made an attempt, and it failed: LLVM has no way to -patch the generated machine code. +patch the generated machine code, and is not suited at all to tracing +JITs. Even one big method JIT trying to use LLVM `has given up`__ for +similar reasons; read that blog post for more details. + +.. __: https://webkit.org/blog/5852/introducing-the-b3-jit-compiler/ So the position of the core PyPy developers is that if anyone wants to make an N+1'th attempt with LLVM, they are welcome, and they will receive a _______________________________________________ pypy-commit mailing list [email protected] https://mail.python.org/mailman/listinfo/pypy-commit
