Chris Lattner ddfa57bd7b Instcombine should not promote whole computation trees to "strange" ... integer types, unless they are already strange. This prevents it from turning the code produced by SROA into crazy libcalls and stuff that the code generator can't handle. In the attached example, the result was an i96 multiply that caused the x86 backend to assert. Note that if TargetData had an idea of what the legal types are for a target that this could be used to stop instcombine from introducing i64 muls, as Scott wanted. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@68598 91177308-0d34-0410-b5e6-96231b3b80d8		2009-04-08 05:41:03 +00:00
..
Hello
Instrumentation
IPO	Use a SmallPtrSet instead of std::set.	2009-03-23 23:39:20 +00:00
Scalar	Instcombine should not promote whole computation trees to "strange"	2009-04-08 05:41:03 +00:00
Utils	Update call graph after inlining invoke.	2009-03-31 17:36:12 +00:00
Makefile	I should definitely read make docs someday :(	2009-03-11 20:40:15 +00:00