arm: Fix maybe-uninitialized GCC warnings
authorChun-Chen Hsu <chunchenhsu@google.com>
Tue, 13 Mar 2018 10:24:21 +0000 (18:24 +0800)
committerChun-Chen TK Hsu <chunchenhsu@google.com>
Wed, 14 Mar 2018 11:57:10 +0000 (11:57 +0000)
commit9f8491ecbfb80696b62a5a878fe40f81a8a0d35c
tree2cfbdec2e3de43346b78994ece52a08cbfc2ba22
parent182b44ee37a0e3071c19f1a34300502fff70d860
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>
src/arch/arm/isa/insts/neon64_mem.isa