_INSERT_1_LOAD_CONST_INLINE(_BORROW) and _LOAD_CONST_UNDER_INLINE(_BORROW) have identical stack effects — they're basically the same thing with different names.
_LOAD_CONST_UNDER_INLINE(_BORROW) already has entries in op_without_push, so remove_unneeded_uops can properly simplify it. However _INSERT_1 don't, thus we should rename all _INSERT_1 usages to _LOAD_CONST_UNDER and remove the duplicate definitions.
Has this already been discussed elsewhere?
This is a minor feature, which does not need previous discussion elsewhere
changed the title [-]Remove duplicate uops `_INSERT_1_LOAD_CONST_INLINE(_BORROW)` in JIT[/-][+]Remove duplicate uops `_LOAD_CONST_UNDER_INLINE(_BORROW)` in JIT[/+]on Apr 8, 2026
Activity
NekoAsakura commented on Apr 8, 2026
cc: @Fidget-Spinner
pythongh-148235: remove duplicate uops `_INSERT_1_LOAD_CONST_INLINE(_…
pythongh-148235: remove duplicate uops `_LOAD_CONST_UNDER_INLINE(_BOR…
pythongh-148235: remove duplicate uops `_LOAD_CONST_UNDER_INLINE(_BOR…
gh-148235: remove duplicate uops `_LOAD_CONST_UNDER_INLINE(_BORROW)` …
Fidget-Spinner commented on Apr 8, 2026
In the future, smaller issues like these can go under #148211. Thanks!
pythongh-148235: remove duplicate uops `_LOAD_CONST_UNDER_INLINE(_BOR…