From: cgd@broadcom.com
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: "Eric Christopher" <echristo@redhat.com>, linux-mips@linux-mips.org
Subject: Re: gcc support for mips32 release 2]
Date: 17 Mar 2004 08:41:47 -0800 [thread overview]
Message-ID: <yov5ish3zar8.fsf@ldt-sj3-010.sj.broadcom.com> (raw)
In-Reply-To: <Pine.LNX.4.55.0403171714410.14525@jurand.ds.pg.gda.pl>
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.
cgd
next prev parent reply other threads:[~2004-03-17 16:42 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 [this message]
2004-03-17 18:44 ` Maciej W. Rozycki
2004-03-18 22:51 ` Ralf Baechle
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=yov5ish3zar8.fsf@ldt-sj3-010.sj.broadcom.com \
--to=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