# HG changeset patch # User Armin Rigo <arigo@tunes.org> # Date 1371202385 -7200 # Fri Jun 14 11:33:05 2013 +0200 # Branch extradoc # Node ID 20772db949f3a85fc43270cb317a3234d1105948 # Parent a21fa8ed4befaac76aaabdaf079f4693afb52835 Update this paragraph diff --git a/download.html b/download.html --- a/download.html +++ b/download.html @@ -201,11 +201,13 @@ PYPY_GC_MAX_DELTA=200MB pypy --jit loop_longevity=300 ../../rpython/bin/rpython -Ojit targetpypystandalone </pre> </li> -<li><p class="first">Because of <tt class="docutils literal">asmgcroot</tt>, compiling the generated C files containing the JIT -is delicate. It requires using either MSVC or gcc with no particularly +<li><p class="first">On Linux, because of <tt class="docutils literal">asmgcroot</tt>, compiling the generated C files +is delicate. It requires using gcc with no particularly fancy options. It does not work e.g. with clang, or if you pass uncommon -options with the <tt class="docutils literal">CFLAGS</tt> environment variable. You can also try to -compile PyPy with the <a class="reference external" href="http://pypy.readthedocs.org/en/latest/config/translation.gcrootfinder.html">shadow stack</a> option.</p> +options with the <tt class="docutils literal">CFLAGS</tt> environment variable. If you insist on +passing these options or using clang, then you can compile PyPy with +the <a class="reference external" href="http://pypy.readthedocs.org/en/latest/config/translation.gcrootfinder.html">shadow stack</a> option instead (for a small performance price in +non-JITted code).</p> </li> </ul> </div> diff --git a/source/download.txt b/source/download.txt --- a/source/download.txt +++ b/source/download.txt @@ -213,11 +213,13 @@ PYPY_GC_MAX_DELTA=200MB pypy --jit loop_longevity=300 ../../rpython/bin/rpython -Ojit targetpypystandalone -* Because of ``asmgcroot``, compiling the generated C files containing the JIT - is delicate. It requires using either MSVC or gcc with no particularly +* On Linux, because of ``asmgcroot``, compiling the generated C files + is delicate. It requires using gcc with no particularly fancy options. It does not work e.g. with clang, or if you pass uncommon - options with the ``CFLAGS`` environment variable. You can also try to - compile PyPy with the `shadow stack`_ option. + options with the ``CFLAGS`` environment variable. If you insist on + passing these options or using clang, then you can compile PyPy with + the `shadow stack`_ option instead (for a small performance price in + non-JITted code). .. _`x86 (IA-32)`: http://en.wikipedia.org/wiki/IA-32 .. _`x86-64`: http://en.wikipedia.org/wiki/X86-64