Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 1/4] environ-selftests: Ignore -Wself-move warning
Date: Wed, 21 Jun 2017 21:05:00 -0000	[thread overview]
Message-ID: <884719ed975085085337b2972a9c2ac4@polymtl.ca> (raw)
In-Reply-To: <87mv91ccey.fsf@sergiodj.net>

On 2017-06-21 22:29, Sergio Durigan Junior wrote:
> On Wednesday, June 21 2017, Simon Marchi wrote:
> 
>> clang gives this warning:
>> 
>> /home/emaisin/src/binutils-gdb/gdb/unittests/environ-selftests.c:139:7: 
>> error: explicitly moving variable of type 'gdb_environ' to itself 
>> [-Werror,-Wself-move]
>>   env = std::move (env);
>>   ~~~ ^            ~~~
>> 
>> In this case, ignoring the warning locally is clearly the thing to do,
>> since it warns exactly about the behavior we want to test.  We also
>> don't want to disable this globally, because we would want the 
>> compiler
> 
> "we would want the code compiler to warn"

Oops thanks.

>> if we wrote that in real code.
>> 
>> I filed a bug in GCC's bugzilla to suggest to add this warning:
>> 
>>   https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81159
> 
> Thanks!
> 
>> gdb/ChangeLog:
>> 
>> 	* unittests/environ-selftests.c (run_tests): Ignore -Wself-move
>> 	warning.
>> ---
>>  gdb/unittests/environ-selftests.c | 9 +++++++++
>>  1 file changed, 9 insertions(+)
>> 
>> diff --git a/gdb/unittests/environ-selftests.c 
>> b/gdb/unittests/environ-selftests.c
>> index ecc3955..6989c5e 100644
>> --- a/gdb/unittests/environ-selftests.c
>> +++ b/gdb/unittests/environ-selftests.c
>> @@ -136,7 +136,16 @@ run_tests ()
>>    env.clear ();
>>    env.set ("A", "1");
>>    SELF_CHECK (strcmp (env.get ("A"), "1") == 0);
>> +
>> +#ifdef __clang__
>> +#pragma clang diagnostic push
>> +#pragma clang diagnostic ignored "-Wself-move"
>> +#endif /* __clang__ */
>>    env = std::move (env);
>> +#ifdef __clang__
>> +#pragma clang diagnostic pop
>> +#endif /* __clang__ */
> 
> Wow.  I know we've discussed this before, but this is ugly :-/.  
> Anyway,
> this file is just a unittest, so I'm totally fine with this.

Yeah, I didn't expect to have to put the #ifdefs for __clang__ though.  
Without them, gcc emits a warning [-Wunknown-pragma].  We always have 
the option to turn -Wunknown-pragma off globally, what do you prefer?


  reply	other threads:[~2017-06-21 21:05 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
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 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
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 [this message]
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

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=884719ed975085085337b2972a9c2ac4@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