-
Notifications
You must be signed in to change notification settings - Fork 2
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
LLVM implementation? #7
Comments
The location expression patch is not landed or reviewed yet -- that only affects wasm specific locations, such as wasm locals/params. The rest of the DWARF sections data, including simple constant expressions, are emitted per this spec in the LLVM. The llvm-dwarfdump can inspect the wasm file sections. There is also https://github.com/yurydelendik/dwarf-to-json project (which is used at https://wasdk.github.io/wasmcodeexplorer/ and Firefox). I'm not sure about the timeline of D52634 or another WIP patch landings. These patches are already present in Rust nightly. See also https://github.com/yurydelendik/llvm-project/tree/frame-pointer . Closing the issue as answered. If you have further questions on the subject please continue the thread or contact me on IRC. |
Fantastic, thanks heaps @yurydelendik I'll grab the patches from your Btw, that "WebAssembly Code Explorer" should be really useful for people wanting to understand the bitcode format. 😄 Wish I'd realised it exists a few weeks ago, when first looking into that part of things. 😉 |
Hmmm, is this correct: Just asking because I'm not used to seeing braces |
I just put emphasis on WIP block of code I was planning to refactor or improve. The code is correct. |
No worries. 😄 |
With the DWARF sections currently generated by LLVM (v8, and development) for wasm, are they following this spec?
Asking because I'm writing some initial parsing code for the
.debug_*
sections in wasm files.Will soon be up to figuring out how locations are handled (eg locals, heap, etc), and this spec seems to be the desired approach.
Just not sure if it's been implemented (even experimentally) yet. 😉
The text was updated successfully, but these errors were encountered: