[LLVMdev] More Back-End Porting Troubles

[Villmow, Micah]

If you do dump(CurDAG) then it will resolve machine nodes for you. See llvm/include/llvm/CodeGen/SelectionDAGNodes.h

From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Cameron McInally
Sent: Wednesday, August 15, 2012 10:23 AM
To: Fabian Scheler
Cc: LLVM Developers Mailing List
Subject: Re: [LLVMdev] More Back-End Porting Troubles

On Wed, Aug 15, 2012 at 12:11 PM, Fabian Scheler <fabian.scheler at gmail.com<mailto:fabian.scheler at gmail.com>>wrote:
Hi LLVM-Folks,
 ...
Currently, I am not even able to find out which instruction is messed
up here  (dumping the node via the dump-Method yields "<<Unknown
Machine Node #65434>>"). Can I use "machine nodes" and "normal nodes"
when lowering a specific instruction within the TargetLowering?

Usually, when I see this type of error in the X86 target, I use the following function to narrow down the search:

>    /// getTargetNodeName - This method returns the name of a target specific
>    /// DAG node.
>    virtual const char *getTargetNodeName(unsigned Opcode) const;

If I'm not mistaken, the normal dump method returns names for ISD Opcodes and not for target specific opcodes, in my case X86ISD Opcodes.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20120815/d11ed03f/attachment.html>