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 08:08:59 -0700 [thread overview]
Message-ID: <20010808080859.D26983@lucon.org> (raw)
In-Reply-To: <11900000.997283081@gandalf.codesourcery.com>; from mark@codesourcery.com on Wed, Aug 08, 2001 at 08:04:41AM -0700
On Wed, Aug 08, 2001 at 08:04:41AM -0700, Mark Mitchell wrote:
>
>
> --On Wednesday, August 08, 2001 03:38:08 PM +0100 Eric Christopher
> <echristo@redhat.com> wrote:
>
> > Quick question: You said you tested, but I wanted to verify that you
> > were able to bootstrap with no regressions? If so, then it is approved
> > for the trunk. Mark will need to approve for the branch.
>
> What incredibly critical problem does this solve? Recall that 3.0.1
> is currently frozen, waiting only for some breakage in V3-land to get
> fixed, before we produce a release candidate.
Have you seen reports on any Linux/mips targets at
http://gcc.gnu.org/ml/gcc-testresults/
My goal is to make it appear one day. I'd like to see gcc 3.0.1 is
at least partially supported on Linux/mips.
H.J.
next prev parent reply other threads:[~2001-08-08 15: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 [this message]
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
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=20010808080859.D26983@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