diff options
author | Tom Tromey <tromey@redhat.com> | 2012-11-02 18:53:54 +0000 |
---|---|---|
committer | Tom Tromey <tromey@redhat.com> | 2012-11-02 18:53:54 +0000 |
commit | d4fb63e140aed000a5c6a9d463e616d8409b56f4 (patch) | |
tree | 58cbf07d01be1182347c4a382277313f515acee2 /gdb/s390-tdep.c | |
parent | b786c521573fce15b05c4b879e05f9cc592e1e4b (diff) | |
download | fsf-binutils-gdb-d4fb63e140aed000a5c6a9d463e616d8409b56f4.zip fsf-binutils-gdb-d4fb63e140aed000a5c6a9d463e616d8409b56f4.tar.gz fsf-binutils-gdb-d4fb63e140aed000a5c6a9d463e616d8409b56f4.tar.bz2 |
* configure: Rebuild.
* configure.ac (build_warnings): Add -Wempty-body.
* m68k-tdep.c (m68k_gdbarch_init): Remove empty 'if'.
* remote.c (handle_notification): Use braces for empty 'else' body.
* s390-tdep.c (s390_analyze_prologue): Use braces for empty
'else' body.
* sh64-tdep.c (sh64_push_dummy_call): Use braces for empty
'else' body.
* solib-som.c (som_relocate_section_addresses): Use braces
for empty 'else' body.
* ui-file.c (stdio_file_write): Use braces for empty 'if' body.
(stdio_file_write_async_safe, stdio_file_fputs): Likewise.
Diffstat (limited to 'gdb/s390-tdep.c')
-rw-r--r-- | gdb/s390-tdep.c | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/gdb/s390-tdep.c b/gdb/s390-tdep.c index 6cd6fd4..0af6f51 100644 --- a/gdb/s390-tdep.c +++ b/gdb/s390-tdep.c @@ -1461,13 +1461,14 @@ s390_analyze_prologue (struct gdbarch *gdbarch, break; else - /* An instruction we don't know how to simulate. The only - safe thing to do would be to set every value we're tracking - to 'unknown'. Instead, we'll be optimistic: we assume that - we *can* interpret every instruction that the compiler uses - to manipulate any of the data we're interested in here -- - then we can just ignore anything else. */ - ; + { + /* An instruction we don't know how to simulate. The only + safe thing to do would be to set every value we're tracking + to 'unknown'. Instead, we'll be optimistic: we assume that + we *can* interpret every instruction that the compiler uses + to manipulate any of the data we're interested in here -- + then we can just ignore anything else. */ + } /* Record the address after the last instruction that changed the FP, SP, or backlink. Ignore instructions that changed |