[LLVMdev] Hazard recognition using MCInst

[Pankaj Gode]

Dear All,

I am following a flow to generate object files(.o) from input (.s assembly) files. 
The input .s is given to AsmParser, which creates MCInst after matching instruction opcode. 
These MCInst are converted to MCStream and then finally emitting to an object file using Target Code Emitter.

I am considering whether hazard recognition can be done on the list of MCInst, which I get after parsing .s file ??

The hazard recognition available with LLVM, uses 'scheduling DAG of 
Machine Instructions' and Alias Analysis data for checking dependencies.
In my case, do I need to create a Schedule DAG from MCInst ? And moreover, is is possible to create a schedule DAG this way ?

I have read about RevGen and other discussions, on creating LLVM IR from object code. 
I
 understood that they suggest using a 'code dictionary' to convert to 
LLVM Machine Instruction & then create a CFG from the information 
avaiable.
There are limitation to this as the IR is incomplete, as 
pointed by in paper "A compiler level intermediate representation based 
binary analysis and rewriting system", 
mentioned in a discussion here (http://stackoverflow.com/questions/6981810/translation-of-machinecode-into-llvm-ir-disassembly-reassembly-of-x86-64-x86).

I am not sure whether creating scheduling DAG or some intermediate representation on top of MCInst for Hazard recognition makes sense.
Is suggestion on the right approach ?

Regards,
Pankaj
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20140312/1bbaee06/attachment.html>