search for: addrr_np

...Hexagon architecture allows instructions in various formats. For example, we have 3 variations of the add instruction as defined below: ADDrr : r1 = add(r2, r3) --> add 2 32-bit registers ADDrr_p : if(p0) r1 = add(r2, r3) --> predicated version of ADDrr instruction, executed when p0 is true ADDrr_np : if(!p0) r1 = add(r2, r3) --> predicated version of ADDrr instruction, executed when p0 is false Currently, we rely on switch tables to transform between formats. However, we would like to have a different mechanism to represent these relationships instead of switch tables. I am thinking of m...

...sInstr'. > > For example: > class Relations { > Instruction ThisInstr; > Instruction BaseForm; > Instruction TruePred; > Instruction FalsePred; > } > > def Rel_ADDrr : Relations<ADDrr, ADDrr, ADDrr_p, ADDrr_np>; > def Rel_ADDrr_p: Relations<ADDrr_p, ADDrr, , >; > def Rel_ADDrr_np : Relations<ADDrr_np,ADDrr, , >; The problem is, this isn't really any better than having a large switch statement. You just moved the table into the .td file. You should be taking advantage of the ins...

...sInstr'. > > For example: > class Relations { > Instruction ThisInstr; > Instruction BaseForm; > Instruction TruePred; > Instruction FalsePred; > } > > def Rel_ADDrr : Relations<ADDrr, ADDrr, ADDrr_p, ADDrr_np>; def > Rel_ADDrr_p: Relations<ADDrr_p, ADDrr, , >; def Rel_ADDrr_np : > Relations<ADDrr_np,ADDrr, , >; The problem is, this isn't really any better than having a large switch statement. You just moved the table into the .td file. You should be taking advantage of the i...