https://gcc.gnu.org/bugzilla/show_bug.cgi?id=127632
--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> --- The trunk branch has been updated by Avinash Jayakar <[email protected]>: https://gcc.gnu.org/g:fadbd0d585193b7c899e4e4288de5bb18549ce46 commit r17-4880-gfadbd0d585193b7c899e4e4288de5bb18549ce46 Author: Avinash Jayakar <[email protected]> Date: Tue Sep 29 13:44:59 2026 +0530 rs6000: (__builtin_atomic_cas_local) Initialize size of type to 0 in altivec_resolve_overloaded_builtin The bootstrap build with the following configure command: configure --enable-checking=release --enable-languages=c,c++,fortran failed since the maybe-uninitialized pass reported the 'size' variable to be unitialized before using it. This case is a false positive because the 'size' variable is accessed only from the second iteration in the loop at which time 'size' would have been initialized. This patch initializes this variable to 0 to get rid of this warning. 2026-10-05 Avinash Jayakar <[email protected]> gcc/ChangeLog: PR target/127632 * config/rs6000/rs6000-c.cc (altivec_resolve_overloaded_builtin): Initialize size to 0.
