Skip to content
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.

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

Before expensive loops, push stack vars to memory #52

Open
Tracked by #43
ControlCplusControlV opened this issue Dec 17, 2022 · 1 comment
Open
Tracked by #43

Before expensive loops, push stack vars to memory #52

ControlCplusControlV opened this issue Dec 17, 2022 · 1 comment

Comments

@ControlCplusControlV
Copy link
Owner

No description provided.

@ControlCplusControlV
Copy link
Owner Author

Before expensive loops, push stack vars to memory

Instead of trying to fix the stack at the end of every iteration, to be the same as before, we could just shift everything to memory when a loop is expensive enough. This wouldn't make sense for branches that run once like an if statement or switch, but for loops should probably always do this, unless w/ the dynamic programming thing above we can find a stack order that would eliminate the need to re-order the stack after every loop.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant