Source

pypy / pypy / doc / config / translation.gcrootfinder.txt

Choose the method used to find the roots in the GC.  This only
applies to our framework GCs.  You have a choice of two
alternatives:

- ``--gcrootfinder=shadowstack``: use a so-called "shadow
  stack", which is an explicitly maintained custom stack of
  root pointers.  This is the most portable solution.

- ``--gcrootfinder=asmgcc``: use assembler hackery to find the
  roots directly from the normal stack.  This is a bit faster,
  but platform specific.  It works so far with GCC or MSVC,
  on i386 and x86-64.

You may have to force the use of the shadowstack root finder if
you are running into troubles or if you insist on translating
PyPy with other compilers like clang.
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.