aboutsummaryrefslogtreecommitdiff
path: root/config.sub
diff options
context:
space:
mode:
authorSimon Marchi <simon.marchi@ericsson.com>2017-06-25 12:49:19 +0200
committerSimon Marchi <simon.marchi@ericsson.com>2017-06-25 12:49:19 +0200
commit07809eafc959a0c588663c0c949eaf8044a1b40a (patch)
tree781644fbcdfd67834cfeea9959d42b0d8ef24b9c /config.sub
parentf076f0349cb958b451872ce4a7987821533c2f49 (diff)
downloadgdb-07809eafc959a0c588663c0c949eaf8044a1b40a.zip
gdb-07809eafc959a0c588663c0c949eaf8044a1b40a.tar.gz
gdb-07809eafc959a0c588663c0c949eaf8044a1b40a.tar.bz2
dtrace-probe: Put semicolon after while on its own line
clang shows this warning. /home/emaisin/src/binutils-gdb/gdb/dtrace-probe.c:424:52: error: while loop has empty body [-Werror,-Wempty-body] while (*p++ != '\0' && p - strtab < strtab_size); ^ /home/emaisin/src/binutils-gdb/gdb/dtrace-probe.c:424:52: note: put the semicolon on a separate line to silence this warning Putting the semicolon on its own line is not a big sacrifice to get rid of this warning. I think it's also useful to keep this, because it can catch errors like this: while (something); { ... } although gcc would warn about it in a different way (misleading indentation). This warning is already discussed here in the GCC bugzilla: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62184 gdb/ChangeLog: * dtrace-probe.c (dtrace_process_dof_probe): Put semi-colon on its own line.
Diffstat (limited to 'config.sub')
0 files changed, 0 insertions, 0 deletions