From: "H . J . Lu" <hjl@lucon.org>
To: Shane Nay <shane@minirl.com>
Cc: James Simmons <jsimmons@transvirtual.com>,
Pavel Machek <pavel@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mips@oss.sgi.com, linux-mips-kernel@lists.sourceforge.net
Subject: Re: [Linux-mips-kernel] Re: [ANNOUNCE] Secondary mips tree.
Date: Tue, 17 Jul 2001 08:35:14 -0700 [thread overview]
Message-ID: <20010717083514.A19836@lucon.org> (raw)
In-Reply-To: <Pine.LNX.4.10.10107161226220.19188-100000@transvirtual.com> <0107170016150H.02677@compiler>
In-Reply-To: <0107170016150H.02677@compiler>; from shane@minirl.com on Tue, Jul 17, 2001 at 12:16:15AM -0700
On Tue, Jul 17, 2001 at 12:16:15AM -0700, Shane Nay wrote:
> > We have been having problems with toolchains as well. We plan to have a
> > new toolchain ready by Wednesday.
>
> Yes, there have been a lot of toolchain issues with MIPs. The last time I
> went on a toolchain testing binge for MIPs was with GCC CVS in about April.
> I had really good results with that toolchain with both the kernel and
> userland. I did some micro tests with 3.0 and they appeared solid, but I had
> updated to the latest non-CVS version of bintools and it was chocking out
> lots of assembler warnings when rebuilding glibc. There are source and
> binary snaps of that toolchain on the agenda FTP site under snow.
>
The toolchain in my RedHat 7.1 mips port is as good as the x86 version
for RedHat 7.1. Since there is no mips maintainer for gcc, many
mips patches aren't reviewed. But they are in my mips toolchain.
H.J.
next prev parent reply other threads:[~2001-07-17 15:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-22 20:57 [ANNOUNCE] Secondary mips tree James Simmons
2001-06-30 14:57 ` Pavel Machek
2001-07-08 18:32 ` James Simmons
2001-07-09 12:02 ` Pavel Machek
2001-07-12 21:47 ` strange 2.4.x problems with dual machine ognen
2001-07-13 15:01 ` [ANNOUNCE] Secondary mips tree James Simmons
2001-07-16 10:22 ` Shane Nay
2001-07-16 19:27 ` [Linux-mips-kernel] " James Simmons
2001-07-17 7:16 ` Shane Nay
2001-07-17 15:35 ` H . J . Lu [this message]
2001-07-17 16:41 ` Toolchains James Simmons
2001-07-17 17:20 ` Toolchains H . J . Lu
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=20010717083514.A19836@lucon.org \
--to=hjl@lucon.org \
--cc=jsimmons@transvirtual.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips-kernel@lists.sourceforge.net \
--cc=linux-mips@oss.sgi.com \
--cc=pavel@suse.cz \
--cc=shane@minirl.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