debuginfo: revisit wasm vs masm location operation representation in debug expressions
Open
debugging
- Dominant language
- Rust
- Stars
- 115
- Forks
- 84
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 15
Description
We might want to revisit the way we represent variable location/values in the debug expressions, parsed from wasm. From frontend itself, we may consider to start emitting masm native locations.
Contributor guide
Research direction
The issue concerns debug expression representation for variable locations/values, comparing wasm and masm (Miden Assembly). Look at the debug info generation and parsing code in the compiler frontend. Understand the current wasm-based location operation representation and how masm native locations differ. Determine what changes are needed to start emitting masm locations from the frontend.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100