You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are too many _SET_IP and _CHECK_VALIDITY micro-ops being inserted into tier 2 code.
There are two causes of this:
Too many micro-ops are marked as escaping
Python call uops do not technically escape but must be preceded by _SET_IP in order to correctly set the return address. We need a way of marking these, so that we insert _SET_IP before them, but do not needlessly insert _CHECK_VALIDITY after them.
Bug report
Bug description:
There are too many
_SET_IP
and_CHECK_VALIDITY
micro-ops being inserted into tier 2 code.There are two causes of this:
_SET_IP
in order to correctly set the return address. We need a way of marking these, so that we insert_SET_IP
before them, but do not needlessly insert_CHECK_VALIDITY
after them.CPython versions tested on:
3.13, CPython main branch
Operating systems tested on:
No response
Linked PRs
The text was updated successfully, but these errors were encountered: