https://gcc.gnu.org/g:cdb987e977e03ba78a8a0e094967a5121e01f2ce
commit r14-11573-gcdb987e977e03ba78a8a0e094967a5121e01f2ce
Author: Jeff Law <j...@ventanamicro.com>
Date: Sun Jun 9 09:17:55 2024 -0600
[committed] [RISC-V] Fix false-positive uninitialized variable
Andreas noted we were getting an uninit warning after the recent constant
synthesis changes. Essentially there's no way for the uninit analysis code
to
know the first entry in the CODES array is a UNKNOWN which will set X before
its first use.
So trivial initialization with NULL_RTX is the obvious fix.
Pushed to the trunk.
gcc/
* config/riscv/riscv.cc (riscv_move_integer): Initialize "x".
Diff:
---
gcc/config/riscv/riscv.cc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/config/riscv/riscv.cc b/gcc/config/riscv/riscv.cc
index f4a3b96745b6..fe9c8085551b 100644
--- a/gcc/config/riscv/riscv.cc
+++ b/gcc/config/riscv/riscv.cc
@@ -2423,7 +2423,7 @@ riscv_move_integer (rtx temp, rtx dest, HOST_WIDE_INT
value,
struct riscv_integer_op codes[RISCV_MAX_INTEGER_OPS];
machine_mode mode;
int i, num_ops;
- rtx x;
+ rtx x = NULL_RTX;
mode = GET_MODE (dest);
/* We use the original mode for the riscv_build_integer call, because HImode
