Scott Michel 3ad0263173 Make tblgen a little smarter about constants smaller than i32. Currently, ... tblgen will complain if a sign-extended constant does not fit into a data type smaller than i32, e.g., i16. This causes a problem when certain hex constants are used, such as 0xff for byte masks or immediate xor values. tblgen will try the sign-extended value first and, if the sign extended value would overflow, it tries to see if the unsigned value will fit. Consequently, a software developer can now safely incant: (XORHIr16 R16C:$rA, 0xffff) which is somewhat clearer and more informative than incanting: (XORHIr16 R16C:$rA, (i16 -1)) even if the two are bitwise equivalent. Tblgen also outputs the 64-bit unsigned constant in the generated ISel code when getTargetConstant() is invoked. llvm-svn: 47188		2008-02-15 23:05:48 +00:00
..
llvm	Make tblgen a little smarter about constants smaller than i32. Currently,	2008-02-15 23:05:48 +00:00
llvm-c	Fixing a bug creating floating point constants of type other	2008-02-02 01:07:50 +00:00