search for: repzret

Hi - Not sure if anyone else saw this or cares about a decompiler (not personally tested) https://github.com/draperlaboratory/fracture I wonder if they have been in contact with anyone in the community in getting this upstreamed. Does it look interesting to anyone else? (thoughts/random comments/feedback)

...; portion of x86 machine code decompiled to IR. That was several weeks > ago and it looks like the project has progressed quite a bit. > > Other projects: > https://github.com/libcpu/libcpu (tried this one a long time ago, also > couldn't get any decompilation) > http://dagger.repzret.org/ (they finally released some source! One of > the devs presented at a LLVM meeting) > > I am definitely interested in seeing a production-quality decompiler! > > Cheers, > Jevin Very cool, I just tested out dagger with a small x86_64 test and it worked! You can see my test an...

On Fri, Jun 3, 2016 at 11:53 AM, Ahmed Bougacha <ahmed.bougacha at gmail.com> wrote: > -llvmdev at cs.uiuc.edu, that list isn't in use anymore. > > On Wed, Jun 1, 2016 at 4:48 PM, Kenneth Adam Miller via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > Hello all, > > > > I would like to restrain the compiler that I build on my local box from >

...scussed in the past would be to >> describe each instruction in terms of the generic mir operations. >> >> Ultimately we could get a lot of this semantic information automatically >> populated by TableGen using the ISel patterns, like dagger does >> (https://github.com/repzret/dagger). >>> Anyway, for the most part, I believe we could implement the >> “interpreter” for just a handful of instruction and get 90% of the >> information right. >> > > This seems interesting. We will need to investigate this further if we > decide to take in...

...es. One way we could do that and that was discussed in the past would be to describe each instruction in terms of the generic mir operations. Ultimately we could get a lot of this semantic information automatically populated by TableGen using the ISel patterns, like dagger does (https://github.com/repzret/dagger). Anyway, for the most part, I believe we could implement the “interpreter” for just a handful of instruction and get 90% of the information right. Cheers, -Quentin > On Feb 14, 2019, at 9:20 AM, Adrian Prantl <aprantl at apple.com> wrote: > > > >> On Feb 13, 20...

Hi All, 2 of my summer interns (Aimee Dipietro and Greg Simpson) used their time over the summer to resurrect the LLVM C Backend: https://github.com/draperlaboratory/llvm-cbe Improvements include recovery of simple for/while loops (instead of goto), better variable naming, inline asm support, and making it work on a more recent version of llvm. I believe they used the repository here as a

Hi, [+ Quentin] Sorry for the late reply. > On Feb 13, 2019, at 9:09 AM, Nikola Prica <nikola.prica at rt-rk.com> wrote: > > On 12.02.2019. 18:06, Adrian Prantl wrote: >> [+ some folks more knowledgable about the Machine layer than me.] >> > That would be useful for us too! :) > > >>> On Feb 12, 2019, at 5:07 AM, Nikola Prica <nikola.prica at