From: "andrzej zaborowski" <balrogg@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] fix gcc4 compile warnings
Date: Fri, 30 Nov 2007 15:30:40 +0100 [thread overview]
Message-ID: <fb249edb0711300630j74911cf6lba75c397b9f7c8fe@mail.gmail.com> (raw)
In-Reply-To: <475019BF.4040906@amd.com>
On 30/11/2007, Andre Przywara <andre.przywara@amd.com> wrote:
> > These casts are not the right way to get rid of the warnings, as are
> > some of the casts in other files in qemu_put_* and qemu_get_*
> > arguments. In this case the warnings are true positives and the bugs
> > causing the warnings have to be addressed instead of just the
> > warnings.
>
> Are you sure of that? Most of the fixes are like this:
> >> - qemu_put_be32s(f, &s->count_shift);
> >> + qemu_put_be32s(f, (uint32_t *)&s->count_shift);
> qemu_put_be32s is (QEMUFile *f, const uint32_t *pv), but after all the
> 2nd argument is only a _pointer_ to an unsigned variable, the size is
> the same (thanks to the C99 explicit types).
count_shift is an int so it is the machine word size, not necesarily
32-bit AFAIK. Otherwise I guess gcc wouldn't warn. You can possibly
use:
qemu_put_be32(f, s->count_shift);
Or point qemu_put_be32_s() to a int32_t/uint32_t variable.
>
> What solution do you prefer for the opaque types? I have used the simple:
> >> - void *args[MAX_ARGS];
> >> + intptr_t args[MAX_ARGS];
> A more portable and clean solution would be this:
> - void *args[MAX_ARGS];
> + union
> + {
> + void* ptr;
> + int i;
> + } args[MAX_ARGS];
> If you prefer this, I can change the patch accordingly.
I'm not sure why you get a warning here and I'm unable to run a build
at the moment. A void * should be able to store some (unknown size)
integer regardless of the platform.
Regards
next prev parent reply other threads:[~2007-11-30 14:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 23:58 [Qemu-devel] [PATCH] fix gcc4 compile warnings André Przywara
2007-11-30 13:23 ` andrzej zaborowski
2007-11-30 14:10 ` Andre Przywara
2007-11-30 14:24 ` Samuel Thibault
2007-11-30 14:30 ` andrzej zaborowski [this message]
2007-11-30 14:38 ` Samuel Thibault
2007-11-30 14:48 ` Paul Brook
2007-11-30 14:56 ` Andre Przywara
2007-11-30 14:06 ` Paul Brook
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=fb249edb0711300630j74911cf6lba75c397b9f7c8fe@mail.gmail.com \
--to=balrogg@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).