Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: Sergio Durigan Junior <sergiodj@sergiodj.net>,
	Simon Marchi <simon.marchi@ericsson.com>,
	gdb-patches@sourceware.org
Subject: Re: [PATCH 1/4] environ-selftests: Ignore -Wself-move warning
Date: Thu, 22 Jun 2017 09:34:00 -0000	[thread overview]
Message-ID: <4f10c70b-c02a-98cb-3ad8-8fc9432340b3@redhat.com> (raw)
In-Reply-To: <1eb85c254f6948eb4a1c79462f0d98ab@polymtl.ca>


On 06/22/2017 08:44 AM, Simon Marchi wrote:
> On 2017-06-21 23:28, Pedro Alves wrote:
>> On 06/21/2017 10:05 PM, Simon Marchi wrote:
>>
>>> 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?
>>>
>>
>> Don't both GCC and Clang understand "#pragma GCC diagnostic" instead?
> 
> Yes, but then it's GCC that complains that it doesn't know the warning:
> 
> /home/emaisin/src/binutils-gdb/gdb/unittests/environ-selftests.c:141:32:
> error: unknown option after ‘#pragma GCC diagnostic’ kind [-Werror=pragmas]
>  #pragma GCC diagnostic ignored "-Wself-move"
>                                 ^
> 

Ah, but that's a different kind of complaint.  Since both compilers
understand "#pragma GCC" but only one understands "#pragma clang",
then it seems clearly better to me to write the infrastructure
macros in terms of the former.  It'll make it a bit easier to
reuse the macros for other warnings.

>> Or better even, wrap it in some macros (and use _Pragma):
>>
>>  #define DIAGNOSTIC_PUSH _Pragma ("GCC diagnostic push")
>>  #define DIAGNOSTIC_POP _Pragma ("GCC diagnostic pop")
>>  #define DIAGNOSTIC_IGNORE(option) \
>>    _Pragma (STRINGIFY (GCC diagnostic ignored option))
> 
> Oh that's interesting.  The gcc doc said that _Pragma was added exactly
> for this purpose (to be usable in macros).  I'll try that.

Right.

Thanks,
Pedro Alves


  reply	other threads:[~2017-06-22  9:34 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 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
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 [this message]
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 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

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=4f10c70b-c02a-98cb-3ad8-8fc9432340b3@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=sergiodj@sergiodj.net \
    --cc=simon.marchi@ericsson.com \
    --cc=simon.marchi@polymtl.ca \
    /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