From: Jeff Cody <jcody@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] git master build failure (migration/colo.c)
Date: Mon, 31 Oct 2016 17:51:59 -0400 [thread overview]
Message-ID: <20161031215159.GF17785@localhost.localdomain> (raw)
In-Reply-To: <05a758e9-027f-d1d1-82f9-cf78627ad63b@ilande.co.uk>
On Mon, Oct 31, 2016 at 08:08:46PM +0000, Mark Cave-Ayland wrote:
> I've just done a git pull and get the following build error here:
>
> cc -I/home/build/src/qemu/git/qemu/tcg
> -I/home/build/src/qemu/git/qemu/tcg/i386
> -I/home/build/src/qemu/git/qemu/linux-headers
> -I/home/build/src/qemu/git/qemu/linux-headers -I.
> -I/home/build/src/qemu/git/qemu -I/home/build/src/qemu/git/qemu/include
> -Imigration -Imigration -I/usr/include/pixman-1
> -I/home/build/src/qemu/git/qemu/dtc/libfdt -Werror -pthread
> -I/usr/include/glib-2.0 -I/usr/lib/x86_64-linux-gnu/glib-2.0/include
> -m64 -mcx16 -D_GNU_SOURCE -D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE
> -Wstrict-prototypes -Wredundant-decls -Wall -Wundef -Wwrite-strings
> -Wmissing-prototypes -fno-strict-aliasing -fno-common -fwrapv
> -Wendif-labels -Wmissing-include-dirs -Wempty-body -Wnested-externs
> -Wformat-security -Wformat-y2k -Winit-self -Wignored-qualifiers
> -Wold-style-declaration -Wold-style-definition -Wtype-limits
> -fstack-protector-all -I/usr/include/p11-kit-1
> -I/usr/include/libpng12 -I/home/build/src/qemu/git/qemu/tests -MMD -MP
> -MT migration/colo-failover.o -MF migration/colo-failover.d -O2
> -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -g -c -o
> migration/colo-failover.o migration/colo-failover.c
> migration/colo.c: In function ‘colo_process_incoming_thread’:
> migration/colo.c:448:9: error: ‘request’ may be used uninitialized in
> this function [-Werror=maybe-uninitialized]
> cc1: all warnings being treated as errors
> make: *** [migration/colo.o] Error 1
> make: *** Waiting for unfinished jobs....
>
> Does anyone else see this at all?
>
I'm not seeing it for later gcc versions (6.2.1), but I was able to
reproduce on earlier ones (4.4.7, for instance). I sent a patch out for
this.
Thanks,
Jeff
prev parent reply other threads:[~2016-10-31 21:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 20:08 [Qemu-devel] git master build failure (migration/colo.c) Mark Cave-Ayland
2016-10-31 21:51 ` Jeff Cody [this message]
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=20161031215159.GF17785@localhost.localdomain \
--to=jcody@redhat.com \
--cc=mark.cave-ayland@ilande.co.uk \
--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).