Repository navigation
Optimize float operations by mutating uniquely-referenced operands in place (JIT only) #146306
Description
Activity
- added a commit that references this issue
on Mar 24, 2026 I think the remaining float operations are probably rare and also annoying to account for (e.g.
float OP int), so let's consider this done, and expand on it in future issues if need be.The next big thing is probably compact longs.
Reacted by stonebig- added 6 commits that reference this issue
on Mar 24, 2026
Feature or enhancement
Proposal:
When the tier 2 optimizer can prove that an operand to a float binary operation is uniquely referenced, we can mutate it in place instead of allocating a new
PyFloatObject. This avoids aPyFloat_FromDoubleallocation and the subsequent deallocation of the consumed operand on every iteration.The unique reference tracking infrastructure added in #144300 can be used for the float operations as well. Also see #90530 where a similar optimization was proposed for tier 1 using runtime refcount checks.
Has this already been discussed elsewhere?
No response given
Links to previous discussion of this feature:
No response
Linked PRs