From: Daniel Jacobowitz <dan@debian.org>
To: Dominic Sweetman <dom@algor.co.uk>
Cc: Eric Christopher <echristo@redhat.com>,
Johannes Stezenbach <js@convergence.de>,
gcc@gcc.gnu.org, linux-mips@oss.sgi.com, sde@algor.co.uk
Subject: Re: [Fwd: Current state of MIPS16 support?]
Date: Wed, 5 Jun 2002 13:53:18 -0400 [thread overview]
Message-ID: <20020605175318.GA4030@nevyn.them.org> (raw)
In-Reply-To: <15614.12481.424601.806779@gladsmuir.algor.co.uk>
On Wed, Jun 05, 2002 at 04:39:45PM +0100, Dominic Sweetman wrote:
> > I'm not certain what you are actually fixing here as I've not seen any
> > descriptions of problems here...
>
> Hmm. Linux/MIPS suffers from widespread and diffuse toolchain
> problems: I thought that much was pretty clear to all involved. I
> agree it seems a pity that the scheme of work laid out above should be
> necessary...
...
> > Almost 90% of the bug reports I see are against IRIX.
>
> That does suggest you're missing some pretty large chunks of the
> community!
No, that's not what it suggests at all. It suggests to me that the
dubious state of Linux/MIPS toolchains is due to one of two things:
- A pre-existing acceptance of this rather than any real problems
- A reluctance to file bug reports
We've been using GCC for MIPS for several years now and seen relatively
few significant problems, so I suspect the former. There's definitely
some of the latter as well, since we've hit more roadblocks on MIPS
than on, say, x86 or PowerPC; it's not our worst problem architecture,
though. And we've been able to fix them all relatively easily.
I'm sure GCC would benefit from access to your regression tests, though :)
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-06-05 17:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3CBFEAA9.9070707@algor.co.uk>
2002-04-30 10:16 ` [Fwd: Current state of MIPS16 support?] Dominic Sweetman
2002-04-30 10:16 ` Dominic Sweetman
2002-05-08 21:40 ` Eric Christopher
2002-05-31 18:40 ` Eric Christopher
2002-05-31 21:44 ` Joe Buck
2002-05-31 21:44 ` Joe Buck
2002-06-05 15:13 ` Dominic Sweetman
2002-06-05 15:13 ` Dominic Sweetman
2002-06-05 16:05 ` law
2002-06-05 16:05 ` law
2002-06-06 8:58 ` Dominic Sweetman
2002-06-06 8:58 ` Dominic Sweetman
2002-06-06 9:59 ` Phil Edwards
2002-06-06 15:36 ` law
2002-06-05 15:39 ` Dominic Sweetman
2002-06-05 17:53 ` Daniel Jacobowitz [this message]
[not found] ` <mailpost.1023291613.28112@news-sj1-1>
2002-06-06 6:31 ` cgd
2002-06-06 9:14 ` Dominic Sweetman
2002-06-06 15:13 ` cgd
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=20020605175318.GA4030@nevyn.them.org \
--to=dan@debian.org \
--cc=dom@algor.co.uk \
--cc=echristo@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=js@convergence.de \
--cc=linux-mips@oss.sgi.com \
--cc=sde@algor.co.uk \
/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