search for: loopvectorizercostmodel

...e it dumps the costs of all of the instructions with different vectorization factors, and it also detects the different kinds of shuffles that we support. > As far as I can see, LoopVectorizationCostModel is the class that does all the work, with assistance from the target transform info. The LoopVectorizerCostModel only predicts which IR will be generated when vectorizing to a specific vector width. It uses TTI to get the cost of each IR instruction. Chandler recently refactored TTI (thank!) and now TTI is an analysis group. The BasicTTI attempts to handle all of the target independent logic. It uses the Targ...

Hi Nadav, I'm interested in knowing how you'll work up the ARM cost model and how easy it'd be to split the work. As far as I can see, LoopVectorizationCostModel is the class that does all the work, with assistance from the target transform info. Do you think that updating ARMTTI would be the best course of action now, and inspect the differences in the CostModel later? I also

...also run the vectorizer with -debug-only=loop-vectorize because it dumps > the costs of all of the instructions with different vectorization factors, > and it also detects the different kinds of shuffles that we support. > Hi Nadav, These are great ways of debugging the cost model! The LoopVectorizerCostModel only predicts which IR will be generated when > vectorizing to a specific vector width. It uses TTI to get the cost of each > IR instruction. Chandler recently refactored TTI (thank!) and now TTI is an > analysis group. The BasicTTI attempts to handle all of the target > independent log...