[PATCH] D57837: [LV] Prevent interleaving if computeMaxVF returned None.

[Hideki Saito via Phabricator via llvm-commits]

hsaito added a comment.

In D57837#1387830 <https://reviews.llvm.org/D57837#1387830>, @fhahn wrote:

> Agreed, having it done implicitly in a function called computeMaxVF does not seem ideal. From the current behavior of computeMaxVF, I think what we actually want to decide whether to disable interleaving up front is just if we optimize for size or not. What do you think?


That was my conclusion as well.

With that understanding, your current direction is

  If VPlan is not built for vectorization purposes, also bail out on interleaving. ---- Work on enabling interleaving in a subsequent patch.

and I'm fine with that approach.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D57837/new/

https://reviews.llvm.org/D57837