mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: Keith Busch <keith.busch@intel.com>,
	linux-kernel@vger.kernel.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] Regulator: Suppress compiler warnings
Date: Tue, 1 Sep 2015 14:09:55 +0100	[thread overview]
Message-ID: <20150901130955.GV5313@sirena.org.uk> (raw)
In-Reply-To: <CAJKOXPcO3k7gtszocL-bq1br_gk0veERdTtBJJXkwj0bNjCaew@mail.gmail.com>

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

On Tue, Sep 01, 2015 at 09:52:13AM +0900, Krzysztof Kozlowski wrote:
> 2015-09-01 1:41 GMT+09:00 Keith Busch <keith.busch@intel.com>:
> > Some compilers complain of possible uninitialized variable usage, like
> > the following:

> >   drivers/regulator/helpers.c: In function ‘regulator_get_bypass_regmap’:
> >   drivers/regulator/helpers.c:463:16: warning: ‘val’ may be used uninitialized in this function [-Wuninitialized]

> > The code is safe though, and only uses the variables if they were
> > successfully set, so suppressing the warning with uninitialized_val.

> >  int regulator_is_enabled_regmap(struct regulator_dev *rdev)
> >  {
> > -       unsigned int val;
> > +       unsigned int uninitialized_var(val);
> >         int ret;
> >
> >         ret = regmap_read(rdev->regmap, rdev->desc->enable_reg, &val);

> This is quite common pattern so such work-around should be added to
> many other functions leading to code obfuscation. Which compiler do
> you have in mind?

Right, plus this will shut up valid compiler warnings which is poor
practice anyway.  I'd say this is a bug in the compiler.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2015-09-01 13:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 16:41 Keith Busch
2015-09-01  0:52 ` Krzysztof Kozlowski
2015-09-01 13:09   ` Mark Brown [this message]
2015-09-01 18:40     ` Keith Busch

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=20150901130955.GV5313@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=k.kozlowski@samsung.com \
    --cc=keith.busch@intel.com \
    --cc=lgirdwood@gmail.com \
    --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

all inboxes | Powered by JetHome®