From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] [6736] Sparse fixes: NULL use, header order, ANSI prototypes, static
Date: Sun, 08 Mar 2009 10:21:09 -0500 [thread overview]
Message-ID: <49B3E265.1040205@codemonkey.ws> (raw)
In-Reply-To: <E1LfyWH-0006ll-Ie@cvs.savannah.gnu.org>
Blue Swirl wrote:
> Revision: 6736
> http://svn.sv.gnu.org/viewvc/?view=rev&root=qemu&revision=6736
> Author: blueswir1
> Date: 2009-03-07 15:32:56 +0000 (Sat, 07 Mar 2009)
> Log Message:
> -----------
> Sparse fixes: NULL use, header order, ANSI prototypes, static
>
> Fix Sparse warnings:
> * use NULL instead of plain 0
> * rearrange header include order to avoid redefining types accidentally
> * ANSIfy SLIRP
> * avoid "restrict" keyword
> * add static
>
This broke the Windows build. The reason is that you moved all system
headers to be included before any QEMU headers. While I agree with this
in principle, Windows headers are sloppy and don't include their
dependencies. Right now, we rely on qemu-common.h being included in the
top in order to get #include <windows.h> every where.
To complicate matters further, we define some special versioning magic
to get windows IPv6 support working. I don't want to add that full blob
to every .c file so it makes sense to use a qemu include file (like
qemu-common.h). That defeats that purpose of your refactoring though so
I wanted to see what you thought about it.
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-03-08 15:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 15:32 [Qemu-devel] [6736] Sparse fixes: NULL use, header order, ANSI prototypes, static Blue Swirl
2009-03-08 15:21 ` Anthony Liguori [this message]
2009-03-08 15:36 ` Blue Swirl
2009-03-08 16:01 ` Filip Navara
2009-03-08 16:16 ` Anthony Liguori
2009-03-08 16:23 ` Blue Swirl
2009-03-08 16:25 ` Anthony Liguori
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=49B3E265.1040205@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=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 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.