Add UseVPlanNative path boolean to inform when to use VPlan native path, removed unnecessary assert modification from earlier and update the test case. Now vectorizing inner loop produces the same vectorized code when VPlan native path flag is enabled and not enabled.

Add test cases for different select conditions and clean up test to only check relevant widened select lines. I checked other tests that other people have written and some of them also check for the relevant lines only, not all lines generated by the python script. So I did the same. Any opinions is this a preferred way?

Change and bare minimum test case

Removed use of PredicatedScalarEvolution and use ScalaEvolution instead to clean up diff.

Call instruction widening as a separate patch here: https://reviews.llvm.org/D97278

Rebase with latest changes, add support for select instruction widening only in this patch and add test case for it. Add call instruction widening as a separate patch later.

Fix failing unit tests.

Accidentally duplicated this with arcanist. Original diff here: https://reviews.llvm.org/D97136

Add support to widen call and select instructions in VPlan native path by using correct recipes when such instruction is encountered. This is already used by inner loop vectorizer. I modified my previously committed VPlan test to also test for the call instruction widening.

Thank you!

Ping! Does someone want to commit this for me with the name Mauri Mustonen and email mauri_mustonen@hotmail.com, thanks!

Squashed diff. And I need someone to commit this change for me. It can be done with the name Mauri Mustonen and email mauri_mustonen@hotmail.com, thanks.

Typed all used LLVM intrinsic functions.

Updated FileCheck to check more detailed about vectorized basic blocks. But I'd still want to get some pointers. Is this now too detailed checking and making the check too brittle for changes?

I need someone else to commit this patch for me. Commit can be made with name Mauri Mustonen and email mauri_mustonen@hotmail.com.