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

Granularity of Stack layouts #20

Open
ekpyron opened this issue Apr 19, 2023 · 1 comment
Open

Granularity of Stack layouts #20

ekpyron opened this issue Apr 19, 2023 · 1 comment

Comments

@ekpyron
Copy link
Contributor

ekpyron commented Apr 19, 2023

[copied from matrix]
For the stack layouts, I'm wondering if it is necessary to produce them at the same granularity as source maps or whether that's excessive. Tooling/debuggers should be able to transport stack layouts across swaps etc. themselves, so I'm wondering if it's enough for the compiler to produce full stack layouts at relevant points in which simple tracing is no longer enough. We can generate this information for each opcode, so this is mainly a tradeoff in the verbosity of this information.

@gnidan
Copy link
Member

gnidan commented May 3, 2023

Seems like generally specifying the entire layout is not unacceptable, but perhaps we can save some space by indicating certain kinds of stack modifications in part. Sounds like we still need to decide on specific behavior though.

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