All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel <qemu-devel@nongnu.org>
Cc: Kevin Wolf <kwolf@redhat.com>, Stefan Weil <sw@weilnetz.de>,
	Anthony Liguori <anthony@codemonkey.ws>,
	Stefan Hajnoczi <stefanha@redhat.com>
Subject: [Qemu-devel] block/stream.c -Werror build failure
Date: Thu, 19 Sep 2013 18:52:15 +0200	[thread overview]
Message-ID: <523B2BBF.7020801@suse.de> (raw)

Hello,

As reported yesterday on IRC, since the last round of pulls I am getting
the following warning-treated-as-error:

  CC    block/stream.o
/home/andreas/QEMU/qemu/block/stream.c: In function ‘stream_run’:
/home/andreas/QEMU/qemu/block/stream.c:111:14: error: ‘copy’ may be used
uninitialized in this function [-Werror=maybe-uninitialized]
cc1: all warnings being treated as errors
make: *** [block/stream.o] Fehler 1

$ gcc --version
gcc (SUSE Linux) 4.7.2 20130108 [gcc-4_7-branch revision 195012]

However I only got this in 1 of 2 repositories I tried. It turns out
that --enable-debug avoids this build issue.

The stream.c code itself looks okay to me. In the case of ret >= 0, copy
is always assigned, including the goto code path.
Still, could we initialize the copy variable to false or revert whatever
change introduced this build regression? (-Wextra?)

Regards,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

             reply	other threads:[~2013-09-19 16:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-19 16:52 Andreas Färber [this message]
2013-09-19 16:59 ` [Qemu-devel] block/stream.c -Werror build failure Stefan Weil
2013-09-19 17:00   ` Andreas Färber

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=523B2BBF.7020801@suse.de \
    --to=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=kwolf@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=sw@weilnetz.de \
    /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.