From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: tca8418_keypad: hide gcc-4.9 -Wmaybe-uninitialized warning
Date: Wed, 26 Oct 2016 15:59:54 -0700 [thread overview]
Message-ID: <20161026225954.GD27930@dtor-ws> (raw)
In-Reply-To: <3580924.2eqYJQ5Dgh@wuerfel>
On Tue, Oct 25, 2016 at 11:59:22AM +0200, Arnd Bergmann wrote:
> On Monday, October 24, 2016 4:45:13 PM CEST Dmitry Torokhov wrote:
> > > diff --git a/drivers/input/keyboard/tca8418_keypad.c b/drivers/input/keyboard/tca8418_keypad.c
> > > index 9002298698fc..3048ef3e3e16 100644
> > > --- a/drivers/input/keyboard/tca8418_keypad.c
> > > +++ b/drivers/input/keyboard/tca8418_keypad.c
> > > @@ -164,11 +164,18 @@ static void tca8418_read_keypad(struct tca8418_keypad *keypad_data)
> > > int error, col, row;
> > > u8 reg, state, code;
> > >
> > > - /* Initial read of the key event FIFO */
> > > - error = tca8418_read_byte(keypad_data, REG_KEY_EVENT_A, ®);
> > > + do {
> > > + error = tca8418_read_byte(keypad_data, REG_KEY_EVENT_A, ®);
> > > + if (error < 0) {
> > > + dev_err(&keypad_data->client->dev,
> > > + "unable to read REG_KEY_EVENT_A\n");
> > > + break;
> > > + }
> > > +
> > > + /* Assume that key code 0 signifies empty FIFO */
> > > + if (reg <= 0)
> > > + break;
> >
> > I am unconvinced that this rearrangement fixes the issue for all older
> > GCCs. Can we simply do:
> >
> > u8 uninitialized_var(reg);
> >
> > and be done with it?
>
> Yes, that would work. However:
>
> - avoiding the fake intialization tends to produce better object
> code, as gcc actually knows what's going on
> - Linus doesn't like uninitialized_var() and would rather see it
> removed from the kernel
> - llvm produces warnings for uninitialized_var()
>
> I have checked gcc-4.6/4.7/4.8/4.9/5.x/6.x, and only gcc-4.9
> produces the warning. 4.9 changed the detection for uninitialized
> variables significantly, which generally caused fewer false
> positives but unfortunately introduced a couple of new ones
> like this.
OK, I'll apply it then.
Thanks.
--
Dmitry
prev parent reply other threads:[~2016-10-26 22:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-24 15:32 [PATCH] Input: tca8418_keypad: hide gcc-4.9 -Wmaybe-uninitialized warning Arnd Bergmann
2016-10-24 23:45 ` Dmitry Torokhov
2016-10-25 9:59 ` Arnd Bergmann
2016-10-26 22:59 ` Dmitry Torokhov [this message]
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=20161026225954.GD27930@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=arnd@arndb.de \
--cc=linux-input@vger.kernel.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).