summaryrefslogtreecommitdiff
path: root/src/arch
diff options
context:
space:
mode:
authorChun-Chen Hsu <chunchenhsu@google.com>2018-03-13 18:24:21 +0800
committerChun-Chen TK Hsu <chunchenhsu@google.com>2018-03-14 11:57:10 +0000
commit9f8491ecbfb80696b62a5a878fe40f81a8a0d35c (patch)
tree2cfbdec2e3de43346b78994ece52a08cbfc2ba22 /src/arch
parent182b44ee37a0e3071c19f1a34300502fff70d860 (diff)
downloadgem5-9f8491ecbfb80696b62a5a878fe40f81a8a0d35c.tar.xz
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>
Diffstat (limited to 'src/arch')
-rw-r--r--src/arch/arm/isa/insts/neon64_mem.isa3
1 files changed, 2 insertions, 1 deletions
diff --git a/src/arch/arm/isa/insts/neon64_mem.isa b/src/arch/arm/isa/insts/neon64_mem.isa
index 4d3241226..4511ad105 100644
--- 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