Skip to content

PEP 831: Fix typo in JIT frame pointer explanation #4919

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
savannahostrowski merged 1 commit into from
Apr 16, 2026
+1 −1
Merged

PEP 831: Fix typo in JIT frame pointer explanation #4919

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion peps/pep-0831.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -411,7 +411,7 @@ code is a prerequisite for the JIT to be considered production-ready.

Individual JIT stencils do not need frame-pointer prologues; the entire JIT
region can be treated as a single frameless region for unwinding purposes.
What matters is that the JIT itself is must reserve frame pointers, so
What matters is that the JIT itself must reserve frame pointers, so
that the frame-pointer register (``%rbp`` on x86-64, ``x29`` on AArch64) is
reserved and not clobbered by stencil code. With frame pointers in the
JIT, most unwinders can walk through JIT regions without needing to inspect
Expand Down
Loading