Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org, kbuild-all@01.org,
	dri-devel@lists.freedesktop.org
Subject: [drm-intel:drm-intel-next-queued 7/33] drivers/gpu/drm/i915/i915_debugfs.c:392: error: 'mapped_count' may be used uninitialized in this function
Date: Mon, 15 Aug 2016 19:49:42 +0800	[thread overview]
Message-ID: <201608151937.qVFFooeD%fengguang.wu@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1721 bytes --]

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

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 26098 bytes --]

[-- Attachment #3: Type: text/plain, Size: 160 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

                 reply	other threads:[~2016-08-15 11:49 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201608151937.qVFFooeD%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kbuild-all@01.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