Using BinDiff to Compare Assembly Changes from Compiler Patches
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 240
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I have a general question regarding BinDiff. My background is in compilers and compiler optimizations, and I’m exploring whether BinDiff can be used to analyze changes in generated assembly after applying a compiler patch.
I work on a closed architecture and I'm trying to see if I'm able to utilize BinDiff for this goal.
Since the architecture I work on is closed, I can’t rely on existing disassemblers like IDA. From what I understand, BinExport typically takes an IDA database as input and produces a protobuf file for BinDiff to analyze.
To support the architecture I'm working on, I assume I would need to parse the assembly files and convert them into a protobuf format according to binExport2.proto.
Am I understanding this correctly? Would this approach work for my use case?
Thanks in advance!
Contributor guide
Assessment
This issue has not been assessed yet.