From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [RFC, PATCH, v2] Add -Wstrict-prototypes, maybe later -Wmissing-prototypes
Date: Tue, 12 Aug 2008 19:10:02 +0300 [thread overview]
Message-ID: <f43fc5580808120910v648e49d0t95d91ff4d69942be@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 352 bytes --]
I just noticed that even -Wstrict-prototypes generates warnings on
dyngen targets, sorry. I'm not sure that the flags should be added
until all dyngen targets have been converted. The fixes should be safe
to apply even without adding the flags.
Anyway, here are the current versions of the patches, now also
monitor.c is silent as well as slirp/if.c.
[-- Attachment #2: wstrict_prototypes.diff --]
[-- Type: plain/text, Size: 1007 bytes --]
[-- Attachment #3: fix_wstrict_prototypes_warnings.diff --]
[-- Type: plain/text, Size: 6538 bytes --]
[-- Attachment #4: wmissing_prototypes.diff --]
[-- Type: plain/text, Size: 1089 bytes --]
[-- Attachment #5: fix_wmissing_prototypes_warnings.diff --]
[-- Type: plain/text, Size: 15100 bytes --]
reply other threads:[~2008-08-12 16:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=f43fc5580808120910v648e49d0t95d91ff4d69942be@mail.gmail.com \
--to=blauwirbel@gmail.com \
--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).