arm: Fix maybe-uninitialized GCC warnings

GCC 7 generates maybe-uninitialized warnings at the code that updates
the "dest" variables in the writeVecElem function of neon64_mem.hh file.
It is because the generated code does not appropriately initialize the
output variable before passing it to the writeVecElem function.  This
patch initializes the output variable to fix this.

Change-Id: I50a8f4e456ccdcaa3db1392ec097017450c56ecb
Signed-off-by: Chun-Chen Hsu <chunchenhsu@google.com>
Reviewed-on: https://gem5-review.googlesource.com/9121
Reviewed-by: Jason Lowe-Power <jason@lowepower.com>
Reviewed-by: Andreas Sandberg <andreas.sandberg@arm.com>
Maintainer: Andreas Sandberg <andreas.sandberg@arm.com>

diff --git a/src/arch/arm/isa/insts/neon64_mem.isa b/src/arch/arm/isa/insts/neon64_mem.isa
index 4d32412266ac7d83ac9958c53832404e649489e4..4511ad105249c3e6916801715eff786180378e50 100644 (file)
--- a/src/arch/arm/isa/insts/neon64_mem.isa
+++ b/src/arch/arm/isa/insts/neon64_mem.isa
@@ -336,7 +336,8 @@ let {{
             eCode = '''
                 //input data from scratch area
                 VReg input[4] = { {0, 0}, {0, 0}, {0, 0}, {0, 0} };
-                VReg output[2];  //output data to arch. SIMD regs
+                //output data to arch. SIMD regs
+                VReg output[2] = { {0, 0}, {0, 0} };
             '''
 
             eCode += getInputCodeOp1L