search for: loopvectorizationanalysisinfo

...ctural perspective. It appears that we are currently abusing Legal as the attic to throw a lot of things in order to avoid 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 (in...

...ive. > It appears that we are currently abusing Legal as the attic to throw a lot of things in order to avoid 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 Analy...

...ppears that we are currently abusing Legal as the attic to throw a > lot of things in order to avoid 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 subtre...

...we are currently abusing Legal as the attic to throw a >> lot of things in order to avoid 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 su...

...re currently abusing Legal as the attic to throw >> a lot of things in order to avoid 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 su...