1. Pypy
  2. Untitled project
  3. pypy
  4. Branches

Branches

core-only-tracing

View source
core-only-tracing
  • Contributors
    1. Loading...
Author Commit Message Date Builds
250+ commits behind default.
Antonio Cuni
(antocuni, arigo): mark more modules as is_core, because they really contain extensions to pyopcode.py
Antonio Cuni
bah, actually fix rpython
Antonio Cuni
tentative rpython fix
Antonio Cuni
(antocuni, arigo, romain around): try to implement a reasonable is_core_function policy for the pypy interpreter
Antonio Cuni
(antocuni, arigo): improve this test
Antonio Cuni
(antocuni, arigo): use a boolean instead of a string to store the value of core-only-mode, and don't disable inlining automatically (for now at least)
Antonio Cuni
(antocuni, arigo): if we are in core mode, we know for sure that the jitcode we are tracing is_core
Antonio Cuni
always disable inlining when setting the jitmode to core-only
Antonio Cuni
rename 'fast' mode to 'core-only'
Antonio Cuni
make sure to inline core-to-core calls
Antonio Cuni
make sure not to inline indirect calls when in core-only mode
Antonio Cuni
fix tests
Antonio Cuni
implement the 'fast' jit mode, in which we trace only inside the 'core' graphs, and do residual calls to everything else; still in-progress, at least one case is missing, see next checkin
Antonio Cuni
(antocuni, arigo, romain) complain if a graph is marked as access_direct but not core, because in this case we would have a wrong behaviour when tracing in core-only mode
Antonio Cuni
(antocuni, arigo, romain): introduce the is_core flag on JitCodes, which will be used to select which graphs to inline when tracing in core-only mode
Antonio Cuni
(antocuni, arigo, bivab, romain): a branch where to experiment with 'lightweight tracing', in which we inline only the opcode implementations and nothing else