qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Weil <sw@weilnetz.de>
To: Alexey Kardashevskiy <aik@ozlabs.ru>
Cc: "Anthony Liguori" <aliguori@us.ibm.com>,
	"Stefan Hajnoczi" <stefanha@gmail.com>,
	qemu-devel@nongnu.org, "David Gibson" <dwg@au1.ibm.com>,
	"Blue Swirl" <blauwirbel@gmail.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] bswap: fix compiler warning
Date: Fri, 12 Apr 2013 19:36:33 +0200	[thread overview]
Message-ID: <51684621.7090204@weilnetz.de> (raw)
In-Reply-To: <20130412164715.GL5065@truffula.fritz.box>

Am 12.04.2013 18:47, schrieb David Gibson:
> On Fri, Apr 12, 2013 at 12:51:51PM +0200, Andreas Färber wrote:
>> Am 12.04.2013 03:41, schrieb Alexey Kardashevskiy:
>>> The bswap functions use memcpy but the bswap.h header itself does not seem to
>>> include it in some configuration such as cross compiling for powerpc64
>>> on x86_64 machine (gcc 4.6.3 from ftp.kernel.org, headers/libs from FC18/ppc64),
>>> the example warning is below.
>>>
>>> The patch explicitly includes string.h.
>>>
>>>   CC    ppc64-softmmu/hw/virtio/virtio.o
>>> In file included from /home/alexey/qemu/include/libfdt_env.h:22:0,
>>>                  from /home/alexey/qemu/../lib4qemu/usr/include/libfdt.h:54,
>>>                  from /home/alexey/qemu/hw/nvram/spapr_nvram.c:25:
>>> /home/alexey/qemu/include/qemu/bswap.h: In function 'lduw_p':
>>> /home/alexey/qemu/include/qemu/bswap.h:244:5: warning: implicit declaration of function 'memcpy' [-Wimplicit-function-declaration]
>>> /home/alexey/qemu/include/qemu/bswap.h:244:5: warning: incompatible implicit declaration of built-in function 'memcpy' [enabled by default]
>>>
>>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>>> ---
>>>  include/qemu/bswap.h |    2 ++
>>>  1 file changed, 2 insertions(+)
>>>
>>> diff --git a/include/qemu/bswap.h b/include/qemu/bswap.h
>>> index d3af35d..d50de0d 100644
>>> --- a/include/qemu/bswap.h
>>> +++ b/include/qemu/bswap.h
>>> @@ -1,6 +1,8 @@
>>>  #ifndef BSWAP_H
>>>  #define BSWAP_H
>>>  
>>> +#include <string.h>
>>> +
>>>  #include "config-host.h"
>>>  #include <inttypes.h>
>>>  #include <limits.h>
>> Including string.h is certainly the right thing to do, but why do you
>> single it out first?
> Yeah, it probably shouldn't go above the config header.  Otherwise
> it's the right thing.

If string.h went directly after limits.h, we'd even preserve the
alphabetic order of the system headers :-)

  reply	other threads:[~2013-04-12 17:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-12  1:41 [Qemu-devel] [PATCH] bswap: fix compiler warning Alexey Kardashevskiy
2013-04-12  9:10 ` Stefan Hajnoczi
2013-04-12 10:51 ` Andreas Färber
2013-04-12 13:03   ` Alexey Kardashevskiy
2013-04-12 16:47   ` David Gibson
2013-04-12 17:36     ` Stefan Weil [this message]
2013-04-12 20:23       ` Alexey Kardashevskiy
2013-04-12 20:31         ` Stefan Weil

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=51684621.7090204@weilnetz.de \
    --to=sw@weilnetz.de \
    --cc=afaerber@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=dwg@au1.ibm.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=stefanha@gmail.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 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).