From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC, PATCH] Add -Wstrict-prototypes, maybe later -Wmissing-prototypes
Date: Sat, 09 Aug 2008 13:24:07 -0500 [thread overview]
Message-ID: <489DE0C7.9000505@codemonkey.ws> (raw)
In-Reply-To: <f43fc5580808081022l28c9bd7bs45cfe8a94e32e308@mail.gmail.com>
Blue Swirl wrote:
> Hi,
>
> I made a series of patches that add -Wstrict-prototypes to the CFLAGS
> and then -Wmissing-prototypes, both of which are enabled by Xen. I
> also fixed most warnings generated -Wstrict-prototypes and some of
> them for the -Wmissing-prototypes case.
>
> Compiling with -Wstrict-prototypes produces only one extra warning. I
> think this flag should be enabled.
>
As long as the plan is to fix all of those warnings, I think it's a good
idea.
Regards,
Anthony Liguori
> But dyngen targets spew a lot of noise with -Wmissing-prototypes so
> I'm not proposing to add that (or maybe that should be coupled with
> CONFIG_DYNGEN_OP). This also meant that I did not care enough to fix
> all warnings. The current warning fix should be safe to apply anyway.
>
> Comments?
>
next prev parent reply other threads:[~2008-08-09 18:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 17:22 [Qemu-devel] [RFC, PATCH] Add -Wstrict-prototypes, maybe later -Wmissing-prototypes Blue Swirl
2008-08-09 18:24 ` Anthony Liguori [this message]
2008-08-10 18:33 ` Blue Swirl
2008-08-11 7:52 ` Gerd Hoffmann
2008-08-11 9:54 ` Samuel Thibault
2008-08-11 13:32 ` M. Warner Losh
2008-08-11 13:30 ` M. Warner Losh
2008-08-11 14:21 ` Anthony Liguori
2008-08-11 14:48 ` Avi Kivity
2008-08-11 14:53 ` Paul Brook
2008-08-11 14:56 ` Laurent Vivier
2008-08-11 14:56 ` Anthony Liguori
2008-08-11 16:38 ` Avi Kivity
2008-08-11 16:47 ` Anthony Liguori
2008-08-11 18:52 ` Blue Swirl
2008-08-11 18:57 ` Laurent Vivier
2008-08-11 19:11 ` Blue Swirl
2008-08-11 19:22 ` Anthony Liguori
2008-08-11 20:03 ` Laurent Vivier
2008-08-12 1:57 ` Anthony Liguori
2008-08-12 8:14 ` Laurent Vivier
2008-08-12 9:22 ` Avi Kivity
2008-08-12 12:24 ` Daniel Jacobowitz
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=489DE0C7.9000505@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=qemu-devel@nongnu.org \
/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 NNTP newsgroup(s).