search for: d41420

...at it has better conformance to VPlan vision going forward (http://www.llvm.org/docs/Proposals/VectorizationPlan.html). All VP*Recipe class definitions are now moved to VPlan.h, and I have a patch under review to move LoopVectorizationPlanner class out of LoopVectorize.cpp (https://reviews.llvm.org/D41420). Next thing I'm working on is LoopVectorizationLegality, and I noticed that it has a component of CostModel and optimization, which doesn't seem right from vectorizer's architectural perspective. It appears that we are currently abusing Legal as the attic to throw a lot of things in o...

...r conformance to VPlan vision going forward > (http://www.llvm.org/docs/Proposals/VectorizationPlan.html). All VP*Recipe class definitions are now > moved to VPlan.h, and I have a patch under review to move LoopVectorizationPlanner class out of > LoopVectorize.cpp (https://reviews.llvm.org/D41420). > > Next thing I'm working on is LoopVectorizationLegality, and I noticed that it has a component of > CostModel and optimization, which doesn't seem right from vectorizer's architectural perspective. > It appears that we are currently abusing Legal as the attic to throw...

...> conformance to VPlan vision going forward > (http://www.llvm.org/docs/Proposals/VectorizationPlan.html). All > VP*Recipe class definitions are now moved to VPlan.h, and I have a patch under review to move LoopVectorizationPlanner class out of LoopVectorize.cpp (https://reviews.llvm.org/D41420). > > Next thing I'm working on is LoopVectorizationLegality, and I noticed > that it has a component of CostModel and optimization, which doesn't seem right from vectorizer's architectural perspective. > It appears that we are currently abusing Legal as the attic to throw...

...onformance to VPlan vision going forward >> (http://www.llvm.org/docs/Proposals/VectorizationPlan.html). All >> VP*Recipe class definitions are now moved to VPlan.h, and I have a patch under review to move LoopVectorizationPlanner class out of LoopVectorize.cpp (https://reviews.llvm.org/D41420). >> >> Next thing I'm working on is LoopVectorizationLegality, and I noticed >> that it has a component of CostModel and optimization, which doesn't seem right from vectorizer's architectural perspective. >> It appears that we are currently abusing Legal as the...

...formance to VPlan vision going forward >> (http://www.llvm.org/docs/Proposals/VectorizationPlan.html). All >> VP*Recipe class definitions are now moved to VPlan.h, and I have a patch under review to move LoopVectorizationPlanner class out of LoopVectorize.cpp (https://reviews.llvm.org/D41420). >> >> Next thing I'm working on is LoopVectorizationLegality, and I noticed >> that it has a component of CostModel and optimization, which doesn't seem right from vectorizer's architectural perspective. >> It appears that we are currently abusing Legal as the...