Nadav Rotem a675c74208 ARM Cost Model: We need to detect the max bitwidth of types in the loop in order to select the max vectorization factor. ... We don't have a detailed analysis on which values are vectorized and which stay scalars in the vectorized loop so we use another method. We look at reduction variables, loads and stores, which are the only ways to get information in and out of loop iterations. If the data types are extended and truncated then the cost model will catch the cost of the vector zext/sext/trunc operations. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@172178 91177308-0d34-0410-b5e6-96231b3b80d8		2013-01-11 07:11:59 +00:00
..
BBVectorize.cpp	Switch BBVectorize to directly depend on having a TTI analysis.	2013-01-07 10:22:36 +00:00
CMakeLists.txt	Add a loop vectorizer.	2012-10-17 18:25:06 +00:00
LLVMBuild.txt
LoopVectorize.cpp	ARM Cost Model: We need to detect the max bitwidth of types in the loop in order to select the max vectorization factor.	2013-01-11 07:11:59 +00:00
Makefile
Vectorize.cpp	LoopVectorizer: Use the "optsize" attribute to decide if we are allowed to increase the function size.	2012-12-12 19:29:45 +00:00