Ulrich Drepper via Gcc <[email protected]> writes: > For two weeks bootstrapping gcc does not work anymore for me since -Werror > is used. The problem appears in stage 2, the previous stage works. This > is on Fedora 44 with gcc 16.1.1: > > /home/drepper/gnu/gcc/gcc/tree-vect-stmts.cc: In function ‘bool > vectorizable_load(vec_info*, stmt_vec_info, gimple_stmt_iterator*, > slp_tree, stmt_vector_for_cost*)’: > /home/drepper/gnu/gcc/gcc/tree-vect-stmts.cc:10408:47: error: ‘stride_step’ > may be used uninitialized [-Werror=maybe-uninitialized] > 10408 | = gimple_build_assign (newoff, > POINTER_PLUS_EXPR, > | > ~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~ > 10409 | running_off, > stride_step); > | > ~~~~~~~~~~~~~~~~~~~~~~~~~ > /home/drepper/gnu/gcc/gcc/tree-vect-stmts.cc:10156:25: note: ‘stride_step’ > was declared here > 10156 | tree stride_base, stride_step, alias_off; > | ^~~~~~~~~~~ > > > This seems legit. Since this is the trunk version I have filed a bug. > Should I?
It's https://gcc.gnu.org/PR125318. --disable-werror is a workaround or using --enable-checking=yes (or not passing --enable-checking=release, as the default on trunk is yes,extra).
signature.asc
Description: PGP signature
