diff options
author | Andreas Arnez <arnez@linux.ibm.com> | 2020-07-29 19:46:44 +0200 |
---|---|---|
committer | Andreas Arnez <arnez@linux.ibm.com> | 2020-07-29 19:46:44 +0200 |
commit | 9811697376b3f1950419ab13b19e2995703b839b (patch) | |
tree | a7b1a220104d285867830af766018a70828700b8 /binutils/winduni.c | |
parent | 90fd07fcd3e6af8679df55b67482d5c8ab8dd9b9 (diff) | |
download | gdb-9811697376b3f1950419ab13b19e2995703b839b.zip gdb-9811697376b3f1950419ab13b19e2995703b839b.tar.gz gdb-9811697376b3f1950419ab13b19e2995703b839b.tar.bz2 |
PR26279 Work around maybe-uninitialized warning in s390-mkopc.c
In s390-mkopc.c, the function insertExpandedMnemonic() searches for the
first occurrence of '*' or '$' in the given mnemonic, and, if a match is
found, chooses an extension table using a switch() on that character. The
switch statement contains a default case that prints an error message and
does not set the extension table. Although this case cannot occur, some
GCC versions obviously conclude that the extension table might have been
left uninitialized after the switch statement and consequently emit
maybe-uninitialized warnings for the variables 'ext_table' and
'ext_table_length'.
Circumvent the warning by handling the unreachable default case with
abort().
opcodes/
* s390-mkopc.c (insertExpandedMnemonic): Handle unreachable
default case with abort() instead of printing an error message and
continuing, to avoid a maybe-uninitialized warning.
Diffstat (limited to 'binutils/winduni.c')
0 files changed, 0 insertions, 0 deletions