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: Ralf Baechle <ralf@linux-mips.org>
Date: Thu, 18 Mar 2004 23:51:54 +0100
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>, Eric Christopher <echristo@redhat.com>, linux-mips@linux-mips.org
In-reply-to: <yov5ish3zar8.fsf@ldt-sj3-010.sj.broadcom.com>
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
User-agent: Mutt/1.4.1i
On Wed, Mar 17, 2004 at 08:41:47AM -0800, cgd@broadcom.com wrote:

> At Wed, 17 Mar 2004 17:18:37 +0100 (CET), Maciej W. Rozycki 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.
> 
> it's probably better than not getting the rest of the infrastructure
> in, though.

It seems a small problem compared to having to answer all the questions
about why Linux tries to optimize for processor X when it's configured
for type Y.  People just love tweaking compiler flags it seems - even if
not necessarily knowing all the consequences ...

  Ralf

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