Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@lucon.org>
To: Mark Mitchell <mark@codesourcery.com>
Cc: Eric Christopher <echristo@redhat.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	"linux-mips@oss.sgi.com" <linux-mips@oss.sgi.com>
Subject: Re: PATCH: Clean up Linux/mips.
Date: Wed, 8 Aug 2001 09:09:23 -0700	[thread overview]
Message-ID: <20010808090923.A28678@lucon.org> (raw)
In-Reply-To: <35250000.997285978@gandalf.codesourcery.com>; from mark@codesourcery.com on Wed, Aug 08, 2001 at 08:52:58AM -0700

On Wed, Aug 08, 2001 at 08:52:58AM -0700, Mark Mitchell wrote:
> > I am trying to get gcc 3.x to work correctly on Linux/mips.
> 
> Sorry, that didn't answer my question either.
> 
> You need to explain what problem your patch solves, in detail, and how
> it solves it, so that even I, not as smart as you, can understand it.
> 

Well, the mips config is a mess and Eric suggested me to clean it up
at least for Linux/mips since I have been working on fixing the gcc
3.x for Linux/mips. I'd love to see Linux/mips be supported in gcc
3.0.1. But I am afraid I don't have the time to do more than what I
have done so far.


H.J.

  reply	other threads:[~2001-08-08 16:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-07 15:42 PATCH: Clean up Linux/mips H . J . Lu
2001-08-08 13:51 ` Eric Christopher
2001-08-08 14:17   ` H . J . Lu
2001-08-08 14:19     ` Eric Christopher
2001-08-08 14:35       ` H . J . Lu
2001-08-08 14:38         ` Eric Christopher
2001-08-08 14:47           ` H . J . Lu
2001-08-08 15:04           ` Mark Mitchell
2001-08-08 15:08             ` H . J . Lu
2001-08-08 15:39               ` Mark Mitchell
2001-08-08 15:45                 ` H . J . Lu
2001-08-08 15:52                   ` Mark Mitchell
2001-08-08 16:09                     ` H . J . Lu [this message]
2001-08-08 16:12                       ` Mark Mitchell

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=20010808090923.A28678@lucon.org \
    --to=hjl@lucon.org \
    --cc=echristo@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=linux-mips@oss.sgi.com \
    --cc=mark@codesourcery.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