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
{{ message }}
Repository navigation
Streamline spilling around calls in the code generator #150516
So that the GC can see all objects on the stack, any call that escapes and could thus potentially trigger the GC, must be wrapped in code to spill values to the stack and save the stack pointer.
Prior to tailcalling, it made sense to save and reload the stack pointer as the stack pointer would have usually been spilled anyway. Now that we use the preserve none calling convention, the stack pointer will not be spilled so reloading is redundant.
We can drop the reload and not adjust the stack pointer, merely saving the adjusted value.
For example, instead of:
Activity
pythongh-150516: Keep genuine reloads after instrumentation/monitorin…
pythongh-150516: Elide redundant stack pointer reloads after escaping…
pythongh-150516: Elide redundant stack pointer reloads after escaping…
pythongh-150516: Review fixes for the spill/reload elision
GH-150516: Reduce the work done to spill and reload the stack around …
pythonGH-150516: Reduce the work done to spill and reload the stack a…