search for: intargetselectiondag

...I tried commenting out all the other instructions definitions and I still get this error. After debugging TblGen I found that the second pattern is being generated as a variant of the first. I think the reason is that the PADD instruction is inheriting the commutative property from ADD defined inTargetSelectionDAG.td. The variant ends up being the same as the original causing the error later on. If all this is correct then how can I mark the node to be non-commutable? I tried using "let isCommutable = 0" in the instruction definition but didn't seem to work. Thanks, Javier On 7/4/2009 3:0...

...other > instructions definitions and I still get this error. After debugging > TblGen I found that the second pattern is being generated as a > variant of the first. I think the reason is that the PADD > instruction is inheriting the commutative property from ADD defined > inTargetSelectionDAG.td. The variant ends up being the same as the > original causing the error later on. If all this is correct then how > can I mark the node to be non-commutable? I tried using "let > isCommutable = 0" in the instruction definition but didn't seem to > work. > &gt...

Are there any other patterns in your TD file? If so, then one of the ones before this pattern will match everything, and this pattern will never be matched. -bw On Jul 3, 2009, at 8:27 PM, Javier Martinez wrote: > Hello, > > I'm new to LLVM and I'm using it to translate from LLVM to another > language rather than emitting actual machine code. The target language > has

Hello, I'm new to LLVM and I'm using it to translate from LLVM to another language rather than emitting actual machine code. The target language has instructions that operate on pointers which aren't naturally exposed in LLVM. Here's what I've done to add pointer support for an instruction called PADD that takes a pointers and an offset and returns the new pointer value: