Vector35 / Vector35/binaryninja-api
Consider switching x86 assembler to xed encoder
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.3k
- Forks
- 298
- Avg merge
- 5d 5h
- Merged PRs (30d)
- 19
Description
xed now has an example that does it: https://github.com/intelxed/xed/blob/main/examples/xed-enc-asmparse.c
This would allow us to support many instructions that are currently not supported by yasm. The performance will also be better https://github.com/Vector35/binaryninja-api/issues/6022
Contributor guide
No contributing guide indexed for this repository
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 by reading the linked XED xed-enc-asmparse.c example and comparing it with the repository's current YASM-based x86 assembler integration. Define the affected assembler entry points and tests before evaluating whether XED can replace the existing path; done means broader instruction support and improved performance are demonstrated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers, reverse-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100