llvm dev - Sep 2009 - [LLVMdev] converting x86 instructions to LLVM instructions

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?

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20090929/7a3beba0/attachment.html>

Hi,

Alexandre Gouraud <alexandre.gouraud at enst-bretagne.fr>
writes:
> if it does not already exists, could it mean it is a nonsense, then why?
Why don't you compile your program directly to LLVM bitcode?

Alexandre Gouraud wrote:
> 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?
The problem is that x86 has a very complex instruction set, and decoding it
all takes a lot of software.  Valgrind already has the tools to do this
decoding, so it's definitely something I would consider.  After all,
Valgrind already does much of what you're trying to do.

Andrew.

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:
http://code.google.com/p/dynamorio/

It is also avialable for Windows.

Martin
>
> 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
http://wwwse.inf.tu-dresden.de

>
> You might want to have a look at DynamoRIO:
> http://code.google.com/p/dynamorio/
>
> It is also avialable for Windows.
>
Thanks Martin,

I know dynamorio, but I think it is almost the same thing as Pin.
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20090929/1119e912/attachment.html>