All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Andrew Jones <drjones@redhat.com>, Thomas Huth <thuth@redhat.com>
Cc: kvm@vger.kernel.org, "David Hildenbrand" <david@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"Laurent Vivier" <lvivier@redhat.com>
Subject: Re: [kvm-unit-tests PATCH] Replace -Wextra with a saner list of warning flags
Date: Thu, 29 Jun 2017 19:00:35 +0200	[thread overview]
Message-ID: <d833ed31-70b6-0001-5c81-b41fb7e1dfed@redhat.com> (raw)
In-Reply-To: <20170629163547.7wp4fzmgb4e4y7tq@kamzik.brq.redhat.com>



On 29/06/2017 18:35, Andrew Jones wrote:
> On Thu, Jun 29, 2017 at 06:30:47PM +0200, Thomas Huth wrote:
>> On 29.06.2017 17:40, Thomas Huth wrote:
>>> Using -Wextra together with -Werror is troublesome - various versions
>>> of GCC produce suspicious or even wrong warnings with -Wextra which
>>> then become fatal errors with -Werror. For example, the current state
>>> of the kvm-unit-tests does not compile anymore with GCC 4.8.1 for
>>> s390x due to an inadequate -Wmissing-field-initializers warning.
>>> That's annoying for users who just would like to compile the
>>> kvm-unit-tests and cumbersome for the developers who have to work
>>> around these problems in the source code. So let's replace -Wextra
>>> by a saner lists of warning flags that are normally enabled by -Wextra.
>>> Most of them are added to the architecture independent CFLAGS list,
>>> so that x86 now benefits from these checks, too. The ones that
>>> could not be added there are placed in the architecture specific
>>> CFLAGS instead.
>>
>> BTW, I also dropped -Wunused-parameter on purpose. It's often a nuisance
>> that you are forced to add "unused" attributes to parameters, just
>> because you can not get rid of certain parameter since your function has
>> to obey a certain API. That means we could now finally also get rid of
>> the ugly "__unused" tags in the code in the lib folder again, if we like ;-)
> 
> Fine by me. Adding __unused gets tiresome and ugly. I even recently
> wrote a patch where I needed to introduce __maybe_unused...

Agreed, C should take inspiration from C++ and add

   int f(int x, int /* unused */)

Paolo

  reply	other threads:[~2017-06-29 17:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-29 15:40 [kvm-unit-tests PATCH] Replace -Wextra with a saner list of warning flags Thomas Huth
2017-06-29 16:30 ` Thomas Huth
2017-06-29 16:35   ` Andrew Jones
2017-06-29 17:00     ` Paolo Bonzini [this message]
2017-06-29 16:56 ` Laurent Vivier
2017-06-29 17:07 ` Paolo Bonzini
2017-06-29 17:19   ` Thomas Huth
2017-06-30 10:40     ` Paolo Bonzini

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=d833ed31-70b6-0001-5c81-b41fb7e1dfed@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=david@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=lvivier@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=thuth@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.