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

Local variables tracking #42

Open
yann300 opened this issue Dec 7, 2023 · 1 comment
Open

Local variables tracking #42

yann300 opened this issue Dec 7, 2023 · 1 comment

Comments

@yann300
Copy link

yann300 commented Dec 7, 2023

local variables (and params):
The compiler should if possible returns all the ranges in the VM trace where a specific local is in the scope, and how to track its ref or value in the stack (this is perhaps the most important thing for us or at least this is where we spent most of the time..)

@gnidan
Copy link
Member

gnidan commented Mar 28, 2024

For this, I imagine something like this pair of instruction annotations (note the use of parent as an example, to indicate how scopes are re-used/inherited):

operation:
  begin: scope
  id: 5
  parent: 4
  variables:
    x:
      type:
        kind: uint
        bits: 256

Then, later another instruction would be annotated with something like:

operation:
  scope: deallocate
  variables: ["x"]

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

2 participants