qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Filip Navara <filip.navara@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [6736] Sparse fixes: NULL use, header order, ANSI prototypes, static
Date: Sun, 8 Mar 2009 17:01:17 +0100	[thread overview]
Message-ID: <5b31733c0903080901s40b6237bo5236e6ea36559462@mail.gmail.com> (raw)
In-Reply-To: <f43fc5580903080836l42351a07tb9ad1c5782318e2a@mail.gmail.com>

On Sun, Mar 8, 2009 at 4:36 PM, Blue Swirl <blauwirbel@gmail.com> wrote:
> On 3/8/09, Anthony Liguori <anthony@codemonkey.ws> wrote:
>> 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.
>
> Taking vl.c as an example, do you mean that even these headers:
> #include <unistd.h>
> #include <fcntl.h>
> #include <signal.h>
> #include <time.h>
> #include <errno.h>
> #include <sys/time.h>
> #include <zlib.h>
> before config-host.h line are now broken because of missing windows.h
> include? Or is it just some header below that?

Only mmsystem.h as far as I can see... which is also needlessly
included in many files (savecm.c, net.c).

F.

  reply	other threads:[~2009-03-08 16:01 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
2009-03-08 15:36   ` Blue Swirl
2009-03-08 16:01     ` Filip Navara [this message]
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=5b31733c0903080901s40b6237bo5236e6ea36559462@mail.gmail.com \
    --to=filip.navara@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).