Skip to content

Commit 1c646d8

Browse files
Explain stencils more clearly
1 parent c20905e commit 1c646d8

File tree

1 file changed

+8
-5
lines changed

1 file changed

+8
-5
lines changed

peps/pep-0774.rst

Lines changed: 8 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -15,13 +15,16 @@ flag on Linux and Mac and ``--experimental-jit`` on Windows. To build CPython wi
1515
the JIT enabled, users are required to have LLVM installed on their machine
1616
(initially, with LLVM 16 but more recently, with LLVM 19). LLVM is responsible
1717
for generating stencils that are essential to our copy-and-patch JIT (see :pep:`744`).
18+
These stencils are predefined, architecture-specific templates that are used
19+
to generate machine code at runtime.
1820

1921
This PEP proposes removing the LLVM build-time dependency for JIT-enabled builds
20-
by hosting the generated stencils in the CPython repository to simplify the
21-
contributor experience and address concerns raised at the Python Core Developer
22-
Sprint in September 2024. That said, there is a clear tradeoff to consider, as
23-
improved developer experience does come at the cost of increased repository
24-
size.
22+
by hosting the generated stencils in the CPython repository. This approach
23+
allows us to leverage the checked-in stencils for supported platforms at build
24+
time, simplifying the contributor experience and address concerns raised at the
25+
Python Core Developer Sprint in September 2024. That said, there is a clear
26+
tradeoff to consider, as improved developer experience does come at the cost of
27+
increased repository size.
2528

2629
It is important to note that this PEP is not a proposal to accept or reject the
2730
JIT itself but rather to determine whether the build-time dependency on LLVM is

0 commit comments

Comments
 (0)