[LLVMdev] converting x86 instructions to LLVM instructions

Martin Süßkraut martin.suesskraut at googlemail.com
Tue Sep 29 07:30:25 PDT 2009

On Tue, Sep 29, 2009 at 14:21, Alexandre Gouraud
<alexandre.gouraud at enst-bretagne.fr> wrote:
> Hi Timo,
> Thanks for commenting. I feel like I have to justify why I don't want to use
> QEMU, which is fine since my choice is not frozen actually.
> QEMU is much more than what I need for dynamically instrumenting software.
> My goal is automated testing to find bugs, which can quickly be intensive in
> term of computational load. Thus I am trying to get the smallest (and
> fastest) tool.
> Even using QEMU, I am not sure the piece of code already exists. And if it
> does, I can still extract it and put where I want. My question is really :
> is it a long work (several months) or is it just a matter of two weeks? And
> if it does not already exists, could it mean it is a nonsense, then why?
> Finally about your proposition using valgrind, I think I will stick to
> windows tools because this is what I know better. But it was ironic, wasn't
> it?
You might want to have a look at DynamoRIO:

It is also avialable for Windows.


> Alexandre.
> 2009/9/29 Timo Juhani Lindfors <timo.lindfors at iki.fi>
>> Alexandre Gouraud <alexandre.gouraud at enst-bretagne.fr> writes:
>> > like to write the same kind of thing, but not using QEMU as they claim
>> > in
>> > the paper, but rather with my own pin tool.
>> You could also use valgrind to convert x86 to valgrind's IR and then
>> write a tool to convert that IR to LLVM.
> --
> Alexandre
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

Martin Süßkraut
Dresden University of Technology,
Computer Science Department
Systems Engineering Group
Dresden, Germany

More information about the llvm-dev mailing list