diff options
author | Sergio Durigan Junior <sergiodj@redhat.com> | 2017-09-21 11:46:48 -0400 |
---|---|---|
committer | Sergio Durigan Junior <sergiodj@redhat.com> | 2017-09-25 01:46:23 -0400 |
commit | 57a024f4650d7562e963efb6b00c4a4cd74185c4 (patch) | |
tree | 2bac6744075de9a5f18cebbab9cd60003bb55b7f /bfd/ChangeLog | |
parent | 5b3fd0aac2b70d860ba34f0e290d87773b09bd11 (diff) | |
download | gdb-57a024f4650d7562e963efb6b00c4a4cd74185c4.zip gdb-57a024f4650d7562e963efb6b00c4a4cd74185c4.tar.gz gdb-57a024f4650d7562e963efb6b00c4a4cd74185c4.tar.bz2 |
Initialize 'imm' on opcodes/aarch64-opc.c:expand_fp_imm (and fix breakage on mingw)
Hi,
While compiling GDB using a mingw compiler from Fedora 26:
../gdb/configure --host=x86_64-w64-mingw32 --target=x86_64-w64-mingw32 \
--disable-binutils --disable-ld --disable-gold --disable-gas --disable-sim \
--disable-gprof --enable-targets=all
I stumbled upon a simple occurrence of -Werror=maybe-uninitialized:
../../gdb/opcodes/aarch64-opc.c: In function 'expand_fp_imm':
../../gdb/opcodes/aarch64-opc.c:2880:10: error: 'imm' may be used uninitialized in this function [-Werror=maybe-uninitialized]
return imm;
^~~
It is the compiler's fault, because this function always assigns to
'imm' if the necessary conditions are met, and it calls "assert (0)"
otherwise, but I thought it'd be clearer to have 'imm' explicitly set
to zero anyway.
opcodes/ChangeLog:
2017-09-21 Sergio Durigan Junior <sergiodj@redhat.com>
* aarch64-opc.c (expand_fp_imm): Initialize 'imm'.
Diffstat (limited to 'bfd/ChangeLog')
0 files changed, 0 insertions, 0 deletions