From: Ralf Baechle <ralf@oss.sgi.com>
To: "Gleb O. Raiko" <raiko@niisi.msk.ru>
Cc: Jun Sun <jsun@mvista.com>,
Alexandr Andreev <andreev@niisi.msk.ru>,
linux-mips@oss.sgi.com
Subject: Re: 3 questions about linux-2.4.18 and R3000
Date: Mon, 3 Jun 2002 01:55:36 -0700 [thread overview]
Message-ID: <20020603015536.B2832@dea.linux-mips.net> (raw)
In-Reply-To: <3CF745B7.16CD0387@niisi.msk.ru>; from raiko@niisi.msk.ru on Fri, May 31, 2002 at 01:43:19PM +0400
On Fri, May 31, 2002 at 01:43:19PM +0400, Gleb O. Raiko wrote:
> > >> We have been using gcc 2.9.5 and binutils 2.10.x for R3000 CPUs for
> > >> quite a while with no problems. It seems newer gcc and binutiles are
> > >> fine too.
Some gcc 3.0 versions definately misscompiles the kernel; anyway 3.0 enjoys
a bad reputation for bugginess and being slow at generating slow code
beyond just the MIPS port, so why both with 3.0. 2.95.4 seems quite
reliable.
> > > I understand, but is there any __official__ recommended versions of these
> > > utils? http://oss.sgi.com/mips/mips-howto.html is out-of-date :(
Send patches.
> >
> > Who are the "officiers" to decide on __official__ versions? :-) If you are
> > really uncomfortable with non-official stuff, you might want to consider
> > paying some vendor and I am sure you will be given an "official" version.
>
> "Official" means "if I report a bug w/o a patch in this list, I don't
> get a message which requests to change the tools".
> I think, Ralf is the "officier" who decides what the right toolchain is.
> Now, last toolchain Ralf announced was
Nah, I don't consider myself an officer :-)
> Date: Fri, 1 Dec 2000 03:06:19 +0100
[embarrasingly old email deleted ...]
The issues with newer toolchains have been discussed at various times on
the list; at this time I don't have a tested toolchain that is usable for
all configurations of the kernel. Also note that my recommendation of
binutils 2.9.5 is only for the kernel.
Anyway, binutils 2.12 is looking promising so far ...
Ralf
next prev parent reply other threads:[~2002-06-03 18:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-24 22:16 3 questions about linux-2.4.18 and R3000 Alexandr Andreev
2002-05-24 21:10 ` Jun Sun
2002-05-27 21:13 ` Alexandr Andreev
2002-05-28 17:15 ` Jun Sun
2002-05-30 0:18 ` Alexandr Andreev
2002-05-31 9:43 ` Gleb O. Raiko
2002-06-03 8:55 ` Ralf Baechle [this message]
2002-06-03 18:30 ` Maciej W. Rozycki
2002-06-03 22:40 ` Ralf Baechle
2002-06-03 23:01 ` Thiemo Seufer
2002-06-03 23:04 ` Ralf Baechle
2002-06-03 23:11 ` Thiemo Seufer
2002-06-03 23:15 ` Ralf Baechle
2002-06-03 23:53 ` Thiemo Seufer
2002-06-04 17:41 ` nick
2002-06-05 22:37 ` Thiemo Seufer
2002-06-05 23:50 ` Ilya Volynets
2002-06-06 23:54 ` Thiemo Seufer
2002-06-04 14:39 ` Maciej W. Rozycki
2002-06-04 14:37 ` Maciej W. Rozycki
2002-06-05 22:38 ` Thiemo Seufer
2002-06-04 14:34 ` Maciej W. Rozycki
2002-06-04 11:31 ` Gleb O. Raiko
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=20020603015536.B2832@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=andreev@niisi.msk.ru \
--cc=jsun@mvista.com \
--cc=linux-mips@oss.sgi.com \
--cc=raiko@niisi.msk.ru \
/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