search for: mulhhu

...,s2) t = INT16(s1) * INT16(s2) #define MULLLU(t,s1,s2) t = UINT16(s1) * UINT16(s2) #define MULLH(t,s1,s2) t = INT16(s1) * INT16((s2) >> 16) #define MULLHU(t,s1,s2) t = UINT16(s1) * UINT16((s2) >> 16) #define MULHH(t,s1,s2) t = INT16((s1) >> 16) * INT16((s2) >> 16) #define MULHHU(t,s1,s2) t = UINT16((s1) >> 16) * UINT16((s2) >> 16) I'm guessing, from what I've seen, I may just need to check in my Pats whether a zext or sext has been used on the value to be operated on..? Thanks, Sam James Molloy-3 wrote: > > Hi Sam, > > I am not a MIPS...

Hi Sam, I am not a MIPS expert by any means, so YMMV, but: MIPS addu only differs to "add" in its (non)setting of the overflow flag. Because LLVM doesn't provide a way via the IR to access the overflow flag, a special notation isn't required in the IR to distinguish the two operations. Do you have another example? Cheers, James -----Original Message----- From:

Thanks for the replies guys but I think I should have phrased my question better... looking at the Mips backend there are machine instructions that operate on signed and unsigned data, such as add and addu. And like Mips, I need to specify unsigned specific instructions, so how do these get chosen between if the LLVM IR does not carry type data? A very general point in the right direction is all i