Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: cgd@broadcom.com
Cc: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	Eric Christopher <echristo@redhat.com>,
	linux-mips@linux-mips.org
Subject: Re: gcc support for mips32 release 2]
Date: Thu, 18 Mar 2004 23:51:54 +0100	[thread overview]
Message-ID: <20040318225154.GA761@linux-mips.org> (raw)
In-Reply-To: <yov5ish3zar8.fsf@ldt-sj3-010.sj.broadcom.com>

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

  parent reply	other threads:[~2004-03-18 22:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-05 22:29 gcc support for mips32 release 2] Eric Christopher
2004-03-17 16:18 ` Maciej W. Rozycki
2004-03-17 16:41   ` cgd
2004-03-17 18:44     ` Maciej W. Rozycki
2004-03-18 22:51     ` Ralf Baechle [this message]
2004-03-18 23:03       ` Eric Christopher
2004-03-19 14:16       ` Maciej W. Rozycki

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=20040318225154.GA761@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=cgd@broadcom.com \
    --cc=echristo@redhat.com \
    --cc=linux-mips@linux-mips.org \
    --cc=macro@ds2.pg.gda.pl \
    /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