https://gcc.gnu.org/bugzilla/show_bug.cgi?id=127677
--- Comment #2 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tamar Christina <[email protected]>: https://gcc.gnu.org/g:d7bd302654fab2ddd8d7e8539f163db63a2f07e5 commit r17-4830-gd7bd302654fab2ddd8d7e8539f163db63a2f07e5 Author: Tamar Christina <[email protected]> Date: Fri Oct 2 13:20:24 2026 +0100 vect: Fix scalar iteration bounds when doing alignment peeling with partial vectors [PR127677] static unsigned int list[32] __attribute__((aligned(64))); __attribute__((noinline, noipa)) static int contains (const unsigned int *p, unsigned int count, unsigned int start, unsigned int key) { for (unsigned int i = start; i < count; ++i) if (p[i] == key) return 1; return 0; } int main (void) { return contains (list, 2, 1, 1); } when compiled on RISC-V with -O3 -march=rv64gcv_zvl256b -mabi=lp64d -mrvv-vector-bits=zvl -mrvv-max-lmul=m2 -g0 shows bnd.9_47 = niters.5_27 - prolog_loop_niters.7_31; _63 = (unsigned long) bnd.9_47; ... and so if niters is lower than prolog iters we get an underflow. i.e. niters = count - start = 2 - 1 = 1 prolog_niters = 7 so when it calculates the remainder remaining = niters - prolog_niters; this underflows: 1 - 7 = 4294967290 Normally we don't get here for AArch64 and x86_64 because of the different paths they take in vectorization. For SVE we perform the loop fully masked, including trailing elements. for Adv. SIMD and x86_64 we insert a peeling check. _46 = niters - 1 = 0; _48 = MAX(peel + 3, 5); // at least 5 if (0 < _48) goto bb26; which skips the alignment peeling prologue. Prior to 8af2e8e49d6e5d33c01c2beaead4933bc286974c we would have generated an epilog for the early break and alignment peeling. The change removed the requirement for an epilog for early break loops which don't have side-effects, but still required alignment peeling. This exposed that the checks in vect_do_peeling generate the epilog and so the iteration check only when poly_uint64 bound_epilog = 0; if (!LOOP_VINFO_USING_PARTIAL_VECTORS_P (loop_vinfo) && LOOP_VINFO_PEELING_FOR_NITER (loop_vinfo)) bound_epilog += vf - 1; if (LOOP_VINFO_PEELING_FOR_GAPS (loop_vinfo)) bound_epilog += 1; so if LOOP_VINFO_USING_PARTUAL_VECTORS_P then no epilog or check is generated. This means that vect_gen_prolog_loop_niters needs to in itself handle this assumption. This is easy to do by generating a MIN (niters, prolog_niters) check. If the guard is generated this will be optimized out, but if not, it makes the prolog peeling loop handle the "scalar" iterations itself without needing a second scalar loop. gcc/ChangeLog: PR tree-optimization/127677 * tree-vect-loop-manip.cc (vect_gen_prolog_loop_niters): Generate MIN expression on niters. gcc/testsuite/ChangeLog: PR tree-optimization/127677 * gcc.dg/vect/vect-early-break_146-pr127677.c: New test.
