From: Paolo Bonzini <pbonzini@redhat.com>
To: Greg Kurz <groug@kaod.org>, qemu-devel@nongnu.org
Cc: "Cornelia Huck" <cornelia.huck@de.ibm.com>,
"Eric Blake" <eblake@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [Qemu-devel] [PATCH v2] kvm: workaround build break on gcc-7.1.1 / fedora26
Date: Mon, 7 Aug 2017 13:55:09 +0200 [thread overview]
Message-ID: <77c63a1b-92f9-8fc5-dbf5-855c28adc03d@redhat.com> (raw)
In-Reply-To: <150210580404.1343.7325713896658799315.stgit@bahia.lan>
On 07/08/2017 13:36, Greg Kurz wrote:
> Building QEMU on fedora26 with the latest gcc package fails:
>
> CC ppc64-softmmu/target/ppc/kvm.o
> In file included from include/sysemu/hw_accel.h:16:0,
> from target/ppc/kvm.c:31:
> target/ppc/kvm.c: In function ‘kvmppc_booke_watchdog_enable’:
> include/sysemu/kvm.h:449:35: error: ‘args_tmp[i]’ may be used uninitialized
> in this function [-Werror=maybe-uninitialized]
> cap.args[i] = args_tmp[i]; \
> ^
> target/ppc/kvm.c: In function ‘kvmppc_set_papr’:
> include/sysemu/kvm.h:449:35: error: ‘args_tmp[i]’ may be used uninitialized
> in this function [-Werror=maybe-uninitialized]
> cc1: all warnings being treated as errors
>
> $ rpm -q gcc
> gcc-7.1.1-3.fc26.ppc64le
>
> The compiler should obviously optimize this code away when no extra
> agument is passed to kvm_vm_enable_cap() and kvm_vcpu_enable_cap(),
> but it doesn't. This bug should be fixed one day in gcc, but we can
> also change our code pattern so that we don't hit the issue anymore.
> We workaround this, by using memcpy() instead of open-coding the copy.
Nice way to do it, thanks. I'll queue it for 2.10.
Paolo
> Signed-off-by: Greg Kurz <groug@kaod.org>
> ---
> v2: - use memcpy()
> ---
> include/sysemu/kvm.h | 14 ++++----------
> 1 file changed, 4 insertions(+), 10 deletions(-)
>
> diff --git a/include/sysemu/kvm.h b/include/sysemu/kvm.h
> index 91fc07ee9afe..3a458f50e9f4 100644
> --- a/include/sysemu/kvm.h
> +++ b/include/sysemu/kvm.h
> @@ -428,11 +428,8 @@ int kvm_vm_check_extension(KVMState *s, unsigned int extension);
> .flags = cap_flags, \
> }; \
> uint64_t args_tmp[] = { __VA_ARGS__ }; \
> - int i; \
> - for (i = 0; i < (int)ARRAY_SIZE(args_tmp) && \
> - i < ARRAY_SIZE(cap.args); i++) { \
> - cap.args[i] = args_tmp[i]; \
> - } \
> + size_t n = MIN(ARRAY_SIZE(args_tmp), ARRAY_SIZE(cap.args)); \
> + memcpy(cap.args, args_tmp, n * sizeof(cap.args[0])); \
> kvm_vm_ioctl(s, KVM_ENABLE_CAP, &cap); \
> })
>
> @@ -443,11 +440,8 @@ int kvm_vm_check_extension(KVMState *s, unsigned int extension);
> .flags = cap_flags, \
> }; \
> uint64_t args_tmp[] = { __VA_ARGS__ }; \
> - int i; \
> - for (i = 0; i < (int)ARRAY_SIZE(args_tmp) && \
> - i < ARRAY_SIZE(cap.args); i++) { \
> - cap.args[i] = args_tmp[i]; \
> - } \
> + size_t n = MIN(ARRAY_SIZE(args_tmp), ARRAY_SIZE(cap.args)); \
> + memcpy(cap.args, args_tmp, n * sizeof(cap.args[0])); \
> kvm_vcpu_ioctl(cpu, KVM_ENABLE_CAP, &cap); \
> })
>
>
next prev parent reply other threads:[~2017-08-07 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 11:36 [Qemu-devel] [PATCH v2] kvm: workaround build break on gcc-7.1.1 / fedora26 Greg Kurz
2017-08-07 11:55 ` Paolo Bonzini [this message]
2017-08-07 14:06 ` Philippe Mathieu-Daudé
2017-08-07 12:16 ` Cornelia Huck
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=77c63a1b-92f9-8fc5-dbf5-855c28adc03d@redhat.com \
--to=pbonzini@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=eblake@redhat.com \
--cc=f4bug@amsat.org \
--cc=groug@kaod.org \
--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).