Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Fred Fish <fnf@intrinsity.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Eliminate hard coded constant num_regs in mips_gdbarch_init
Date: Tue, 01 Jul 2003 21:50:00 -0000	[thread overview]
Message-ID: <3F020208.5060900@redhat.com> (raw)
In-Reply-To: <20030627202552.A18648B5FD@bletchley.vert.intrinsity.com>

> It's about par for the course :-(  The code also assumes that 
>> mips_r3041_reg_names, mips_r3051_reg_names and mips_r3081_reg_names are 
>> the same size (90 - 32).  If you're trying to add more than 90 
>> registers, you've a bigger problem.
> 
> 
> Currently we have at total of 416 registers defined, including the

you have a bigger problem :-(

> standard mips architecture registers.  However that includes an
> individual register for every element of each matrix register, each of
> which holds 16 32-bit values.  I'm working on redefining the register
> set more like how the MMX and Altivec registers work, where $m0 is a
> single register instead of 16 individual registers ($m0_00,
> ... $m0_15).

Insight, at least, works much better when you do this.  Also note the 
``reggroups'', it lets you categorize all the registers - again working 
much better with GUIs.

Andrew



      reply	other threads:[~2003-07-01 21:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-27 17:28 Fred Fish
2003-06-27 19:53 ` Andrew Cagney
2003-06-27 20:25   ` Fred Fish
2003-07-01 21:50     ` Andrew Cagney [this message]

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=3F020208.5060900@redhat.com \
    --to=ac131313@redhat.com \
    --cc=fnf@intrinsity.com \
    --cc=gdb-patches@sources.redhat.com \
    /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