From: Jason Wang <jasowang@redhat.com>
To: Dmitry Fleytman <dmitry@daynix.com>, qemu-devel@nongnu.org
Cc: Yan Vugenfirer <yan@daynix.com>,
Peter Maydell <peter.maydell@linaro.org>,
Leonid Bloch <leonid@daynix.com>,
Shmulik Ladkani <shmulik.ladkani@ravellosystems.com>
Subject: Re: [Qemu-devel] [PATCH] e1000e: Fix build with gcc 4.6.3 and ust tracing
Date: Mon, 6 Jun 2016 09:18:54 +0800 [thread overview]
Message-ID: <5754CF7E.4050908@redhat.com> (raw)
In-Reply-To: <1465023763-10773-1-git-send-email-dmitry@daynix.com>
On 2016年06月04日 15:02, Dmitry Fleytman wrote:
> This patch fixes used-uninitialized false
> positive while compiling with ust tracing
> backend plus gcc 4.6.3:
>
> hw/net/e1000e.c: In function ‘e1000e_io_write’:
> hw/net/e1000e.c:170:39: error: ‘idx’ may be used uninitialized in this function [-Werror=uninitialized]
> hw/net/e1000e.c: In function ‘e1000e_io_read’:
> hw/net/e1000e.c:145:35: error: ‘idx’ may be used uninitialized in this function [-Werror=uninitialized]
> cc1: all warnings being treated as errors
> make: *** [hw/net/e1000e.o] Error 1
>
> Signed-off-by: Dmitry Fleytman <dmitry@daynix.com>
> ---
> hw/net/e1000e.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/hw/net/e1000e.c b/hw/net/e1000e.c
> index 61bcbb6..692283f 100644
> --- a/hw/net/e1000e.c
> +++ b/hw/net/e1000e.c
> @@ -133,7 +133,7 @@ static uint64_t
> e1000e_io_read(void *opaque, hwaddr addr, unsigned size)
> {
> E1000EState *s = opaque;
> - uint32_t idx;
> + uint32_t idx = 0;
> uint64_t val;
>
> switch (addr) {
> @@ -158,7 +158,7 @@ e1000e_io_write(void *opaque, hwaddr addr,
> uint64_t val, unsigned size)
> {
> E1000EState *s = opaque;
> - uint32_t idx;
> + uint32_t idx = 0;
>
> switch (addr) {
> case E1000_IOADDR:
Acked-by: Jason Wang <jasowang@redhat.com>
Maybe in the future, we need something like uninitialized_var() tricks
in Linux for this.
next prev parent reply other threads:[~2016-06-06 1:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-04 7:02 [Qemu-devel] [PATCH] e1000e: Fix build with gcc 4.6.3 and ust tracing Dmitry Fleytman
2016-06-06 1:18 ` Jason Wang [this message]
2016-06-06 9:06 ` Peter Maydell
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=5754CF7E.4050908@redhat.com \
--to=jasowang@redhat.com \
--cc=dmitry@daynix.com \
--cc=leonid@daynix.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=shmulik.ladkani@ravellosystems.com \
--cc=yan@daynix.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.