From: Adrian Bunk <bunk@stusta.de>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: Kyle Moffett <mrmacman_g4@mac.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jiri Kosina <jikos@jikos.cz>, Lee Revell <rlrevell@joe-job.com>,
andrea@suse.de, viro@zeniv.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: fs/block_dev.c:953: warning: 'found' might be used uninitialized in this function
Date: Sat, 31 Mar 2007 16:04:32 +0200 [thread overview]
Message-ID: <20070331140432.GS14134@stusta.de> (raw)
In-Reply-To: <200703311011.32682.toralf.foerster@gmx.de>
On Sat, Mar 31, 2007 at 10:11:27AM +0200, Toralf Förster wrote:
> Am Freitag, 30. März 2007 21:47 schrieb Adrian Bunk:
> >
> >
> > No, the code is correct and it's impossible that the variable ever gets
> > read uninitialized.
> >
> > And BTW, i386 gcc 4.1 doesn't give me a warning for this.
> > Toralf, which gcc version and architecture did you see this with?
>
> > cu
> > Adrian
> >
>
> Hi, I use currently the following version:
>
> gcc version 3.4.6 (Gentoo 3.4.6-r2, ssp-3.4.6-1.0, pie-8.7.10)
For finding warnings it's better to use the latest gcc version - gcc is
evalving, and more recent versions tend to both give more valid warnings
and give less warnings for non-problems (like in this case).
> MfG/Sincerely
>
> Toralf Förster
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2007-03-31 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 16:47 fs/block_dev.c:953: warning: 'found' might be used uninitialized in this function Toralf Förster
2007-03-28 16:56 ` Lee Revell
2007-03-28 17:23 ` Jiri Kosina
2007-03-28 20:14 ` Andrew Morton
2007-03-28 21:59 ` Dan Aloni
2007-03-30 3:16 ` Kyle Moffett
2007-03-30 19:47 ` Adrian Bunk
2007-03-31 3:09 ` Cong WANG
2007-03-31 8:11 ` Toralf Förster
2007-03-31 14:04 ` Adrian Bunk [this message]
2007-03-30 19:40 ` Adrian Bunk
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=20070331140432.GS14134@stusta.de \
--to=bunk@stusta.de \
--cc=akpm@linux-foundation.org \
--cc=andrea@suse.de \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mrmacman_g4@mac.com \
--cc=rlrevell@joe-job.com \
--cc=toralf.foerster@gmx.de \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.