Chandler Carruth b778cbc0c8 [canonicalize] Teach InstCombine to canonicalize loads which are only ... ever stored to always use a legal integer type if one is available. Regardless of whether this particular type is good or bad, it ensures we don't get weird differences in generated code (and resulting performance) from "equivalent" patterns that happen to end up using a slightly different type. After some discussion on llvmdev it seems everyone generally likes this canonicalization. However, there may be some parts of LLVM that handle it poorly and need to be fixed. I have at least verified that this doesn't impede GVN and instcombine's store-to-load forwarding powers in any obvious cases. Subtle cases are exactly what we need te flush out if they remain. Also note that this IR pattern should already be hitting LLVM from Clang at least because it is exactly the IR which would be produced if you used memcpy to copy a pointer or floating point between memory instead of a variable. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@226781 91177308-0d34-0410-b5e6-96231b3b80d8		2015-01-22 05:08:12 +00:00
..
Hello
InstCombine	[canonicalize] Teach InstCombine to canonicalize loads which are only	2015-01-22 05:08:12 +00:00
Instrumentation
IPO
ObjCARC
Scalar
Utils
Vectorize
CMakeLists.txt
LLVMBuild.txt
Makefile