10000 GH-130415: Use boolean guards to narrow types to values in the JIT by brandtbucher · Pull Request #130659 · python/cpython · GitHub
[go: up one dir, main page]
Skip to content

GH-130415: Use boolean guards to narrow types to values in the JIT #130659

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
merged 13 commits into from
Mar 2, 2025
Merged

GH-130415: Use boolean guards to narrow types to values in the JIT #130659

Changes from 1 commit
Commits
Show all changes
13 commits
Select commit Hold shift + click to select a range
d0f236a
Add failing regression tests
brandtbucher Feb 27, 2025
7929a57
Add "truth" symbols
brandtbucher Feb 27, 2025
6c4588e
Fix up test
brandtbucher Feb 28, 2025
1d17afe
is
brandtbucher Feb 28, 2025
dcb294c
Add creation and narrowing of truths
brandtbucher Feb 28, 2025
41e77a8
Use the new truth symbols
brandtbucher Feb 28, 2025
d0b1724
Fix tests
brandtbucher Feb 28, 2025
c8214c9
blurb add
brandtbucher Feb 28, 2025
ffa559b
"truth" -> "truthiness"
brandtbucher Feb 28, 2025
cbd4569
Fix some compiler warnings
brandtbucher Feb 28, 2025
9f1b271
Invert the "not" arg for clarity
brandtbucher Mar 1, 2025
07697ed
Merge branch 'main' into jit-narrow-to-bool-bool
brandtbucher Mar 2, 2025
4edba18
Add tests for truthiness symbol
brandtbucher Mar 2, 2025
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
Prev Previous commit
Next Next commit
Fix some compiler warnings
  • Loading branch information
@brandtbucher
brandtbucher committed Feb 28, 2025
commit cbd4569dee37b5b2686b17b2ada6605a4739030e
5 changes: 3 additions & 2 deletions Python/optimizer_symbols.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -663,7 +663,7 @@ _Py_uop_abstractcontext_fini(JitOptContext *ctx)
void
_Py_uop_abstractcontext_init(JitOptContext *ctx)
{
static_assert(sizeof(JitOptSymbol) <= 2*sizeof(uint64_t));
static_assert(sizeof(JitOptSymbol) <= 2 * sizeof(uint64_t), "JitOptSymbol has grown");
ctx->limit = ctx->locals_and_stack + MAX_ABSTRACT_INTERP_SIZE;
ctx->n_consumed = ctx->locals_and_stack;
#ifdef Py_DEBUG // Aids debugging a little. There should never be NULL in the abstract interpreter.
Expand Down Expand Up @@ -718,6 +718,7 @@ _Py_uop_symbols_test(PyObject *Py_UNUSED(self), PyObject *Py_UNUSED(ignored))
_Py_uop_abstractcontext_init(ctx);
PyObject *val_42 = NULL;
PyObject *val_43 = NULL;
PyObject *tuple = NULL;

// Use a single 'sym' variable so copy-pasting tests is easier.
JitOptSymbol *sym = _Py_uop_sym_new_unknown(ctx);
Expand Down Expand Up @@ -821,7 +822,7 @@ _Py_uop_symbols_test(PyObject *Py_UNUSED(self), PyObject *Py_UNUSED(ignored))
"tuple item does not match value used to create tuple"
);
PyObject *pair[2] = { val_42, val_43 };
PyObject *tuple = _PyTuple_FromArray(pair, 2);
tuple = _PyTuple_FromArray(pair, 2);
sym = _Py_uop_sym_new_const(ctx, tuple);
TEST_PREDICATE(
_Py_uop_sym_get_const(ctx, _Py_uop_sym_tuple_getitem(ctx, sym, 1)) == val_43,
Expand Down
0