[llvm] [LoopVectorize] Enable vectorisation of early exit loops with live-outs (PR #120567)

[Florian Hahn via llvm-commits]

https://github.com/fhahn commented:

Thanks for the updates, a few small comments left

> Hi @fhahn, the Windows build is complaining about getExitBlocks that is called from the new isExitBlock function. The error is:
> 
> C:\BuildTools\VC\Tools\MSVC\14.29.30133\include\xutility(1378): error C2280: 'llvm::filter_iterator_impl<llvm::mapped_iterator<IteratorT,FuncTy,BlockTy *>,llvm::VPlan::getExitBlocks::<lambda_38c1aefa419e66528297efd947a86d73>,llvm::detail::fwd_or_bidi_tag_impl<false>::type> &llvm::filter_iterator_impl<llvm::mapped_iterator<IteratorT,FuncTy,BlockTy *>,llvm::VPlan::getExitBlocks::<lambda_38c1aefa419e66528297efd947a86d73>,llvm::detail::fwd_or_bidi_tag_impl<false>::type>::operator =(const llvm::filter_iterator_impl<llvm::mapped_iterator<IteratorT,FuncTy,BlockTy *>,llvm::VPlan::getExitBlocks::<lambda_38c1aefa419e66528297efd947a86d73>,llvm::detail::fwd_or_bidi_tag_impl<false>::type> &)': attempting to reference a deleted function
>         with
> ...
> It's not immediately obvious to me that this is a problem with isExitBlock and possibly a problem with getExitBlocks or some assumption about the function is used. I'll investigate this a bit further, but I may just have to remove the assert for now.

Sounds good, it looks like it may not be playing nicely with is_contained for some reason. I also don't have a windows machine to check this.

https://github.com/llvm/llvm-project/pull/120567