Add managed ildasm initial project structure #123848
Conversation
am11
commented
Feb 1, 2026
am11
commented
- Add src/tools/ildasm with CLI, library, and test projects
- Implement all 218 IL opcodes in InstructionDisassembler
- Add Options class and wire CLI arguments to library
- Output basic assembly/module/type/method structure
- Add TODOs for remaining work (token resolution, etc.)
- Add src/tools/ildasm with CLI, library, and test projects - Implement all 218 IL opcodes in InstructionDisassembler - Add Options class and wire CLI arguments to library - Output basic assembly/module/type/method structure - Add TODOs for remaining work (token resolution, etc.)
github-actions
bot
added
the
needs-area-label
am11
added
area-ILTools-coreclr
community-contribution
|
Tagging subscribers to this area: @JulieLeeMSFT, @dotnet/jit-contrib |
src/tools/ildasm/tests/ILDisassembler.Tests/InstructionDisassemblerTests.cs
Show resolved
Hide resolved
|
Let's wait on ildasm until we finish ilasm. In any case, I was thinking that we should build ildasm on the managed type system and the ILImporter infrastructure over there so we can reuse a bunch of code and have less to maintain in the future. |
Managed type system expects metadata for all dependencies that is not compatible with how ildasm works. You would be constantly fighting against that. BTW: We have a little managed IL disassembler as a debugging aid: https://github.com/dotnet/runtime/blob/main/src/coreclr/tools/Common/TypeSystem/IL/ILDisassembler.cs . It was not built using |
|
I was able to rewire it with: https://github.com/am11/runtime/tree/feature/managed-ildasm2 It's a bit cleaner. Do you want this S.R.M version or push that one? |
4 participants
