From: Simon Marchi <simon.marchi@polymtl.ca>
To: Sergio Durigan Junior <sergiodj@sergiodj.net>
Cc: Simon Marchi <simon.marchi@ericsson.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/4] dtrace-probe: Put semicolon after while on its own line
Date: Wed, 21 Jun 2017 21:08:00 -0000 [thread overview]
Message-ID: <6b97c3b96161cab3a6e672e6ee8968ed@polymtl.ca> (raw)
In-Reply-To: <87d19xcc5t.fsf@sergiodj.net>
On 2017-06-21 22:34, Sergio Durigan Junior wrote:
> On Wednesday, June 21 2017, Simon Marchi wrote:
>
>> 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.
>> ---
>> gdb/dtrace-probe.c | 3 ++-
>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>
>> diff --git a/gdb/dtrace-probe.c b/gdb/dtrace-probe.c
>> index 122f8de..9a02694 100644
>> --- a/gdb/dtrace-probe.c
>> +++ b/gdb/dtrace-probe.c
>> @@ -421,7 +421,8 @@ dtrace_process_dof_probe (struct objfile *objfile,
>> arg.type_str = xstrdup (p);
>>
>> /* Use strtab_size as a sentinel. */
>> - while (*p++ != '\0' && p - strtab < strtab_size);
>> + while (*p++ != '\0' && p - strtab < strtab_size)
>> + ; /* Silence clang's -Wempty-body warning. */
>
> Lately I've been choosing to explicitly put "continue;" when the body
> doesn't contain anything, like:
>
> while (*p++ != '\0' && p - strtab < strtab_size)
> continue;
>
> I don't know what others think about it, but it would solve this
> problem
> and also be more verbose that we're just iterating without a body.
I also looks good, but I don't have a preference. I'll do that if
others like it too.
Thanks,
Simon
next prev parent reply other threads:[~2017-06-21 21:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 20:15 [PATCH 0/4] Get rid of some more warnings given by clang Simon Marchi
2017-06-21 20:15 ` [PATCH 3/4] dtrace-probe: Put semicolon after while on its own line Simon Marchi
2017-06-21 20:34 ` Sergio Durigan Junior
2017-06-21 21:08 ` Simon Marchi [this message]
2017-06-21 21:36 ` Pedro Alves
2017-06-25 10:48 ` Simon Marchi
2017-06-25 10:57 ` Simon Marchi
2017-06-21 20:15 ` [PATCH 1/4] environ-selftests: Ignore -Wself-move warning Simon Marchi
2017-06-21 20:29 ` Sergio Durigan Junior
2017-06-21 21:05 ` Simon Marchi
2017-06-21 21:12 ` Sergio Durigan Junior
2017-06-21 21:28 ` Pedro Alves
2017-06-21 21:32 ` Sergio Durigan Junior
2017-06-22 7:44 ` Simon Marchi
2017-06-22 9:34 ` Pedro Alves
2017-06-21 21:16 ` Simon Marchi
2017-06-21 21:30 ` Sergio Durigan Junior
2017-06-22 8:31 ` [PATCH v2] " Simon Marchi
2017-06-22 9:51 ` Pedro Alves
2017-06-22 10:52 ` Pedro Alves
2017-06-22 10:57 ` Simon Marchi
2017-06-22 11:43 ` Pedro Alves
2017-06-21 20:15 ` [PATCH 2/4] x86-dregs: Print debug registers one per line Simon Marchi
2017-06-21 20:31 ` Sergio Durigan Junior
2017-06-21 21:06 ` Simon Marchi
2017-06-25 10:58 ` Simon Marchi
2017-06-21 20:15 ` [PATCH 4/4] main: Don't add int to string Simon Marchi
2017-06-21 20:35 ` Sergio Durigan Junior
2017-06-25 10:58 ` Simon Marchi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6b97c3b96161cab3a6e672e6ee8968ed@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@sergiodj.net \
--cc=simon.marchi@ericsson.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox