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

[ 💻 Clarity VM ] Optimize stack pointer management #34

Open
obycode opened this issue Aug 17, 2023 · 0 comments
Open

[ 💻 Clarity VM ] Optimize stack pointer management #34

obycode opened this issue Aug 17, 2023 · 0 comments

Comments

@obycode
Copy link
Collaborator

obycode commented Aug 17, 2023

Currently, we are incrementing the stack pointer (a Wasm global) each time a new value needs to be pushed to the execution stack (the current function's stack frame in the linear memory). Instead, we should do a compilation pass that computes the total stack size needed for a function, and increments the stack pointer once, during the function prologue, and save the offsets for each local to use during the compilation pass.

@obycode obycode changed the title Optimize stack pointer management [ 💻 Clarity VM ] Optimize stack pointer management Sep 5, 2023
@github-project-automation github-project-automation bot moved this to 🆕 New in Stacks Core Eng Sep 5, 2023
@obycode obycode moved this from 🆕 New to 📋 Backlog in Stacks Core Eng Sep 20, 2023
@smcclellan smcclellan added this to the WASM Phase 3 milestone Mar 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Status: 📋 Backlog
Development

No branches or pull requests

2 participants