This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [WIP/RFC] MIPS registers overhaul
- From: cgd at broadcom dot com
- To: ac131313 at redhat dot com
- Cc: "Kevin Buettner" <kevinb at redhat dot com>,gdb-patches at sources dot redhat dot com
- Date: 17 Jun 2003 09:27:18 -0700
- Subject: Re: [WIP/RFC] MIPS registers overhaul
- References: <1030510002453.ZM3880@localhost.localdomain><3EBD6131.30209@redhat.com><1030514220025.ZM10373@localhost.localdomain><3EC461C1.1080104@redhat.com> <mailpost.1053057614.17325@news-sj1-1><yov5znlma5s9.fsf@broadcom.com> <mailpost.1053123913.16634@news-sj1-1><yov5wugqa4m8.fsf@broadcom.com> <3ECA8EC6.6030405@redhat.com><yov5llx1mkab.fsf@broadcom.com> <3EECAB89.10609@redhat.com><yov5wuflwzx4.fsf@ldt-sj3-010.sj.broadcom.com><3EEE2B85.6030207@redhat.com> <mailpost.1055796186.4097@news-sj1-1><yov5znkhe1m7.fsf@ldt-sj3-010.sj.broadcom.com><3EEF253D.9060502@redhat.com> <mailpost.1055860052.3406@news-sj1-1>
At Tue, 17 Jun 2003 14:27:32 +0000 (UTC), "Andrew Cagney" wrote:
> The key bit being that the terminology differentaties between a 32 bit
> CP1 register and a 64 bit FPR.
^^^^^^^^^^^^
a.k.a. "FGR"
> This also suggests a better way of representing the registers to the user:
>
> MIPS I:
> $cp0, $cp1, ...: 32/64 bit raw co-processor registers
I would strongly recommend "$fgrN" since:
* that follows the manual more closely (see my previous cites;
unfortunately i can't quote the C&V's right now since my Kane is at
home 8-),
* "cpN" (a.k.a. "copN") already have fairly-well understood meanings
in MIPS-wordl which aren't this, and assmuing that one might want to
provide useful names for, oh, say, the cp2 registers, and that might
confusing very quickly.
Of course, re: the latter point of the second bullet, it looks like
gcc already believes those registers to be named "$c2rN", so at least
little bit's a red herring. 8-)
chris