https://gcc.gnu.org/bugzilla/show_bug.cgi?id=120805
--- Comment #18 from Avinash Jayakar <avinashd at linux dot ibm.com> --- (In reply to Tamar Christina from comment #17) > (In reply to Avinash Jayakar from comment #16) > > Created attachment 61956 [details] > > I have just changed the order within the conditional where the const_vf gets > > assigned, to have it behave in similar way as before (use of log_vf) > > That to me is just a plaster rather than a fix. You've flipped the > initialization of logvf rather than just adding the explicit requirement > that this code can't support epilogues. ok, but adding a statement that it does not support epilogue is also a plaster right? because there can be other cases where LOOP_VINFO_USING_PARTIAL_VECTORS_P (loop_vinfo) is true, and epilogue is just one of them. So if there is a scenario like that, then we would have to not support those cases explicitly. If we are definitely sure that LOOP_VINFO_USING_PARTIAL_VECTORS_P (loop_vinfo) would be true for epilogues only when vf > 0, then the fix you suggested will work. I am not sure if that is the case. If the patch is not convincing, you can take this issue.
