[LLVMdev] Auxiliary operand types for disassembler.

[Jim Grosbach]

Hi Sid,

This feels like it’s exposing too much of the disassembler internals into the MCOperand representation. I’m not sure I follow why that’s necessary. Can you elaborate a bit?

-Jim

On Jun 25, 2013, at 8:24 AM, Sid Manning <sidneym at codeaurora.org> wrote:

> 
> I'm working on a disassembler for hexagon (vliw) architecture and I would like to add an additional operand type, "kAux" to the MCOperand class.
> 
> The reason for this is that each insn has parse bits which are not explicit operands and have differing meanings based on the insn's location within the packet and the number of insns inside the packet. In order for the disassembler to correctly represent the insn it needs to accumulate the series of insns that form the packet. Only when the entire packet is known can the meaning of the parse bits be properly interpreted.
> 
> Changing objdump's interface to printInst so it passes the raw insn bits down would allow the printer to accumulate the same information and would work just as well I think.
> 
> -- 
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation
> <MCInst.h.diff>_______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130625/e7dfd693/attachment.html>