public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Building 100 kernels; we suck at dependencies and drown in warnings
Date: Mon, 27 Feb 2006 09:25:01 -0800	[thread overview]
Message-ID: <20060227092501.7be9b1a2@localhost.localdomain> (raw)
In-Reply-To: 9a8748490602261412x6f610253mf0a991bd76cded89@mail.gmail.com

On Sun, 26 Feb 2006 23:12:51 +0100
"Jesper Juhl" <jesper.juhl@gmail.com> wrote:

> On 2/26/06, Lee Revell <rlrevell@joe-job.com> wrote:
> > On Sun, 2006-02-26 at 22:56 +0100, Jesper Juhl wrote:
> > > Yeah so gcc is not perfect, but that still doesn't change that the
> > > intention of the warning and the use of the word "might" is as I said
> > > above.
> >
> > Not a very compelling case for changing the kernel rather than getting
> > GCC fixed.
> >
> 
> I think we are misunderstanding eachother. Or rather, I seem to have
> misread what Nix wrote.
> 
> I saw  "(i.e., there's a reason that warning uses the word *might*.)"
> and mistakenly read it as a question - "is there a reason that warning
> uses the word *might*?".
> I then proceeded to answer that question.
> When I read your latest mail I then couldn't make sense of things any
> longer and went back and read the previous mails again and realized my
> mistake.
> 
> My bad, sorry.

I went hunting for this in the GCC bugzilla, and one bug basically said.
"Yeah, we know the initialization checking code doesn't work right, but
 fixing it is too hard"

  reply	other threads:[~2006-02-27 17:25 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
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 [this message]
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=20060227092501.7be9b1a2@localhost.localdomain \
    --to=shemminger@osdl.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