Re: [Capstone-users] LLVM Bitcode as Input File

[Nguyen A. Q. <aq...@gm...>]

On Tue, Sep 16, 2014 at 9:51 PM, Peter Lucia <pe...@ro...> wrote:

> Any thoughts on how hard it would be to implement?  Note that I'm only
> trying to go to LLVM assembly code, not some other architecture's assembly
> code.  Thanks
>

do you mean generating machine code from LLVM bitcode? this involves the
backends of all related archs, and is quite different from what Capstone is
doing. so extending Capstone to do this is not the choice, but you need to
do that from scratch.

to have a better idea, look at the source of llvm-dis. that is certainly a
lot of works.


cheers,
Q




> Peter
>
> On Tue, Sep 16, 2014 at 8:24 AM, Nguyen Anh Quynh <aq...@gm...>
> wrote:
>
>>
>>
>> On Tue, Sep 16, 2014 at 6:20 AM, Peter Lucia <pe...@ro...> wrote:
>>
>>> Hello,
>>>
>>> Is LLVM Bitcode itself a supported input architecture?  I have some
>>> files that have not yet been fully compiled to PowerPC or MIPS, but instead
>>> are still in LLVM Bitcode format (in other words, clang with the -emit-
>>> llvm option) and I'd love to use capstone to disassemble them
>>> pragmatically.
>>>
>>> If this is not already implemented, how hard would it be to do?  Is
>>> there some other better way to do this?  I'm using llvm-dis now, but it's
>>> not ideal for all the reasons capstone would seem to excel.
>>>
>>>
>> unfortunately no. the main idea of Capstone is to disassemble machine
>> binary code back to assembly code. so Capstone does not, and will never
>> convert LLVM bitcode back to assembly for you.
>>
>>
>> thanks.
>> Q
>>
>
>