linux-mips
[Top] [All Lists]

Re: gcc support for mips32 release 2]

To: cgd@broadcom.com
Subject: Re: gcc support for mips32 release 2]
From: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Date: Wed, 17 Mar 2004 19:44:42 +0100 (CET)
Cc: Eric Christopher <echristo@redhat.com>, linux-mips@linux-mips.org
In-reply-to: <yov5ish3zar8.fsf@ldt-sj3-010.sj.broadcom.com>
Organization: Technical University of Gdansk
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <1078525778.3353.2.camel@dzur.sfbay.redhat.com> <Pine.LNX.4.55.0403171714410.14525@jurand.ds.pg.gda.pl> <yov5ish3zar8.fsf@ldt-sj3-010.sj.broadcom.com>
Sender: linux-mips-bounce@linux-mips.org
On Wed, 17 Mar 2004 cgd@broadcom.com wrote:

> >  Well, I think this can be handled by creating an artificial processor
> > entry (e.g. "PROCESSOR_MIPS64R2" in this case) and replacing it with a
> > real one once an implementation is publicly available.
> 
> yeah.  doing that, but introducing known "to be removed" code bugs me.

 That's a mechanical update and a very trivial one -- to be done with
"s///".  Sometimes you just cannot avoid placeholders.

> it's probably better than not getting the rest of the infrastructure
> in, though.

 Indeed -- you get certain automatical updates done by the others in
return.

-- 
+  Maciej W. Rozycki, Technical University of Gdansk, Poland   +
+--------------------------------------------------------------+
+        e-mail: macro@ds2.pg.gda.pl, PGP key available        +

<Prev in Thread] Current Thread [Next in Thread>