-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does ddisasm work for Risc-V binaries? #43
Comments
We do not have any support for Risc-V binaries yet. But we are open to contributions and Capstone does support Risc-V so the external dependency for Risc-V is satisfied. |
Hello @eschulte Thanking you |
The changes on the GTIRB side should be minimal, basically just adding RISC-V to the ISA enum in our protobuf module definition and to the corresponding ISA enums in our Python, Java, and Common Lisp APIs. That part should be trivial. On the DDisasm side I'd look under Also, if you're considering this (which would be awesome!), do be aware of our code of conduct and the fact that we ask all contributors to DDisasm to sign our contributor license agreement which give GrammaTech rights to your contributions to DDisasm so that we can maintain our GPL. |
Thank you @eschulte. I will probably start working on some small binary rewriting examples w.r.t x86 backend to get accustomed to ddisasm. And then try looking into RiscV backend. -Sai |
@SaiVK you will probably want to extend gtirb-pprinter (https://github.com/grammatech/gtirb-pprinter) as well, so it can print RISC-V gtirb files. Similarly to ddisasm, you might want to look at how other ISAs are implemented there, such as ARM64 https://github.com/GrammaTech/gtirb-pprinter/blob/master/src/gtirb_pprinter/Arm64PrettyPrinter.cpp to get an idea of what is needed. |
Thanks, @aeflores for the pointers. I will look into it. -Sai |
Hello Everyone
Can ddisasm be applied to Risc-V binaries to generate relocatable-assembly code and perform CFG analysis etc...?
Thanking you
Sai
The text was updated successfully, but these errors were encountered: