Displaying 4 results from an estimated 4 matches for "fpcondccodetofcc".
2008 Sep 19
2
[LLVMdev] Custom Opcodes versus built-in opcodes
...here that getTargetNode is the preferred method
to use in a Custom Lowering function? Even the other backends use
getNode in their lowering functions with custom opcodes.
This is from SparcISelLowering.cpp
CompareFlag = DAG.getNode(SPISD::CMPFCC, MVT::Flag, LHS, RHS);
if (SPCC == ~0U) SPCC = FPCondCCodeToFCC(CC);
Opc = SPISD::BRFCC;
}
return DAG.getNode(Opc, MVT::Other, Chain, Dest,
DAG.getConstant(SPCC, MVT::i32), CompareFlag);
Micah
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/atta...
2008 Sep 19
0
[LLVMdev] Custom Opcodes versus built-in opcodes
...the preferred
> method to use in a Custom Lowering function? Even the other backends
> use getNode in their lowering functions with custom opcodes.
> This is from SparcISelLowering.cpp
> CompareFlag = DAG.getNode(SPISD::CMPFCC, MVT::Flag, LHS, RHS);
> if (SPCC == ~0U) SPCC = FPCondCCodeToFCC(CC);
> Opc = SPISD::BRFCC;
> }
> return DAG.getNode(Opc, MVT::Other, Chain, Dest,
> DAG.getConstant(SPCC, MVT::i32), CompareFlag);
Actually, I'm wrong, sorry about that. It looks like the encoding is
in the definition of the enum:
enum {...
2008 Sep 19
0
[LLVMdev] Custom Opcodes versus built-in opcodes
On Sep 18, 2008, at 4:04 PM, Villmow, Micah wrote:
> I am using lowering instructions and using custom opcodes that I can
> more easily directly map to my backend. These opcodes are then used
> to emit a custom set of instructions into the MachineBasicBlock.
> I’ve been able to get one to work correctly, however, I’ve ran into
> an issue where my second one is being
2008 Sep 18
4
[LLVMdev] Custom Opcodes versus built-in opcodes
I am using lowering instructions and using custom opcodes that I can
more easily directly map to my backend. These opcodes are then used to
emit a custom set of instructions into the MachineBasicBlock. I've been
able to get one to work correctly, however, I've ran into an issue where
my second one is being confused as a FRAMEADDR opcode instead of my
opcode.
DValue