From: Lee Revell <rlrevell@joe-job.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Nix <nix@esperi.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: Building 100 kernels; we suck at dependencies and drown in warnings
Date: Sun, 26 Feb 2006 16:53:39 -0500 [thread overview]
Message-ID: <1140990819.24141.176.camel@mindpipe> (raw)
In-Reply-To: <9a8748490602261349v381933b9xeb2ddeedac053910@mail.gmail.com>
On Sun, 2006-02-26 at 22:49 +0100, Jesper Juhl wrote:
> On 2/26/06, Nix <nix@esperi.org.uk> wrote:
> > (i.e., there's a reason that warning uses the word *might*.)
> >
> The compiler says "might be used uninitialized" when it cannot
> determine if a variable will be initialized before first use or not.
Quoting the "silence gcc warning" thread:
"Really, this is a gcc bug. My version of the compiler:
gcc version 4.0.3 20051201 (prerelease) (Debian 4.0.2-5)
Doesn't give this warning. And, since the loop has fixed parameters,
gcc should see not only that it's always executed, but that it could be
unrolled."
Lee
next prev parent reply other threads:[~2006-02-26 21:53 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-26 16:21 Building 100 kernels; we suck at dependencies and drown in warnings Jesper Juhl
2006-02-26 16:31 ` Jesper Juhl
2006-02-26 16:35 ` Jesper Juhl
2006-02-26 19:31 ` Dave Jones
2006-02-26 19:43 ` Jesper Juhl
2006-02-26 20:11 ` Jesper Juhl
2006-02-26 23:45 ` Nigel Cunningham
2006-02-27 2:02 ` Pavel Machek
2006-02-26 19:30 ` Dave Jones
2006-02-26 17:00 ` Adrian Bunk
2006-02-26 17:29 ` Jesper Juhl
2006-02-26 17:41 ` Adrian Bunk
2006-02-26 18:08 ` Jesper Juhl
2006-02-26 17:38 ` Jesper Juhl
2006-02-26 18:21 ` Diego Calleja
2006-02-26 18:45 ` Jesper Juhl
2006-02-26 19:03 ` Diego Calleja
2006-02-26 20:42 ` Lee Revell
2006-02-26 20:44 ` Jesper Juhl
2006-02-26 21:46 ` Nix
2006-02-26 21:49 ` Jesper Juhl
2006-02-26 21:53 ` Lee Revell [this message]
2006-02-26 21:56 ` Jesper Juhl
2006-02-26 22:08 ` Lee Revell
2006-02-26 22:12 ` Jesper Juhl
2006-02-27 17:25 ` Stephen Hemminger
2006-02-26 22:14 ` Al Viro
2006-02-26 22:32 ` Nix
2006-02-26 22:50 ` Lee Revell
2006-02-26 21:14 ` Grant Coady
2006-02-27 12:56 ` David Greaves
2006-02-28 10:30 ` Roman Zippel
2006-02-26 22:43 ` Sam Ravnborg
2006-03-02 20:25 ` Jesper Juhl
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=1140990819.24141.176.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nix@esperi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox