[PATCH] D28975: [LV] Introducing VPlan to model the vectorized code and drive its transformation

[Jonas Paulsson via Phabricator via llvm-commits]

jonpa added a comment.

Hi,

I have been working with improving cost estimates in the LoopVectorizer a bit. I wonder if VPlan will improve cost estimation for different VFs, including 1?

One issue currently that I don't know yet quite how to tackle, is that two scalarized instructions (def->use), have too big of scalarization costs computed, since the inserts from the first, and the extracts of the second will be optimized away. There are also several other minor issues I have found so far. I guess I should probably wait for VPlan to arrive before trying anything... Is that going to be anytime soon?

Looking forward to this

/Jonas


https://reviews.llvm.org/D28975