public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Nabendu Maiti" <nabendu.bikash.maiti@intel.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/bxt: Fix uninitialized variables in intel_check_sprite_plane
Date: Tue, 08 Dec 2015 13:20:39 +0200	[thread overview]
Message-ID: <87bna1xk3c.fsf@intel.com> (raw)
In-Reply-To: <5665CD34.9080702@intel.com>

On Mon, 07 Dec 2015, Nabendu Maiti <nabendu.bikash.maiti@intel.com> wrote:
> On 11/26/2015 11:33 PM, Nabendu Maiti wrote:
>>
>>
>> On 11/18/2015 10:56 PM, Ville Syrjälä wrote:
>>> On Wed, Nov 18, 2015 at 10:33:55PM +0530, Maiti, Nabendu Bikash wrote:
>>>>
>>>> On 11/18/2015 7:00 PM, Ville Syrjälä wrote:
>>>>> On Wed, Nov 18, 2015 at 06:48:37PM +0530, Maiti, Nabendu Bikash wrote:
>>>>>> Then just one line change of initializing the variables is better?
>>>>> Or maybe fix your compiler instead? I don't get any warning/errors 
>>>>> from
>>>>> this. What version of gcc are you using?
>>>>    I still get the warning and error if -Werror is enabled, And on
>>>> Makefile O1 optimization is enabled.
>>> And why exactly are you building with -O1?
>> I am using it for platform level debug symbol inclusion in elf which 
>> are excluded in Os/O2 . We need it.Else it will break generic kernel.
> Any comments? Please let me know if anything need to be done from my side.

Nobody is doing anything about this because it's the compiler being
silly.

We could merge your patch (provided it said this was a compiler issue)
but frankly it wouldn't take long for someone to submit a patch to drop
the unnecessary initializations again.

We could probably rearrange the code to avoid warnings (e.g. use a local
temp variable for state->visible, or use "goto out" where state->visible
is set to false) but seems like a lot of churn just to make a silly tool
happy.

Your build is bound to produce a lot of false positives across the whole
kernel build. What do you do with those?


BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-12-08 11:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 12:13 [PATCH] drm/i915/bxt: Fix uninitialized variables in intel_check_sprite_plane Nabendu Maiti
2015-11-18 12:15 ` Ville Syrjälä
2015-11-18 12:19 ` Chris Wilson
2015-11-18 12:44   ` Maiti, Nabendu Bikash
2015-11-18 12:52   ` Ville Syrjälä
2015-11-18 13:18     ` Maiti, Nabendu Bikash
2015-11-18 13:30       ` Ville Syrjälä
2015-11-18 17:03         ` Maiti, Nabendu Bikash
2015-11-18 17:26           ` Ville Syrjälä
2015-11-26 18:03             ` Nabendu Maiti
2015-12-07 18:17               ` Nabendu Maiti
2015-12-08 11:20                 ` Jani Nikula [this message]
2015-12-10  8:42                   ` Daniel Vetter

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=87bna1xk3c.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=nabendu.bikash.maiti@intel.com \
    --cc=ville.syrjala@linux.intel.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