From: "P. Christeas" <p_christ@hol.gr>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: David Daney <ddaney@avtrex.com>,
Kishore K <hellokishore@gmail.com>,
Linux/MIPS Development <linux-mips@linux-mips.org>
Subject: Re: gcc -3.4.4 and linux-2.4.32
Date: Thu, 19 Jan 2006 12:30:57 +0200 [thread overview]
Message-ID: <200601191230.59347.p_christ@hol.gr> (raw)
In-Reply-To: <Pine.LNX.4.62.0601191100001.21230@pademelon.sonytel.be>
On Thursday 19 January 2006 12:00 pm, Geert Uytterhoeven wrote:
> On Thu, 19 Jan 2006, P. Christeas wrote:
> > Just to let you know:
> > In a very interesting twist, gcc4.0.2 produces a faulty kernel with the
> > 2.4.31 kernel (as the latter is provided from the hardware's
> > manufacturer). I'm validating gcc and binutils at the moment.
>
> That's why 2 days ago this one went in in 2.4.x:
> | [PATCH] document that gcc 4 is not supported
> |
> | gcc 4 is not supported for compiling kernel 2.4, and I don't see any
> | compelling reason why kernel 2.4 should ever be adapted to gcc 4.
Which comes round to the main reason I'm doing this work (port the platform to
2.6): if we are not using the *latest* kernel with the *latest* build/user
tools, then we cannot share our work. Patches to an old kernel/gcc may
probably get discarded when moving to the next version.
Nevertheless, I think my problem has been the binutils. After switching to
version 2.16.1, the oops probability (per reset) dropped from 80% to <20% and
the oops is less random. (that is, there is also one, real, bug)
next prev parent reply other threads:[~2006-01-19 10:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-16 12:23 gcc -3.4.4 and linux-2.4.32 Kishore K
2006-01-16 12:23 ` Kishore K
2006-01-16 17:34 ` David Daney
2006-01-17 12:07 ` Kishore K
2006-01-17 12:26 ` P. Christeas
2006-01-18 22:35 ` P. Christeas
2006-01-19 10:00 ` Geert Uytterhoeven
2006-01-19 10:30 ` P. Christeas [this message]
2006-01-19 12:33 ` "useless" pgprot_noncached define in include/asm-mips/pgtable.h Niels Sterrenburg
2006-01-23 15:54 ` Atsushi Nemoto
2006-01-17 13:43 ` gcc -3.4.4 and linux-2.4.32 Ralf Baechle
2006-01-17 13:40 ` Ralf Baechle
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=200601191230.59347.p_christ@hol.gr \
--to=p_christ@hol.gr \
--cc=ddaney@avtrex.com \
--cc=geert@linux-m68k.org \
--cc=hellokishore@gmail.com \
--cc=linux-mips@linux-mips.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.