From: Fengguang Wu <fengguang.wu@intel.com>
To: Cornelia Huck <cornelia.huck@de.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org
Subject: Re: [kbuild-all] drivers/virtio/virtio_balloon.o: warning: objtool: release_pages_balloon()+0x98: function has unreachable instruction
Date: Wed, 20 Jul 2016 09:09:01 +0800 [thread overview]
Message-ID: <20160720010901.GI17027@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <201607200114.HcVYZBtb%fengguang.wu@intel.com>
Hi Cornelia, Michael,
Sorry please ignore this one -- it looks like false warning from old
gcc 4.4 and 4.6 -- we just enabled old compiler tests triggered
thousands of these warnings..
Thanks,
Fengguang
On Wed, Jul 20, 2016 at 01:33:15AM +0800, kbuild test robot wrote:
>tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
>head: 47ef4ad2684d380dd6d596140fb79395115c3950
>commit: 87c9403b0d1de4676b0bd273eea68fcf6de68e68 virtio_balloon: fix PFN format for virtio-1
>date: 8 weeks ago
>config: x86_64-randconfig-a0-07191719 (attached as .config)
>compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
>reproduce:
> git checkout 87c9403b0d1de4676b0bd273eea68fcf6de68e68
> # save the attached .config to linux build tree
> make ARCH=x86_64
>
>All warnings (new ones prefixed by >>):
>
> drivers/virtio/virtio_balloon.c: In function 'update_balloon_stats':
> drivers/virtio/virtio_balloon.c:249: warning: 'events[2]' is used uninitialized in this function
> drivers/virtio/virtio_balloon.c:251: warning: 'events[3]' is used uninitialized in this function
> drivers/virtio/virtio_balloon.c:232: warning: 'events[12]' is used uninitialized in this function
> drivers/virtio/virtio_balloon.c:239: note: 'events[12]' was declared here
> drivers/virtio/virtio_balloon.c:232: warning: 'events[11]' is used uninitialized in this function
> drivers/virtio/virtio_balloon.c:239: note: 'events[11]' was declared here
>>> drivers/virtio/virtio_balloon.o: warning: objtool: release_pages_balloon()+0x98: function has unreachable instruction
>
>---
>0-DAY kernel test infrastructure Open Source Technology Center
>https://lists.01.org/pipermail/kbuild-all Intel Corporation
>_______________________________________________
>kbuild-all mailing list
>kbuild-all@lists.01.org
>https://lists.01.org/mailman/listinfo/kbuild-all
prev parent reply other threads:[~2016-07-20 1:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-19 17:33 kbuild test robot
2016-07-20 1:09 ` Fengguang Wu [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=20160720010901.GI17027@wfg-t540p.sh.intel.com \
--to=fengguang.wu@intel.com \
--cc=cornelia.huck@de.ibm.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®