Author: Armin Rigo <[email protected]>
Branch:
Changeset: r70400:ac4800c0db8a
Date: 2014-04-02 19:06 +0200
http://bitbucket.org/pypy/pypy/changeset/ac4800c0db8a/
Log: Mention llvm-translation-backend without killing the rest of the
entry.
diff --git a/pypy/doc/faq.rst b/pypy/doc/faq.rst
--- a/pypy/doc/faq.rst
+++ b/pypy/doc/faq.rst
@@ -438,7 +438,9 @@
faster than compiling it with gcc.) We might in theory get extra
benefits from LLVM's GC integration, but this requires more work on the
LLVM side before it would be remotely useful. Anyway, it could be
-interfaced via a custom primitive in the C code.
+interfaced via a custom primitive in the C code. (The latest such
+experimental backend is in the branch ``llvm-translation-backend``,
+which can translate PyPy with or without the JIT on Linux.)
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
_______________________________________________
pypy-commit mailing list
[email protected]
https://mail.python.org/mailman/listinfo/pypy-commit
