Displaying 3 results from an estimated 3 matches for "bricc".
Did you mean:
brick
2008 Sep 19
0
[LLVMdev] Custom Opcodes versus built-in opcodes
...I'm wrong, sorry about that. It looks like the encoding is
in the definition of the enum:
enum {
FIRST_NUMBER = ISD::BUILTIN_OP_END+SP::INSTRUCTION_LIST_END,
CMPICC, // Compare two GPR operands, set icc.
CMPFCC, // Compare two FP operands, set fcc.
BRICC, // Branch to dest on icc condition
BRFCC, // Branch to dest on fcc condition
...
Are your "targetISD" enums properly defined with the offset?
getTargetNode is required when passing in MachineInstr opcode numbers
at isel time.
-Chris
-------------- next part -----...
2016 Apr 27
2
[Sparc] builtin setjmp / longjmp - need help to get past last problem
...****
const char *SparcTargetLowering::getTargetNodeName(unsigned Opcode) const {
switch ((SPISD::NodeType)Opcode) {
! case SPISD::FIRST_NUMBER: break;
! case SPISD::CMPICC: return "SPISD::CMPICC";
! case SPISD::CMPFCC: return "SPISD::CMPFCC";
! case SPISD::BRICC: return "SPISD::BRICC";
! case SPISD::BRXCC: return "SPISD::BRXCC";
! case SPISD::BRFCC: return "SPISD::BRFCC";
! case SPISD::SELECT_ICC: return "SPISD::SELECT_ICC";
! case SPISD::SELECT_XCC: return "SPISD::SELECT_XCC";
! ca...
2008 Sep 19
2
[LLVMdev] Custom Opcodes versus built-in opcodes
________________________________
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu]
On Behalf Of Chris Lattner
Sent: Friday, September 19, 2008 10:49 AM
To: LLVM Developers Mailing List
Subject: Re: [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