All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benoit Boissinot <bboissin@gmail.com>
To: Bob Gill <gillb4@telusplanet.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Kernel 2.6.12-rc4 and gcc-4.0.0 (datatype issue?)
Date: Tue, 10 May 2005 02:17:04 +0200	[thread overview]
Message-ID: <40f323d0050509171736748ead@mail.gmail.com> (raw)
In-Reply-To: <1115676539.7849.73.camel@localhost.localdomain>

On 5/10/05, Bob Gill <gillb4@telusplanet.net> wrote:
> Hi.  I recently built 2.6.12-rc4 with gcc-4.0.0, and got a few eip's on
> boot (as reported by dmesg).  I have not found the errors affecting the
> system yet (but I haven't tested exhaustively yet either).  If building
> the recent kernels with gcc-4.0.0 is too early, then please disregard
> this message.
> My first guess (as to the nature of the problem) is a conversion problem
> in kernel/sysctl.c (line 1462 or thereabouts)...this:
> 
This is a gcc bug (fixed in newer snapshots)

regards,

Benoit

      reply	other threads:[~2005-05-10  0:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-09 22:08 Kernel 2.6.12-rc4 and gcc-4.0.0 (datatype issue?) Bob Gill
2005-05-10  0:17 ` Benoit Boissinot [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=40f323d0050509171736748ead@mail.gmail.com \
    --to=bboissin@gmail.com \
    --cc=gillb4@telusplanet.net \
    --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 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.