cpython/Tools/jit
2025-10-17 11:26:17 +01:00
..
_llvm.py gh-138497: Support LLVM_VERSION configuration via env (#138498) 2025-10-07 07:54:31 -07:00
_optimizers.py GH-135904: Implement assembler optimization for AArch64. (GH-139855) 2025-10-17 11:26:17 +01:00
_schema.py GH-135904: Implement assembler optimization for AArch64. (GH-139855) 2025-10-17 11:26:17 +01:00
_stencils.py GH-135904: Implement assembler optimization for AArch64. (GH-139855) 2025-10-17 11:26:17 +01:00
_targets.py GH-135904: Implement assembler optimization for AArch64. (GH-139855) 2025-10-17 11:26:17 +01:00
_writer.py GH-137959: Replace shim code in jitted code with a single trampoline function. (GH-137961) 2025-08-21 10:40:53 +01:00
build.py gh-138497: Support LLVM_VERSION configuration via env (#138498) 2025-10-07 07:54:31 -07:00
jit.h GH-135904: Improve the JIT's performance on macOS (GH-136528) 2025-07-14 10:14:20 -07:00
mypy.ini GH-113464: Add a JIT backend for tier 2 (GH-113465) 2024-01-28 18:48:48 -08:00
README.md gh-138497: Support LLVM_VERSION configuration via env (#138498) 2025-10-07 07:54:31 -07:00
template.c GH-137959: Replace shim code in jitted code with a single trampoline function. (GH-137961) 2025-08-21 10:40:53 +01:00
trampoline.c GH-137959: Replace shim code in jitted code with a single trampoline function. (GH-137961) 2025-08-21 10:40:53 +01:00

The JIT Compiler

This version of CPython can be built with an experimental just-in-time compiler1. While most everything you already know about building and using CPython is unchanged, you will probably need to install a compatible version of LLVM first.

Python 3.11 or newer is required to build the JIT.

Installing LLVM

The JIT compiler does not require end users to install any third-party dependencies, but part of it must be built using LLVM2. You are not required to build the rest of CPython using LLVM, or even the same version of LLVM (in fact, this is uncommon).

LLVM version 19 is the officially supported version. You can modify if needed using the LLVM_VERSION env var during configure. Both clang and llvm-readobj need to be installed and discoverable (version suffixes, like clang-19, are okay). It's highly recommended that you also have llvm-objdump available, since this allows the build script to dump human-readable assembly for the generated code.

It's easy to install all of the required tools:

Linux

Install LLVM 19 on Ubuntu/Debian:

wget https://apt.llvm.org/llvm.sh
chmod +x llvm.sh
sudo ./llvm.sh 19

Install LLVM 19 on Fedora Linux 40 or newer:

sudo dnf install 'clang(major) = 19' 'llvm(major) = 19'

macOS

Install LLVM 19 with Homebrew:

brew install llvm@19

Homebrew won't add any of the tools to your $PATH. That's okay; the build script knows how to find them.

Windows

LLVM is downloaded automatically (along with other external binary dependencies) by PCbuild\build.bat.

Otherwise, you can install LLVM 19 by searching for it on LLVM's GitHub releases page, clicking on "Assets", downloading the appropriate Windows installer for your platform (likely the file ending with -win64.exe), and running it. When installing, be sure to select the option labeled "Add LLVM to the system PATH".

Alternatively, you can use chocolatey:

choco install llvm --version=19.1.0

Dev Containers

If you are working on CPython in a Codespaces instance, there's no need to install LLVM as the Fedora 41 base image includes LLVM 19 out of the box.

Building

For PCbuild-based builds, pass the --experimental-jit option to build.bat.

For all other builds, pass the --enable-experimental-jit option to configure.

Otherwise, just configure and build as you normally would. Cross-compiling "just works", since the JIT is built for the host platform.

The JIT can also be enabled or disabled using the PYTHON_JIT environment variable, even on builds where it is enabled or disabled by default. More details about configuring CPython with the JIT and optional values for --enable-experimental-jit can be found here.


  1. PEP 744 ↩︎

  2. Clang is specifically needed because it's the only C compiler with support for guaranteed tail calls (musttail), which are required by CPython's continuation-passing-style approach to JIT compilation. Since LLVM also includes other functionalities we need (namely, object file parsing and disassembly), it's convenient to only support one toolchain at this time. ↩︎