On 6/7/24 11:49 AM, Andreas Schwab wrote:
In file included from ../../gcc/rtl.h:3973,
from ../../gcc/config/riscv/riscv.cc:31:
In function 'rtx_def* init_rtx_fmt_ee(rtx, machine_mode, rtx, rtx)',
inlined from 'rtx_def* gen_rtx_fmt_ee_stat(rtx_code, machine_mode, rtx,
rtx)' at ./genrtl.h:50:26,
inlined from 'void riscv_move_integer(rtx, rtx, long int, machine_mode)'
at ../../gcc/config/riscv/riscv.cc:2786:10:
./genrtl.h:37:16: error: 'x' may be used uninitialized
[-Werror=maybe-uninitialized]
37 | XEXP (rt, 0) = arg0;
../../gcc/config/riscv/riscv.cc: In function 'void riscv_move_integer(rtx, rtx,
long int, machine_mode)':
../../gcc/config/riscv/riscv.cc:2723:7: note: 'x' was declared here
2723 | rtx x;
| ^
cc1plus: all warnings being treated as errors
Thanks. I guess the change in control flow in there does hide x's state
pretty well. It may not even be provable as initialized without knowing
how this routine interacts with the costing phase that fills in the codes.
I'll take care of it.
Thanks again,
jeff
