tree:   git://anongit.freedesktop.org/drm-intel drm-intel-next-queued
head:   21a2c58a9c122151080ecbdddc115257cd7c30d8
commit: 2bd160a131ac617fc2441bfb4a02964c964a5da6 [7/33] drm/i915: Reduce 
i915_gem_objects to only show object information
config: x86_64-randconfig-s2-08151903 (attached as .config)
compiler: gcc-4.4 (Debian 4.4.7-8) 4.4.7
reproduce:
        git checkout 2bd160a131ac617fc2441bfb4a02964c964a5da6
        # 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_debugfs.c: In function 'i915_gem_object_info':
>> drivers/gpu/drm/i915/i915_debugfs.c:392: error: 'mapped_count' may be used 
>> uninitialized in this function
>> drivers/gpu/drm/i915/i915_debugfs.c:393: error: 'mapped_size' may be used 
>> uninitialized in this function

vim +/mapped_count +392 drivers/gpu/drm/i915/i915_debugfs.c

   386  static int i915_gem_object_info(struct seq_file *m, void* data)
   387  {
   388          struct drm_info_node *node = m->private;
   389          struct drm_device *dev = node->minor->dev;
   390          struct drm_i915_private *dev_priv = to_i915(dev);
   391          struct i915_ggtt *ggtt = &dev_priv->ggtt;
 > 392          u32 count, mapped_count, purgeable_count, dpy_count;
 > 393          u64 size, mapped_size, purgeable_size, dpy_size;
   394          struct drm_i915_gem_object *obj;
   395          struct drm_file *file;
   396          int ret;

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/octet-stream
Size: 26098 bytes
Desc: not available
URL: 
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160815/fda5d97c/attachment-0001.obj>

Reply via email to