From: Ralf Baechle <ralf@oss.sgi.com>
To: Andre.Messerschmidt@infineon.com
Cc: linux-mips@oss.sgi.com
Subject: Re: Cross Compiler again
Date: Mon, 26 Nov 2001 22:28:55 +1100 [thread overview]
Message-ID: <20011126222855.D30436@dea.linux-mips.net> (raw)
In-Reply-To: <86048F07C015D311864100902760F1DD01B5E3DA@dlfw003a.dus.infineon.com>; from Andre.Messerschmidt@infineon.com on Thu, Nov 22, 2001 at 06:13:46PM +0100
On Thu, Nov 22, 2001 at 06:13:46PM +0100, Andre.Messerschmidt@infineon.com wrote:
> > I regularly use gcc 3.0.1 to build the latest oss cvs kernels without
> > obvious incident.
> >
> I am using a 2.4.2 Kernel from Montavista, which is not working with gcc
> 3.0.1.
General rule for the kernel is don't use gcc 3.x. It's not only buggier
than the older compilers, it also produces worse code. In particular it's
know to misscompile certain drivers on other architectures. I'm still
using egcs 1.1.2 which is known to be a very solid compiler. That may seem
to be a bit overly conservative to some; for those I recommend a compiler
derived from 2.95.3.
> Maybe it would be wise to upgrade. Does anybody know if there are any
> problems using a MIPS 5Kc with the current kernel?
Nothing that's known.
Ralf
next prev parent reply other threads:[~2001-11-26 12:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 17:13 AW: Cross Compiler again Andre.Messerschmidt
2001-11-25 17:13 ` Daniel Jacobowitz
2001-11-26 11:28 ` Ralf Baechle [this message]
2001-11-26 12:06 ` Maciej W. Rozycki
-- strict thread matches above, loose matches on Subject: below --
2001-11-26 16:27 AW: " Andre.Messerschmidt
2001-11-26 20:31 ` Daniel Jacobowitz
2001-11-26 13:38 AW: " Andre.Messerschmidt
2001-11-26 13:48 ` Ralf Baechle
2001-11-26 8:59 Andre.Messerschmidt
2001-11-26 11:22 ` Ralf Baechle
2001-11-22 12:42 Andre.Messerschmidt
2001-11-22 18:17 ` H . J . Lu
2001-11-22 9:08 Andre.Messerschmidt
2001-11-22 10:03 ` H . J . Lu
2001-11-22 15:53 ` Bradley D. LaRonde
2001-11-22 15:53 ` Bradley D. LaRonde
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=20011126222855.D30436@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=Andre.Messerschmidt@infineon.com \
--cc=linux-mips@oss.sgi.com \
/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