public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: "Manuel López-Ibáñez" <lopezibanez@gmail.com>
Cc: Gcc Patch List <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH v2] cpp/c: Add -Wexpansion-to-defined
Date: Wed, 10 Aug 2016 12:06:00 -0000	[thread overview]
Message-ID: <59051c81-0056-3e01-54a6-07b71307965c@gnu.org> (raw)
In-Reply-To: <CAESRpQBuO7Rj00ikPFt_zr8ROoatzGpT0p1SLHin1NKzwvJs1Q@mail.gmail.com>



On 10/08/2016 13:31, Manuel López-Ibáñez wrote:
> My only fear is that people not using -Wpedantic nor -pedantic-errors
> expect that GNU extensions work. This is a GNU extension that defines
> something that is undefined according to ISO. Enabling the warning
> with -Wextra is just annoying those people who may not care about
> other compilers.

I think this warning falls in the same category as
-Wshift-negative-value.  (In fact I dislike -Wshift-negative-value a
lot, and would put that one under -Wpedantic only).

It is interesting that GCC has been relying for a long time on such
behavior in the HAVE_DESIGNATED_INITIALIZERS macro, despite GCC not
having any interest in compiling with -Wpedantic.  I think this
reinforces the choice of adding the warning to -Wextra.

People using -Wextra are used to having to remove some warnings
manually, and this one probably doesn't have many hits (1 in QEMU, which
is what motivated me to add it to GCC; and 2 in GCC not counting the
duplicate code between gcc/system.h and libcpp/system.h).

Paolo

  parent reply	other threads:[~2016-08-10 12:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10 10:06 Paolo Bonzini
2016-08-10 11:32 ` Manuel López-Ibáñez
2016-08-10 11:53   ` Joseph Myers
2016-08-10 12:06   ` Paolo Bonzini [this message]
2016-08-10 14:43     ` Manuel López-Ibáñez
2016-08-10 14:45       ` Paolo Bonzini
2016-08-10 15:25         ` Manuel López-Ibáñez
2016-08-10 15:29           ` Paolo Bonzini
2016-08-10 15:33             ` Joseph Myers
2016-08-10 15:51               ` Paolo Bonzini
2016-08-10 15:58                 ` Joseph Myers
2016-08-10 16:01                   ` Paolo Bonzini
2016-08-11  3:02 ` Sandra Loosemore

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=59051c81-0056-3e01-54a6-07b71307965c@gnu.org \
    --to=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=lopezibanez@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).