search for: interleaveinfo

...id passing many pointers around. From vectorizer's architectural point of view, we should distinguish Legal from "Vectorization Context Information" (I'd call it LoopVectorizationAnalysisInfo), some of which (such as induction, reduction, etc.) are populated during the Legal step. InterleaveInfo shouldn't even be a member of Legal. Nothing to do with Legality. It would be a good member of LoopVectorizationAnalysisInfo. Eventually, I'd like to see these under Analysis subtree (instead of Transform), since they are indeed Analysis. As a first step of this LoopVectorizationLegality c...

...many pointers around. From vectorizer's architectural point of view, we should distinguish Legal from > "Vectorization Context Information" (I'd call it LoopVectorizationAnalysisInfo), some of which (such as > induction, reduction, etc.) are populated during the Legal step. InterleaveInfo shouldn't even be > a member of Legal. Nothing to do with Legality. It would be a good member of LoopVectorizationAnalysisInfo. > Eventually, I'd like to see these under Analysis subtree (instead of Transform), since they are indeed Analysis. > > As a first step of this LoopVec...

...inters around. From > vectorizer's architectural point of view, we should distinguish Legal > from "Vectorization Context Information" (I'd call it > LoopVectorizationAnalysisInfo), some of which (such as induction, reduction, etc.) are populated during the Legal step. InterleaveInfo shouldn't even be a member of Legal. Nothing to do with Legality. It would be a good member of LoopVectorizationAnalysisInfo. > Eventually, I'd like to see these under Analysis subtree (instead of Transform), since they are indeed Analysis. > > As a first step of this LoopVectoriz...

...ound. From >> vectorizer's architectural point of view, we should distinguish Legal >> from "Vectorization Context Information" (I'd call it >> LoopVectorizationAnalysisInfo), some of which (such as induction, reduction, etc.) are populated during the Legal step. InterleaveInfo shouldn't even be a member of Legal. Nothing to do with Legality. It would be a good member of LoopVectorizationAnalysisInfo. >> Eventually, I'd like to see these under Analysis subtree (instead of Transform), since they are indeed Analysis. >> >> As a first step of this L...

...d. From >> vectorizer's architectural point of view, we should distinguish Legal >> from "Vectorization Context Information" (I'd call it >> LoopVectorizationAnalysisInfo), some of which (such as induction, reduction, etc.) are populated during the Legal step. InterleaveInfo shouldn't even be a member of Legal. Nothing to do with Legality. It would be a good member of LoopVectorizationAnalysisInfo. >> Eventually, I'd like to see these under Analysis subtree (instead of Transform), since they are indeed Analysis. >> >> As a first step of this L...

...aced at the beginning of Transform Step: // Notice: any optimization or new instruction that go // into the code below should be also be implemented in // the cost-model. 2. Legal Step does more than check for vectorizability; e.g., it records auxiliary artifacts such as collectLoopUniforms() and InterleaveInfo. 3. Transform Step first populates the single basic block of the vectorized loop and later revisits scalarized instructions to predicate them one by one, as needed. Proposal: introduce the Vectorization Plan as an explicit model of a vectorization candidate and update the overall flow: 1. Lega...