All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: "Andreas Färber" <afaerber@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Stefan Hajnoczi <stefanha@gmail.com>,
	qemu-devel@nongnu.org, Blue Swirl <blauwirbel@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH] bswap: fix compiler warning
Date: Fri, 12 Apr 2013 23:03:41 +1000	[thread overview]
Message-ID: <5168062D.8080104@ozlabs.ru> (raw)
In-Reply-To: <5167E747.2020106@suse.de>

On 04/12/2013 08:51 PM, 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?


I have no idea :)
I just tried to do cross compilation and hit this one. And it is not the 
only problem, I hit another one but this is against gcc or libc, have not 
discovered it yet.



-- 
Alexey

  reply	other threads:[~2013-04-12 13:03 UTC|newest]

Thread overview: 13+ 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 [this message]
2013-04-12 16:47   ` David Gibson
2013-04-12 17:36     ` Stefan Weil
2013-04-12 20:23       ` Alexey Kardashevskiy
2013-04-12 20:31         ` [Qemu-trivial] " Stefan Weil
2013-04-12 20:31           ` Stefan Weil
2013-04-15  1:47           ` [Qemu-trivial] [PATCH v2] " Alexey Kardashevskiy
2013-04-15  1:52             ` [Qemu-trivial] [Qemu-ppc] " David Gibson
2013-04-15 10:52             ` [Qemu-trivial] " Andreas Färber
2013-04-19  9:28             ` Stefan Hajnoczi

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=5168062D.8080104@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=blauwirbel@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --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 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.