Re: gcc support for mips32 release 2]

["Maciej W. Rozycki" <macro@ds2.pg.gda.pl>]

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        +