21–30 of 40 posts
If we would write some code in rust, compile it to, for example, x86_64. And then de-compile it to C. It would be perfectly memory-safe C code, right?
Nothing is perfectly memory-safe. Also, not sure I would see the point of this translation?
How about formally verified SPARK code?
If we would write some code in rust, compile it to, for example, x86_64. And then de-compile it to C. It would be perfectly memory-safe C code, right?
Compiling down to asm, lot of information is lost regarding memory layout etc, so it's not the best source for generating code.
If we would write some code in rust, compile it to, for example, x86_64. And then de-compile it to C. It would be perfectly memory-safe C code, right?
As Rust is llvm based, you don't need to compile it to C. Just write a backend that translates LLVM IR to C instead of x86_64. The IR is very C looking, it's probably overly complex. Compiling down to asm, lot of information is lost regarding memory layout etc, so it's not the best source for generating code.
edit: you also have mrustc as a Rust to C compiler outright.
How about this for an idea: a decompiler that uses Machine Learning to name the decompiled variables and functions. Would be nice even if it worked only sometimes.
How about this for an idea: a decompiler that uses Machine Learning to name the decompiled variables and functions. Would be nice even if it worked only sometimes.
It's also something that could be somewhat easy to get a lot of learning material for.
The main website seems to be dead, and there are no examples of its output.
The main website seems to be dead, and there are no examples of its output.
A shame. My understanding is this was state of the art, for a free and open source decompiler. Of course, times change and AFAICT Ghidra has taken up that mantle.
If we would write some code in rust, compile it to, for example, x86_64. And then de-compile it to C. It would be perfectly memory-safe C code, right?
As Rust is llvm based, you don't need to compile it to C. Just write a backend that translates LLVM IR to C instead of x86_64. The IR is very C looking, it's probably overly complex. Compiling down to asm, lot of information is lost regarding memory layout etc, so it's not the best source for generating code.
Earlier quoted context omitted.
A shame. My understanding is this was state of the art, for a free and open source decompiler. Of course, times change and AFAICT Ghidra has taken up that mantle.
I'm surprised to hear that, I thought retdec was pretty well regarded.
retdec haven't tagged (or built) a release in a couple years, unfortunately, but there is recent activity on their repo.
How about this for an idea: a decompiler that uses Machine Learning to name the decompiled variables and functions. Would be nice even if it worked only sometimes.
Wait, did I say it was possible? I'm curious what a neural netted compiler would produce. Probably your average CRUD software.