microsoft / microsoft/SizeBench
Diffing two binaries should have side-by-side disassembly when drilled into a specific function
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 175
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
I have been doing some binary size analysis to determine where some growth has come from. A certain function increased in size from 3.1KB to 3.9KB. Exactly what part of it grew is not obvious. It would be super helpful if the comparative analysis view of a function had the disassembly for both sides (ideally with highlighting of differences). That way I can see exactly what is different and spend my time making it better instead of spending all my time trying to spot the difference.
In practice I had to open 2 copies of SizeBench in non-comparison view to see the disassembly. This was manual and error-prone and I did not enjoy it.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start from the comparative analysis view when drilling into a specific function, then trace how the non-comparison view displays disassembly for each binary. Done means the comparative function view shows both disassemblies side by side, with differences highlighted if feasible, so users no longer need two separate SizeBench windows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- desktop, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100