From: kbuild test robot <fengguang.wu@intel.com>
To: Dave Gordon <david.s.gordon@intel.com>
Cc: kbuild-all@01.org, linux-kernel@vger.kernel.org,
Chris Wilson <chris@chris-wilson.co.uk>
Subject: drivers/gpu/drm/i915/i915_gem_gtt.c:2367: error: 'gtt_entry' may be used uninitialized in this function
Date: Sun, 6 Nov 2016 08:10:42 +0800 [thread overview]
Message-ID: <201611060834.ihxGOqUu%fengguang.wu@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1729 bytes --]
Hi Dave,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: ffbcbfca846ed117e3d4009acfbf1e1590c56b2f
commit: 85d1225ec066b2ef46fbd0ed1bae78ae1f3e6c91 drm/i915: Introduce & use new lightweight SGL iterators
date: 6 months ago
config: x86_64-randconfig-s0-11060725 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
git checkout 85d1225ec066b2ef46fbd0ed1bae78ae1f3e6c91
# save the attached .config to linux build tree
make ARCH=x86_64
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All errors (new ones prefixed by >>):
cc1: warnings being treated as errors
drivers/gpu/drm/i915/i915_gem_gtt.c: In function 'gen8_ggtt_insert_entries':
>> drivers/gpu/drm/i915/i915_gem_gtt.c:2367: error: 'gtt_entry' may be used uninitialized in this function
drivers/gpu/drm/i915/i915_gem_gtt.c: In function 'gen6_ggtt_insert_entries':
drivers/gpu/drm/i915/i915_gem_gtt.c:2442: error: 'gtt_entry' may be used uninitialized in this function
vim +/gtt_entry +2367 drivers/gpu/drm/i915/i915_gem_gtt.c
2361 enum i915_cache_level level, u32 unused)
2362 {
2363 struct drm_i915_private *dev_priv = to_i915(vm->dev);
2364 struct i915_ggtt *ggtt = i915_vm_to_ggtt(vm);
2365 struct sgt_iter sgt_iter;
2366 gen8_pte_t __iomem *gtt_entries;
> 2367 gen8_pte_t gtt_entry;
2368 dma_addr_t addr;
2369 int rpm_atomic_seq;
2370 int i = 0;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 28447 bytes --]
next reply other threads:[~2016-11-06 0:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 0:10 kbuild test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-02-05 10:31 drivers/gpu/drm/i915/i915_gem_gtt.c:2367: error: 'gtt_entry' may be used uninitialized in this function kbuild test robot
2017-01-16 8:46 kbuild test robot
2016-12-25 1:16 kbuild test robot
2016-12-11 1:31 kbuild test robot
2016-12-04 12:34 kbuild test robot
2016-11-20 5:31 kbuild test robot
2016-11-13 4:32 kbuild test robot
2016-10-30 5:57 kbuild test robot
2016-10-16 2:51 kbuild test robot
2016-10-02 1:27 kbuild test robot
2016-09-24 3:06 kbuild test robot
2016-09-10 23:35 kbuild test robot
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=201611060834.ihxGOqUu%fengguang.wu@intel.com \
--to=fengguang.wu@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=david.s.gordon@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.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).