Now that the libObect support for wasm is better we can
have readobj and nm produce more useful output too.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
test/tools/llvm-readobj/file-headers.test | ||
---|---|---|
29 ↗ | (On Diff #93556) | using generated using? |
tools/llvm-readobj/WasmDumper.cpp | ||
159 ↗ | (On Diff #93556) | Should we also print the numeric value of the symbol type, as in other formats? Actually come to think of it we don't specify (or document externally) what those are, maybe we should. |
Comment Actions
- Merge remote-tracking branch 'origin/master' into better_nm_readobj_support
- use printEnum in WasmDumper.cpp
tools/llvm-readobj/WasmDumper.cpp | ||
---|---|---|
159 ↗ | (On Diff #93556) | Fixed by switching to printEnum. I agree we should document these types, probably in https://github.com/WebAssembly/tool-conventions/blob/master/Linking.md. One interesting aspect is that these symbol types are synthetic in that the numeric types don't actually exist in the object file, they mostly exist (in memory only) to enable tools such as nm to distinguish where the symbol came from. |