Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: jtc@redback.com (J.T. Conklin)
To: Michael Hayes <m.hayes@elec.canterbury.ac.nz>
Cc: Stan Shebs <shebs@cygnus.com>, gdb@sourceware.cygnus.com
Subject: Re: Proposal for handling large numbers of registers
Date: Fri, 06 Aug 1999 18:27:00 -0000	[thread overview]
Message-ID: <5mwvv82xei.fsf@jtc.redbacknetworks.com> (raw)
In-Reply-To: <14251.31513.361599.969792@ongaonga.elec.canterbury.ac.nz>

>> So I'm considering importing the idea of "register classes" from
>> GCC.  GCC uses the class idea to guide allocation and instruction
>> selection, but we don't even need that much; just define the names
>> of the classes and which registers belong to each.

> It would be nice if one could just cut the register class
> definitions from gcc tm.h and paste them into gdb tm.h.

I'm not sure that a compilers notion of register classes make sense
for debugging and vice versa.  For debugging, broad categories like
"integer registers", "floating point registers", "system registers"
seem to be most appropriate; while compilers think of classes like
"registers that can be used for indexing", "special register used
for integer divide instructions", etc.

        --jtc

-- 
J.T. Conklin
RedBack Networks
From m.hayes@elec.canterbury.ac.nz Fri Aug 06 18:36:00 1999
From: Michael Hayes <m.hayes@elec.canterbury.ac.nz>
To: jtc@redback.com
Cc: Michael Hayes <m.hayes@elec.canterbury.ac.nz>, Stan Shebs <shebs@cygnus.com>, gdb@sourceware.cygnus.com
Subject: Re: Proposal for handling large numbers of registers
Date: Fri, 06 Aug 1999 18:36:00 -0000
Message-id: <14251.35343.506647.777893@ongaonga.elec.canterbury.ac.nz>
References: <199908062333.QAA16667@andros.cygnus.com> <14251.31513.361599.969792@ongaonga.elec.canterbury.ac.nz> <5mwvv82xei.fsf@jtc.redbacknetworks.com>
X-SW-Source: 1999-q3/msg00125.html
Content-length: 679

J.T. Conklin writes:
 > I'm not sure that a compilers notion of register classes make sense
 > for debugging and vice versa.  For debugging, broad categories like
 > "integer registers", "floating point registers", "system registers"
 > seem to be most appropriate; while compilers think of classes like
 > "registers that can be used for indexing", "special register used
 > for integer divide instructions", etc.

For most targets I have looked at, these other classes you mention are
usually sub-classes of the "integer registers", "fp registers", etc.
However, I can see from most user's perspectives that they will not be
interested in these special sub-classes.

Michael.


  reply	other threads:[~1999-08-06 18:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199908062333.QAA16667@andros.cygnus.com>
1999-08-06 17:33 ` Michael Hayes
1999-08-06 18:27   ` J.T. Conklin [this message]
1999-08-09 16:31 ` J.T. Conklin

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=5mwvv82xei.fsf@jtc.redbacknetworks.com \
    --to=jtc@redback.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=m.hayes@elec.canterbury.ac.nz \
    --cc=shebs@cygnus.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